Enable <input type="search"> in privileged documents
Categories
(Core :: Layout: Form Controls, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: tgiles, Assigned: tgiles)
References
(Blocks 1 open bug)
Details
(Whiteboard: [recomp])
Attachments
(4 files)
By enabling the <input type="search"> clear search button in privileged documents, regardless of the layout.forms.input-type-search.enabled pref, would be beneficial for the following reasons:
- It enables the moz-input-search component to be utilized in our UI without needing to create a duplicate implementation of the "clear search" functionality
- It allows us to consolidate and merge duplicate "search box with clear button" implementations:
- Firefox View
- Changing this one should also affect the sidebar, since the "Tabs from other devices" and "History" sections also use this particular search textbox.
- DevTools
- GeckoView
- Firefox View
- It increases visibility of the "clear search" button and any user experience issues with said input without impacting the entire web
- It moves us closer to being able to turn on
layout.forms.input-type-search.enabledby default (Bug 1654288)
We will need to address the previous cases before enabling the "clear search" button, otherwise each of the cases will have duplicate buttons that are styled differently.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Since this will result in duplicate UI elements in various places,
we should wait until the start of a new Nightly cycle to land the
change. See Bug 1936920, Bug 1956650, and Bug 1956812 for known places
where there will be duplicate clear search buttons.
Depends on D243387
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Backed out for causing bc failures @ browser_history_sidebar.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/2db065807374c10d5bbaab5640c01bfb8c5d11e1
Comment 4•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 5•1 year ago
|
||
Hey Emilio, following up on my request for some help debugging a devtools test failure that seems related to min-width calculations or some other related issue. The particular test I'm trying to fix is browser_webconsole_filter_buttons_overflow.js which passes without issue on central. However, once I introduce the "enable clear search button" patch, then the test fails because the layout of the webconsole view doesn't switch from "wide" to "narrow". Even if I remove (or use display: none) the previously existing button, I can't get the devtools webconsole view to wrap the search/filter input as expected.
You can easily reproduce this issue by setting layout.forms.input-type-search.enabled=true in the _webconsole.toml file at line 195.
Not sure what else to look into to figure out this issue and would appreciate your insight into this. Thanks!
Comment 6•1 year ago
|
||
Not just a leaf. This matches nsNumberControlFrame and co.
This goes all the way back to bug 558594 and fixes the test failures
described in comment 5.
I'll check if there's any WPT covering this.
Comment 7•1 year ago
|
||
Seems like a bug in the search control frame implementation!
Comment 9•1 year ago
|
||
| bugherder | ||
Comment 10•1 year ago
|
||
Err sorry thought you were going to land the actual enablement while at it. Probably should've landed it in a separate bug.
Updated•1 year ago
|
| Assignee | ||
Comment 11•1 year ago
|
||
In order to get this stack of patches to land, I needed to hide the
extra clear search button that is in fxview-search-textbox.
I needed to update browser_history_sidebar to access the anonymous
content element, the clear search button, in order to keep the test
as designed.
I needed to update browser_adopt_sidebar_from_opener due to the sidebar
width not being reset to the original value after running this test.
This narrow width would cause the next ran test to fail in non-obvious
ways.
Comment 12•1 year ago
|
||
Comment 13•1 year ago
|
||
Comment 14•1 year ago
|
||
Backed out for causing bc fails @ browser_history_firefoxview.js
| Assignee | ||
Comment 15•1 year ago
|
||
Since there isn't a separate fxview clear search button, the tests
needed to be updated to activate the clear search button that exists
in the HTMLInputElement.
Comment 16•1 year ago
|
||
Comment 17•1 year ago
|
||
Comment 18•1 year ago
|
||
Backed out for causing bc fails @ browser_history_firefoxview.js & browser_history_sidebar.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/fc99862302036c47353c398bb6a925b54962220a
Comment 19•1 year ago
|
||
Comment 20•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/1cdd656f5a5e
https://hg.mozilla.org/mozilla-central/rev/a2e9312df4d8
https://hg.mozilla.org/mozilla-central/rev/d8971955d303
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Description
•