Default devtools.inspector.rule-view.focusNextOnEnter to true
Categories
(DevTools :: Inspector: Rules, task)
Tracking
(firefox122 fixed, firefox123 fixed, firefox124 fixed)
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
Details
Attachments
(6 files, 4 obsolete files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
We got many feedback (e.g. on https://fxdx.dev/rules-view-enter-key/) of people frustrated by the new behavior since it's been there for a very long time (ever?) and it works that way in every browser devtools. Hence, we should revert to the original behavior (pre Bug 1861674).
It's still nice to have the pref for people who want the new behavior
Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Comment 4•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/7d511dc53852
https://hg.mozilla.org/mozilla-central/rev/959c3318d5c3
Assignee | ||
Comment 5•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200159
Updated•1 year ago
|
Assignee | ||
Comment 6•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200160
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Uplift Approval Request
- Steps to reproduce for manual QE testing: -
- Risk associated with taking this patch: low
- Needs manual QE test: no
- User impact if declined: This rolls back a keyboard behavior change in the Inspector that people are really frustrated with, as it changes a very old, standard-wide, pattern. If declined, people might switch to other browser devtools to develop/debug their websites
- Fix verified in Nightly: no
- Code covered by automated testing: yes
- Explanation of risk level: devtools only, basically backs out changes that were made 2 versions ago
- Is Android affected?: no
- String changes made/needed: -
Assignee | ||
Comment 8•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200159
Updated•1 year ago
|
Assignee | ||
Comment 9•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200160
Updated•1 year ago
|
Comment 10•1 year ago
|
||
Uplift Approval Request
- String changes made/needed: -
- Is Android affected?: no
- Needs manual QE test: no
- Risk associated with taking this patch: low
- Steps to reproduce for manual QE testing: -
- Explanation of risk level: devtools only, basically backs out changes that were made 2 versions ago
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- User impact if declined: This rolls back a keyboard behavior change in the Inspector that people are really frustrated with, as it changes a very old, standard-wide, pattern. If declined, people might switch to other browser devtools to develop/debug their websites
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 11•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200159
Updated•1 year ago
|
Assignee | ||
Comment 12•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200160
Updated•1 year ago
|
Comment 13•1 year ago
|
||
Uplift Approval Request
- Code covered by automated testing: yes
- User impact if declined: This rolls back a keyboard behavior change in the Inspector that people are really frustrated with, as it changes a very old, browsers-wide, pattern. If declined, people might switch to other browser devtools to develop/debug their websites
- Fix verified in Nightly: no
- Explanation of risk level: devtools only, basically backs out changes that were made 2 versions ago
- Steps to reproduce for manual QE testing: -
- Needs manual QE test: no
- Risk associated with taking this patch: low
- Is Android affected?: no
- String changes made/needed: -
Assignee | ||
Comment 14•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200159
Updated•1 year ago
|
Assignee | ||
Comment 15•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D200160
Updated•1 year ago
|
Comment 16•1 year ago
|
||
Uplift Approval Request
- Is Android affected?: no
- String changes made/needed: -
- Steps to reproduce for manual QE testing: -
- Needs manual QE test: no
- Risk associated with taking this patch: low
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- User impact if declined: This rolls back a keyboard behavior change in the Inspector that people are really frustrated with, as it changes a very old, browsers-wide, pattern. If declined, people might switch to other browser devtools to develop/debug their websites
- Explanation of risk level: devtools only, basically backs out changes that were made 2 versions ago
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 17•1 year ago
|
||
uplift |
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 18•1 year ago
|
||
uplift |
Description
•