URL text selection highlight colour in private mode doesn't match text selection handles

NEW
Unassigned

Status

()

Firefox for Android
Theme and Visual Design
P3
normal
8 months ago
7 months ago

People

(Reporter: winson.wen1, Unassigned)

Tracking

57 Branch
All
Android
Points:
---

Firefox Tracking Flags

(fennec-, firefox55 wontfix, firefox56 wontfix, firefox57 affected)

Details

(Reporter)

Description

8 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20170915220136

Steps to reproduce:

Open a private tab
Type text in the url bar
Select text in url bar


Actual results:

Highlight is purple while text selection handles are blue


Expected results:

Maybe the highlight colour should match the handles?
Not sure if current behaviour is intentional but it looks like a bug.

Comment 1

8 months ago
Interestingly enough this issue predates Photon - in 55 I see the same issue.

Given that the selection highlight colour was tweaked for Photon, I guess the highlight colour is intentional and so it's probably rather the selection handles that should change.

Carol, what's your opinion on this?

Also, a slight scope creep, but should text selection for page contents use purple in private mode, too (at the moment it's all blue)?
Status: UNCONFIRMED → NEW
tracking-fennec: --- → ?
status-firefox55: --- → wontfix
status-firefox56: --- → wontfix
status-firefox57: --- → affected
Component: General → Theme and Visual Design
Ever confirmed: true
Flags: needinfo?(chuang)
OS: Unspecified → Android
Hardware: Unspecified → All
Summary: URL text selection colour in private mode is purple → URL text selection highlight colour in private mode doesn't match text selection handles

Comment 2

8 months ago
The previous Firefox is also using orange as the main color for text selection handle; different text highlight for Normal/Private tab. Let's keep the same behavior for now.
Flags: needinfo?(chuang)

Updated

7 months ago
tracking-fennec: ? → -
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.