When creating a new pref, it is not discover-able how to create it.
Categories
(Firefox :: Settings UI, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | --- | unaffected |
firefox67 | --- | affected |
People
(Reporter: alice0775, Unassigned)
References
(Blocks 1 open bug)
Details
it is bad UI
Comment 1•6 years ago
|
||
Can you clarify?
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to :Paolo Amadini from comment #1)
Can you clarify?
Sorry, I changed summary.
There are no description in the placeholder.
There are no context menu about creating a new pref.
Comment 3•6 years ago
|
||
I agree that if the page is approached specifically with the task of adding a new preference in mind, it might be unclear what the next step is when the search text box is shown.
While a better interface might have a separate section to add new preferences, updating the text in the placeholder might indeed help for the essential interface we've implemented here.
Updated•6 years ago
|
Comment 4•6 years ago
|
||
:paolo, is this a regression or an enhancement request? If it is a regression, do we have a regression range?
Comment 5•6 years ago
|
||
As a "future goal", I proposed a button opening a modal in the mockup.
Maybe it would be worth to implement this change before the beta version is released.
Paolo: How difficult is it, to check if a modal is opened etc? You said that this would be rather difficult.
Comment 6•6 years ago
|
||
(In reply to Neha Kochar [:neha] from comment #4)
:paolo, is this a regression or an enhancement request?
Enhancement request.
(In reply to :Matthias Kammüller from comment #5)
Paolo: How difficult is it, to check if a modal is opened etc? You said that this would be rather difficult.
Yes, as we discussed before this would be quite difficult, and I would do it for this page only if we need the same support for other in-content pages.
For the moment, updating the text in the placeholder should work. We might do this as part of bug 1524779 so we only change the string once.
Description
•