Closed Bug 1408007 Opened 7 years ago Closed 7 years ago

SVG indicators not changing colours properly for background tabs(other tabs)

Categories

(Firefox :: Theme, defect, P1)

58 Branch
defect

Tracking

()

RESOLVED FIXED
Firefox 58
Tracking Status
firefox58 --- fixed

People

(Reporter: u595893, Assigned: sfoster)

References

(Blocks 1 open bug)

Details

(Whiteboard: [reserve-photon-animation])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171011220113

Steps to reproduce:

In FF58 open a bunch of folders together


Actual results:

The selected tabs first shows grey indicator then changes to blue but the rest of the tabs show only grey


Expected results:

Initially the indicators should have been grey then when websites send data it should change to blue
This used to happen in earlier implementation and was useful as it would change to blue from grey to notify that websites are loading,
now it stays grey and doesn't notify if websites are loading.
Has Regression Range: --- → irrelevant
Has STR: --- → irrelevant
Component: Untriaged → Tabbed Browser
OS: Unspecified → All
Hardware: Unspecified → All
Summary: SVG indicators not changing colours properly → SVG indicators not changing colours properly for background tabs(other tabs)
This sounds like a duplicate of bug 1404495.
(In reply to Dão Gottwald [::dao] from comment #2)
> This sounds like a duplicate of bug 1404495.

It's fixed according to that bug but still the indicators do not change colours for background tabs(circling indicators one had two animation to show this on other tabs too ie connecting & loading)
Meant reverse circle while connecting and blue one while loading and this was very useful info.

Current one has no info for background one's
See Also: → 1404495
Whiteboard: [photon-animation][triage]
Component: Tabbed Browser → Theme
What theme are you using? What color is your titlebar?
Flags: needinfo?(shellye5)
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #5)
> What theme are you using? What color is your titlebar?

Default or dark theme.

Light theme seems to work fine!
Flags: needinfo?(shellye5) → needinfo?(jaws)
Bug 1396062 made it so that we will show white as the loading state and grey as the connecting state if "bright text" is being used (dark theme and potentially default depending on your window titlebar color).

What color is your titlebar?
Flags: needinfo?(jaws)
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #7)
> Bug 1396062 made it so that we will show white as the loading state and grey
> as the connecting state if "bright text" is being used (dark theme and
> potentially default depending on your window titlebar color).
> 
> What color is your titlebar?

can see the white in dark theme but not always, default & light it's always grey(not selected tab but the other tabs)

its default colour in win10 which firefox provides (no title bar accent colour)
https://bug1408079.bmoattachments.org/attachment.cgi?id=8917908

only prefs changed are

no fav icons, mintabwidth =85

compact density
@jaws

might be white dots but still look like grey,
Not sure though.
Can it be some other variation? It's hard to differentiate (if it switches from grey to white)
Maybe grey to black?
Default profile with default theme & compact mode.
Sam, can you look in to this?
Flags: needinfo?(sfoster)
Priority: -- → P3
Whiteboard: [photon-animation][triage] → [reserve-photon-animation]
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #11)
> Sam, can you look in to this?

Sure, I'll take a look.
Assignee: nobody → sfoster
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(sfoster)
Priority: P3 → P1
I'm having trouble reproducing this. Here's what I'm trying: 

* Nightly, in win10:
* Open a bunch of tabs (to real websites, not just about:newtab)
* Close browser (with pref to restore tabs when starting)
* Open browser, and ctrl+tab through the tabs to trigger their starting to load (they won't load at all while in the background otherwise)

I'm seeing the expected white loading indicator for the background tabs. In the dark and default theme. Any suggestions :shellye?
Flags: needinfo?(shellye5)
(In reply to Sam Foster [:sfoster] from comment #13)
> I'm having trouble reproducing this. Here's what I'm trying: 
> 
> * Nightly, in win10:
> * Open a bunch of tabs (to real websites, not just about:newtab)
> * Close browser (with pref to restore tabs when starting)
> * Open browser, and ctrl+tab through the tabs to trigger their starting to
> load (they won't load at all while in the background otherwise)
> 
> I'm seeing the expected white loading indicator for the background tabs. In
> the dark and default theme. Any suggestions :shellye?

can you try

open few bookmarks together say 20 and don't switch tabs just look

sometimes they stay grey(usually on slow network) if they don't switch/connect quickly and sometimes the difference is not noticeable(like grey to blue)

but if you guys feel it okay then no problem.
Flags: needinfo?(shellye5) → needinfo?(sfoster)
plus they are blue in light theme

white in default and dark theme
(In reply to shellye from comment #14)
> can you try
> 
> open few bookmarks together say 20 and don't switch tabs just look

This doesn't make sense to me. As I understand it we don't attempt to load background tabs until they have been selected/brought into the foreground. Maybe I'm picturing this wrong?
Flags: needinfo?(sfoster)
(In reply to Sam Foster [:sfoster] from comment #16)
> (In reply to shellye from comment #14)
> > can you try
> > 
> > open few bookmarks together say 20 and don't switch tabs just look
> 
> This doesn't make sense to me. As I understand it we don't attempt to load
> background tabs until they have been selected/brought into the foreground.
> Maybe I'm picturing this wrong?

Yes, you are picturing this wrong. :) As opposed to session restore, we load bookmarks or any other links right away, not on demand.
Ok, so what I'm seeing is that when the tabs have a light background we show the grey dot for busy (connecting) and blue for progress/loading. When brighttext is applied for dark tabs (dark theme, or title bar off so the tabs use a dark title bar color) the dots are grey and white respectively. As the fill is at 70% opacity, the state change is pretty subtle. The reporter's expectation is that they should be blue. I'm inclined to agree that the difference is a bit hard to spot, and as Asa points out in bug 1404495, this is valuable information especially on slower connections.  

It seems like this was discussed at some length in bug 1396062, and white was landed on for the progress color as the blue was hard to differentiate against a blue background. So just switching back to blue is not a solution. It seems like the options are 

* to tweak colors (where we are constrained because of all the variations this needs to work under)
* adjust opacity/contrast
* adjust the image and/or animation. E.g using a hollow dot for connecting and a filled dot for loading. 
* or, of course to decide this is good-enough as-is and wontfix. 

Seems like a UX call. Eric/Amy?
Flags: needinfo?(epang)
Flags: needinfo?(amlee)
(In reply to Sam Foster [:sfoster] from comment #18)
> Ok, so what I'm seeing is that when the tabs have a light background we show
> the grey dot for busy (connecting) and blue for progress/loading. When
> brighttext is applied for dark tabs (dark theme, or title bar off so the
> tabs use a dark title bar color) the dots are grey and white respectively.
> As the fill is at 70% opacity, the state change is pretty subtle. The
> reporter's expectation is that they should be blue. I'm inclined to agree
> that the difference is a bit hard to spot, and as Asa points out in bug
> 1404495, this is valuable information especially on slower connections.  
> 
> It seems like this was discussed at some length in bug 1396062, and white
> was landed on for the progress color as the blue was hard to differentiate
> against a blue background. So just switching back to blue is not a solution.
> It seems like the options are 
> 
> * to tweak colors (where we are constrained because of all the variations
> this needs to work under)
> * adjust opacity/contrast
> * adjust the image and/or animation. E.g using a hollow dot for connecting
> and a filled dot for loading. 
> * or, of course to decide this is good-enough as-is and wontfix. 
> 
> Seems like a UX call. Eric/Amy?

The ideal situation would be too keep the base colours consistent (the brightness/contrast can change). 
Grey (connecting) > blue (loading). Higher opacity on the selected tab and lower on background tabs.

But then we run into the problem of title bars with blue background tabs.  Is there anyway we can check the title bar colour and only divert from blue when the loading dot isn't visible as opposed to changing it for all cases?
Flags: needinfo?(sfoster)
Flags: needinfo?(jaws)
Flags: needinfo?(epang)
Flags: needinfo?(amlee)
Can we just use a lighter blue like #bbbbff?
(In reply to Dão Gottwald [::dao] from comment #20)
> Can we just use a lighter blue like #bbbbff?

If the graphic solution is out, I'm in favor of a simpler solution like this if at all possible. We have simplified the issue of different color and brightness toolbars down to a brighttext boolean. ISTM that handling certain colors in different ways is a slippery slope.
Flags: needinfo?(sfoster)
(In reply to Sam Foster [:sfoster] from comment #21)
> (In reply to Dão Gottwald [::dao] from comment #20)
> > Can we just use a lighter blue like #bbbbff?
> 
> If the graphic solution is out, I'm in favor of a simpler solution like this
> if at all possible. We have simplified the issue of different color and
> brightness toolbars down to a brighttext boolean. ISTM that handling certain
> colors in different ways is a slippery slope.

Makes sense to me. Eric, thoughts?
Flags: needinfo?(epang)
#bbbbff would work except for the cases where the titlebar color is #bbbbff (or something close). Let's try it though and see how it looks. If this is gonna uplift to 57 we can't do anything drastic anyways.
Flags: needinfo?(jaws)
attachment 8925176 [details] looks a little better to me. Its still subtle, but I think an improvement? 

pushed to try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b3338da42854bb5ad536fc392850bf6bdf14d131
Attachment #8925176 - Flags: review?(dao+bmo)
(In reply to Sam Foster [:sfoster] from comment #25)
> attachment 8925176 [details] looks a little better to me. Its still subtle,
> but I think an improvement? 
> 
> pushed to try:
> https://treeherder.mozilla.org/#/
> jobs?repo=try&revision=b3338da42854bb5ad536fc392850bf6bdf14d131

just feedback

subtle blue looks nice but can it change from deep grey to subtle bright blue instead of grey to subtle blue?
so it's easy to see the state change of connection?
Flags: needinfo?(sfoster)
Comment on attachment 8925176 [details]
Bug 1408007 - Update tab loading throbber color for in-active tabs in darker themes

https://reviewboard.mozilla.org/r/196414/#review201834
Attachment #8925176 - Flags: review?(dao+bmo) → review+
(In reply to shellye from comment #26)
> just feedback
> 
> subtle blue looks nice but can it change from deep grey to subtle bright
> blue instead of grey to subtle blue?
> so it's easy to see the state change of connection?

We can't use a darker blue here because of bug 1396062, so for now at least this needs to be a compromise.
Flags: needinfo?(sfoster)
Pushed by sfoster@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/565d98335e7e
Update tab loading throbber color for in-active tabs in darker themes r=dao
(In reply to Sam Foster [:sfoster] from comment #28)
> (In reply to shellye from comment #26)
> > just feedback
> > 
> > subtle blue looks nice but can it change from deep grey to subtle bright
> > blue instead of grey to subtle blue?
> > so it's easy to see the state change of connection?
> 
> We can't use a darker blue here because of bug 1396062, so for now at least
> this needs to be a compromise.


Can we try these updated colours? Currently the light blue looks closer to lavender to me and doesn't really fit into the Photon colour palette.

Also, I agree with Shellye that the grey should be darker so the 2 states are easier to be distinguished.

Blue: #84c1ff
Grey: #717171

Thanks!
Flags: needinfo?(epang) → needinfo?(sfoster)
https://hg.mozilla.org/mozilla-central/rev/565d98335e7e
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 58
Blocks: 1415019
> Can we try these updated colours? Currently the light blue looks closer to
> lavender to me and doesn't really fit into the Photon colour palette.

Sorry Eric, I had already pushed my patch when this comment came in. I've opened bug 1415019 to follow up on these color choices.
Flags: needinfo?(sfoster)
(In reply to Sam Foster [:sfoster] from comment #32)
> > Can we try these updated colours? Currently the light blue looks closer to
> > lavender to me and doesn't really fit into the Photon colour palette.
> 
> Sorry Eric, I had already pushed my patch when this comment came in. I've
> opened bug 1415019 to follow up on these color choices.

Thanks Sam!
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: