Implement the full mute button spec
Categories
(Firefox :: Sidebar, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox136 | --- | fixed |
People
(Reporter: muffinresearch, Assigned: kcochrane)
References
(Regressed 1 open bug)
Details
(Keywords: perf-alert, Whiteboard: [fidefe-sidebar])
Attachments
(1 file, 1 obsolete file)
Updated•5 months ago
|
Comment 2•3 months ago
|
||
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Comment 3•2 months ago
•
|
||
The a11y team (ayeddi specifically) has said we should keeping the inline audio/mute button not focusable (enduring it is included in the context menu for the tab and is a labeled button, as Close button is), because the muscle memory + efficiency of keyboard navigation + making it separately focusable would require some form of complex KB nav pattern that I am not sure we need to introduce here.
That’s being said, since playing audio may be annoying for any user, mouse users would be able to hover a Mute button without activating the tab (AFAIK), but we need to make sure the Mute button is (1) a programmatically button and (2) is labeled, so a screen reader user could use the screen-reader-provided shortcuts to find this button and activate it + voice control users would be able to call “Click Mute tab” or similar and have it muzzled. Similarly to the Close button for a tab
Assignee | ||
Comment 4•2 months ago
|
||
Backed out for causing mda failures @ browser_mute_webAudio.js
- Backout link
- Push with failures
- Failure Log
- Failure line:
TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabMediaIndicator/browser_mute_webAudio.js | Test timed out -
Assignee | ||
Updated•2 months ago
|
Comment 8•2 months ago
|
||
bugherder |
Comment 9•2 months ago
|
||
This caused a number of regression, some of which seem fairly serious. Do you have a good handle on or plan for most of these? Are you confident enough that they can be addressed in the current cycle (i.e. ideally before January 2, the soft code freeze for 135)? Should we consider backing this out and relanding later with the known issues addressed, to take away some of the pressure?
Assignee | ||
Comment 10•2 months ago
•
|
||
Bug 1936985 and bug 1937573 are already in review. The only one that seems like it might be tough to figure out is bug 1936985 given we currently have no way to determine from the stylesheets when a tab has reached min-width, but perhaps we can find a short-term workaround for this and file a follow-up to address that?
I'm working on bug 1937534 now. I think we just need to add back the old svg that had the circle built-in.
I've just left a comment on bug 1937268 to say that this will somewhat be improved when bug 1936985 lands as we're decreasing inline-margin around the audio button there, but we're not going to have as much as the tab title visible when a user has many tabs open and the audio button is present, that's just the nature of this new design requested by UX.
So as far as I can tell, that's just 3 bugs that are open and 2/3 are in review.
Comment 11•2 months ago
|
||
Still seems like a bit much to me, given that even those in review aren't necessarily close to the finish line. Reviews will be slower too, given bank holidays in various countries, plus I expect many folks will take some extra time off. I think I'll be available for 3, maximum 4 days. :/
Assignee | ||
Comment 12•2 months ago
•
|
||
Discussing with the team if we think it's necessary to revert changes for this.
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 13•2 months ago
|
||
After discussing with Product/UX/Engineering, we've decided it'd be best to back out these changes for now until we have more people around to discuss fixes for the regressions after the holidays.
Comment 14•2 months ago
|
||
Backed out as requested for causing multiple regressions.
Updated•2 months ago
|
Updated•2 months ago
|
Comment 15•2 months ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/7e1ede96105189f4b4815ed47379535b4c909c3f.
Assignee | ||
Comment 16•2 months ago
|
||
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 17•1 month ago
|
||
(In reply to Pulsebot from comment #7)
Pushed by kcochrane@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a2a3d6bf518f
Implement full mute button spec
r=desktop-theme-reviewers,tabbrowser-reviewers,dao,sessionstore-reviewers,
sclements
Perfherder has detected a awsy performance change from push a2a3d6bf518f49b2d6cda74bbac02ce48f074a9b.
Improvements:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
3% | Images Tabs closed [+30s, forced GC] | windows11-64-2009-shippable-qr | fission tp6 | 1,682,193.33 -> 1,630,880.00 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
You can run these tests on try with ./mach try perf --alert 43246
For more information on performance sheriffing please see our FAQ.
Comment hidden (obsolete) |
Comment 19•28 days ago
|
||
Comment 20•28 days ago
•
|
||
Backed out for causing mochitests failures in browser_audioTabIcon.js.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_audioTabIcon.js | Test timed out -
Please also check these mochitests failures.
L.E. There are also these mochitests failiures.
Assignee | ||
Updated•26 days ago
|
Comment 21•26 days ago
|
||
Comment 22•26 days ago
|
||
Backed out for causing bc failures @ browser_multiselect_tabs_play.js
- Backout link
- Push with failures
- Failure Log
- Failure line:
TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_play.js | Test timed out -
Bc failures @ browser_parsable_css.js
- Failure Log
- Failure line:
TEST-UNEXPECTED-FAIL | browser/base/content/test/static/browser_parsable_css.js | Got error message for chrome://browser/skin/tabbrowser/tabs.css: Error in parsing value for ‘background-image’. Declaration dropped. -
Assignee | ||
Updated•26 days ago
|
Comment 23•26 days ago
|
||
Comment 24•25 days ago
|
||
bugherder |
Description
•