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 Firefox, you can't hit the <input type=text>, because it's ordered under the <html> box. In Blink and WebKit you can.
If you make the same test-case with two other elements, then Blink and WebKit agree with Gecko, as expected.
So I think the behavior in WebKit/Blink probably is a consequence of the background propagation to the viewport, but I still think this probably shouldn't work? I guess whether it works depends on whether you consider the box hit-testable, or the background area... If so, I should probably file WebKit and Blink issues, but since the spec for hit testing doesn't exist, I kinda want to confirm my intuition is correct.
This is probably changeable on Gecko's end if needed, but Gecko's behavior seems more consistent to me...
Consider this reduced test-case for Mozilla bug 1948937:
In Firefox, you can't hit the
<input type=text>
, because it's ordered under the<html>
box. In Blink and WebKit you can.If you make the same test-case with two other elements, then Blink and WebKit agree with Gecko, as expected.
So I think the behavior in WebKit/Blink probably is a consequence of the background propagation to the viewport, but I still think this probably shouldn't work? I guess whether it works depends on whether you consider the box hit-testable, or the background area... If so, I should probably file WebKit and Blink issues, but since the spec for hit testing doesn't exist, I kinda want to confirm my intuition is correct.
This is probably changeable on Gecko's end if needed, but Gecko's behavior seems more consistent to me...
cc @bfgeek @dbaron @smfr @tabatkins
The text was updated successfully, but these errors were encountered: