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
It seems the input type="date" standard does not specify whether or not any DOM events (click, keydown, etc) originating in the picker popup shadow DOM should be created with composed = true.
General developer documentation regarding UA generated events inside shadow DOM suggests that such events should be observable by event listeners in the regular DOM (i.e. light DOM) and therefore composed = true.
User expectation (I currently have a sample size of 1 (just myself)) is that the user interaction with the date picker popup is observable in the light DOM.
Are there any security concerns forbidding such a motion?
At the moment I'm not sure whether this is just a gap in the specification or should be treated as a bug in the tested browsers.
The text was updated successfully, but these errors were encountered:
Behavior for internal shadow roots is not specified to this extent. Furthermore, form controls and definitely their pickers are UI which makes requiring uniform behavior not really tenable.
The picker popup itself doesn't even (necessarily) live in the same process as the element, so events can't really propagate from there. And especially on mobile date pickers might be implemented using OS provided pickers.
What is the issue with the HTML Standard?
It seems the
input type="date"
standard does not specify whether or not any DOM events (click
,keydown
, etc) originating in the picker popup shadow DOM should be created withcomposed = true
.General developer documentation regarding UA generated events inside shadow DOM suggests that such events should be observable by event listeners in the regular DOM (i.e. light DOM) and therefore
composed = true
.A quick test with chrome and firefox showed that (in at least those two browsers) currently no shadow DOM events are propagated.
User expectation (I currently have a sample size of 1 (just myself)) is that the user interaction with the date picker popup is observable in the light DOM.
Are there any security concerns forbidding such a motion?
At the moment I'm not sure whether this is just a gap in the specification or should be treated as a bug in the tested browsers.
The text was updated successfully, but these errors were encountered: