Closed Bug 1921060 Opened 5 months ago Closed 25 days ago

Implement the full mute button spec

Categories

(Firefox :: Sidebar, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
136 Branch
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)

Duplicate of this bug: 1928482

Yulia has updated the spec (which was shared with Dao and Anna with any feedback incorporated already). We have new assets which can be found here.

See Also: → 1933479
Assignee: nobody → kcochrane
Status: NEW → ASSIGNED

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

Depends on: 1936086
Pushed by kcochrane@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5b573c874645 Implement full mute button spec r=desktop-theme-reviewers,tabbrowser-reviewers,dao,sessionstore-reviewers,sclements

Backed out for causing mda failures @ browser_mute_webAudio.js

TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabMediaIndicator/browser_mute_webAudio.js | Test timed out -
Flags: needinfo?(kcochrane)
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
Flags: needinfo?(kcochrane)
Regressions: 1936832
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
Regressions: 1936985
Regressions: 1937534
Regressions: 1937573
Regressions: 1937268
Regressions: 1937686

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?

Flags: needinfo?(kcochrane)

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.

Flags: needinfo?(kcochrane) → needinfo?(dao+bmo)

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. :/

Flags: needinfo?(dao+bmo)

Discussing with the team if we think it's necessary to revert changes for this.

Flags: needinfo?(nfay)
Flags: needinfo?(nfay) → needinfo?(aryx.bugmail)
Flags: needinfo?(aryx.bugmail)
Regressions: 1937957

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.

Backed out as requested for causing multiple regressions.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 135 Branch → ---
Status: REOPENED → ASSIGNED
Attachment #9444640 - Attachment is obsolete: true
Attachment #9441812 - Attachment description: Bug 1921060 - Implement full mute button spec → WIP: Bug 1921060 - Implement full mute button spec
Attachment #9441812 - Attachment description: WIP: Bug 1921060 - Implement full mute button spec → Bug 1921060 - Implement full mute button spec

(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.

Keywords: perf-alert
Pushed by kcochrane@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d448ac7b0d9e Implement full mute button spec r=desktop-theme-reviewers,tabbrowser-reviewers,dao,sessionstore-reviewers,sclements,sidebar-reviewers,fluent-reviewers,bolsson

Backed out for causing mochitests failures in browser_audioTabIcon.js.

Please also check these mochitests failures.

L.E. There are also these mochitests failiures.

Flags: needinfo?(kcochrane)
Flags: needinfo?(kcochrane)
Pushed by kcochrane@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2821188eb89d Implement full mute button spec r=desktop-theme-reviewers,tabbrowser-reviewers,dao,sessionstore-reviewers,sclements,sidebar-reviewers,fluent-reviewers,bolsson

Backed out for causing bc failures @ browser_multiselect_tabs_play.js

TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_play.js | Test timed out -

Bc failures @ browser_parsable_css.js

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. -
Flags: needinfo?(kcochrane)
Flags: needinfo?(kcochrane)
Pushed by kcochrane@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/34f28da9e8d5 Implement full mute button spec r=desktop-theme-reviewers,tabbrowser-reviewers,dao,sessionstore-reviewers,sclements,sidebar-reviewers,fluent-reviewers,bolsson
Status: ASSIGNED → RESOLVED
Closed: 2 months ago25 days ago
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
Regressions: 1943016
Regressions: 1943072
Regressions: 1944306
No longer regressions: 1944306
Regressions: 1945993
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: