You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In https://html.spec.whatwg.org/multipage/input.html#show-the-picker%2C-if-applicable, UI gets shown to the user representing the picker for either input or select elements. If those elements get removed from the DOM while the picker is shown (except for type=file apparently), the picker UI gets dismissed immediately in Chrome+Safari, but not Firefox (click the input within 2 seconds of loading the following data: URL):
Aligning on Chrome/Safari behavior here makes sense to me I think, so we should consider patching up that algorithm to hook into DOM and respond to the removal appropriately by dismissing the picker UI. The solution to this will likely come in the form of semi-handwavy text inside the existing algorithm (although something more procedural could be considered maybe).
While not strictly speaking observable to websites (although maybe it is through :open?), it probably makes sense to state something about expectations here.
What is the issue with the HTML Standard?
In https://html.spec.whatwg.org/multipage/input.html#show-the-picker%2C-if-applicable, UI gets shown to the user representing the picker for either
input
orselect
elements. If those elements get removed from the DOM while the picker is shown (except fortype=file
apparently), the picker UI gets dismissed immediately in Chrome+Safari, but not Firefox (click the input within 2 seconds of loading the followingdata:
URL):Aligning on Chrome/Safari behavior here makes sense to me I think, so we should consider patching up that algorithm to hook into DOM and respond to the removal appropriately by dismissing the picker UI. The solution to this will likely come in the form of semi-handwavy text inside the existing algorithm (although something more procedural could be considered maybe).
Context: I ran into this while working on whatwg/dom#1307.
The text was updated successfully, but these errors were encountered: