Replace bespoke preferences navigation sidebar with Category Navigation reusable component
Categories
(Firefox :: Settings UI, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: mconley, Assigned: fterdal, NeedInfo)
References
(Blocks 4 open bugs)
Details
(Whiteboard: [recomp])
Attachments
(1 file, 1 obsolete file)
kcochrane is working on making the page navigation sidebar from Firefox View be more reusable in bug 1850591. It offers a number of accessibility improvements over the bespoke one written for preferences (the heading for wayfinding, the notch to indicate the selected page), and has had a lot of recent attention from the UX / a11y teams. We should definitely consider switching about:preferences over to it once bug 1850591 is closed out and the reusable component is ready for use.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 1•7 months ago
|
||
This will be needed to complete the SRD work. The new nav will need to:
- include the search bar
- support displaying a notice when an enterprise policy is enabled
- support displaying a notice about the user's current profile
You can see examples of what these will look like together here.
Not sure about the sequencing here - maybe we want to do the nav switch behind a pref so that it's not visible until we've reorganized the settings pages.
Comment 2•3 months ago
|
||
FYI there was a Bug 2002923 that was cutting of the focus outline in an element in an area that appears to be getting replaced in this work. In the meantime, we've added a temporary hack to resolve it and just referenced this bug in that patch, so we remember to remove the hack when this work is complete. cc: mstriemer
Comment 3•1 month ago
|
||
I just filed bug 2013918 to add accesskeys. I made it depend on this since it could definitely be a follow-up, but it may make sense to treat that as the bug to add the accesskey support to moz-page-nav and then do the conversion here and use it right away after. No preference personally on the order
| Assignee | ||
Updated•1 month ago
|
Comment 4•1 month ago
|
||
A couple of things to note about this bug:
- we are no longer planning on displaying a profiles notice, so we only need to show the enterprise notice
- we have a nav-notice component that can be placed in the
subheadingslot ofmoz-page-navfor the enterprise notice (the component is probably a bit overbuilt/unnecessary now, but it seemed useful when we were gonna need to show themed profiles) - there's a pretty full working example of what the nav should look like here (storybook code can be found here)
I guess whether or not we put the new nav behind the SRD feature flag kinda comes down to whether or not we want to deal with test failures up front, and if we're ok with handling showing different navigation options based on the flag since the IA is changing in redesigned settings.
| Assignee | ||
Comment 5•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
Updated•29 days ago
|
Updated•29 days ago
|
Backed out for causing mochitest related failures at browser_aiFeatures_block_dialog.js and browser_cookies_exceptions.js
Backout link
Push with failures
Failure log(s) 1
Failure log(s) 2
Comment 10•17 days ago
|
||
| Assignee | ||
Comment 11•17 days ago
|
||
Thanks! I'll try and reproduce these locally and push again
| Assignee | ||
Comment 12•15 days ago
|
||
Updated•14 days ago
|
Comment 13•14 days ago
|
||
Comment 14•14 days ago
|
||
Backout for causing bc failures at preferences/tests/browser_usage_telemetry_support_link.js
Backout link
Push with failures
Failure log
Failure line TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_usage_telemetry_support_link.js | testSupportLinkTelemetry - Test timed out
Comment 15•14 days ago
•
|
||
Comment 16•14 days ago
|
||
Comment 17•14 days ago
|
||
Comment 18•14 days ago
|
||
Backed out for causing bc failures at browser_usage_telemetry.js
Backout link
Push with failures
Failure log(s)
Comment 19•13 days ago
|
||
Hi, @Finn, it also causes those failures
| Assignee | ||
Comment 20•13 days ago
|
||
Hi @rperta, thank you for the links and for your patience with this revision! I've just submitted another landing request after resolving those test failures. Let me know if you find any others.
Comment 21•13 days ago
|
||
Comment 22•13 days ago
|
||
Comment 23•13 days ago
|
||
Revert for causing bc failures on browser_syncedtabs_firefoxview.js.
Updated•10 days ago
|
Updated•10 days ago
|
| Assignee | ||
Comment 24•10 days ago
|
||
I believe my recent changes to moz-page-nav.css have fixed the browser_syncedtabs_firefoxview.js test failures. It looks like they were only failing on the tsan builds, and the failure isn't recurring (at least according to the latest Try).
I've just submitted another land request. Let me know if anything else requires fixing.
Comment 25•10 days ago
|
||
Comment 26•9 days ago
|
||
Comment 28•8 days ago
|
||
Comment 29•8 days ago
|
||
Comment 30•8 days ago
|
||
Backed out for causing bc failures @ browser_syncedtabs_firefoxview.js
Updated•8 days ago
|
Comment 31•8 days ago
|
||
Comment 32•7 days ago
|
||
| bugherder | ||
Description
•