The Manage Settings Option from the Callout 3 does not redirect the user to the correct option in about:preferences
Categories
(Firefox :: Settings UI, defect)
Tracking
()
People
(Reporter: rdoghi, Assigned: mstriemer)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Found in
- Nightly 138.0a1 (2023-08-25)
Affected versions
- Nightly 138.0a1 (2023-08-25)
Affected platforms
- All
Preconditions:
Have RC in the Sidebar.
Steps to reproduce
- Open the Review Checker in the Firefox Sidebar but do not optin.
- Close the Sidebar and Close the Firefox browser.
- Advance Time for 24 hours.
- Reach a product details page.
- Expand the Dismiss options dropdown from the RC callout.
- Click the Manage Settings option.
Expected result
- The user should be redirected to the "Recommend features as you browse" option in about:preferences.
Actual result
- The user is redirected to the beginning of the about:preferences page.
Regression range
Not Applicable
Comment 1•28 days ago
•
|
||
Looks like this is a more general issue with the preferences page being linked to from the split dismiss button. We're seeing it on other messages as well. about:preferences#general-cfrfeatures
doesn't work in nightly but works in release.
Comment 2•28 days ago
|
||
mozregression narrowed it to this pushlist. Based on reading the code, I believe this was regressed by bug 1951141. It seems that our items are created without a data-subcategory
. This is apparently because it's setting subcategory
and not data-subcategory
, which is what the function uses to scroll and highlight.
This looks like an easy fix, but before changing it to data-subcategory
let's ask Mark if there's anything relying on it being subcategory
.
Comment 3•28 days ago
|
||
Set release status flags based on info from the regressing bug 1951141
Comment 4•26 days ago
|
||
Updated•26 days ago
|
Comment 5•26 days ago
|
||
(In reply to Shane Hughes [:aminomancer] from comment #2)
This looks like an easy fix, but before changing it to
data-subcategory
let's ask Mark if there's anything relying on it beingsubcategory
.
Yeah I'm fairly sure this was just an oversight.
Updated•25 days ago
|
Comment 7•25 days ago
|
||
bugherder |
Reporter | ||
Comment 8•25 days ago
|
||
Verified as fixed in our latest Nightly 139.0a1 (2025-04-04)
Comment 9•25 days ago
|
||
The patch landed in nightly and beta is affected.
:Gijs, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox138
towontfix
.
For more information, please visit BugBot documentation.
Updated•25 days ago
|
Comment 10•25 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D244375
Updated•25 days ago
|
Comment 11•25 days ago
|
||
beta Uplift Approval Request
- User impact if declined: Broken review checker callout links
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: see comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: minor changes to how only a small part of prefs is generated, plus a more general change to how we scroll the prefs
- String changes made/needed: No
- Is Android affected?: no
Updated•23 days ago
|
Comment 12•23 days ago
|
||
uplift |
Updated•23 days ago
|
Reporter | ||
Comment 13•22 days ago
|
||
Verified as fixed in our latest Beta 138.0b4
Reporter | ||
Updated•22 days ago
|
Description
•