Closed Bug 1524073 Opened 5 years ago Closed 5 years ago

Showing all content of about:config requires user interaction after landing patch from bug #1521765

Categories

(Toolkit :: Preferences, defect)

66 Branch
x86_64
Windows 7
defect
Not set
major

Tracking

()

VERIFIED WONTFIX
Tracking Status
firefox-esr60 --- unaffected
firefox65 --- unaffected
firefox66 --- unaffected
firefox67 --- wontfix

People

(Reporter: Virtual, Unassigned)

References

Details

(4 keywords)

STR:

  1. Open about:config
  2. and see that you have to press ESC keyboard button to see it's all content,
    when in old about:config all content was already shown by default, no more user action was needed, while still having focus on Search text box.

Regression caused by:
bug #1521765

Has Regression Range: --- → yes
Has STR: --- → yes

This is by design.

I notice you filed a number of other bugs for every small change you noticed in about:config. I'd like to clarify that this is a new design and we've approached it from scratch, see the mailing list posts for details. If you're interested, sometimes there is more context on design decisions in resolved dependencies of bug 1493439.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX

This change makes about:config harder to access to users with disabilities and special needs, especially for users using mostly mouse, not keyboard. Please reconsider this, as for now I'm only seeing that it's to show dragon image. Thank you very much in advance for reply.

Flags: needinfo?(paolo.mozmail)

This was explained in the mailing list post, but the reason for requiring user interaction is performance. That said, I think the mouse-only use case you mentioned is worth considering, and I filed bug 1524779 to add a separate button that would also allow showing all preferences without requiring keyboard interaction. As noted there, this would also align with other design improvements. Thanks for mentioning that use case.

Flags: needinfo?(paolo.mozmail)

Thank you very much for reconsidering this!

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.