Z-index is not honored correctly on unknown elements
Reported by
wisniews...@gmail.com,
Sep 12 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36
Steps to reproduce the problem:
The attached testcase renders differently in Blink and WebKit than it does in Edge and Gecko.
What is the expected behavior?
The word "TEXT" should appear over the red block in the testcase.
What went wrong?
It seems that z-index is not correctly honored for unknown elements.
Did this work before? No
Does this work in other browsers? No
In the attached testcase, the red block is painted over the word "TEXT" in Blink and WebKit, but not in Gecko or Edge.
Based on the z-indices involved, Gecko and Edge are rendering this correctly.
This only happens when an unknown element is used rather than a standard HTML element ("custom-element" in this testcase).
Chrome version: 61.0.3163.79 Channel: stable
OS Version:
Flash Version:
I've reproduced the issue on Linux, Windows, and OSX.
It also reproduces for me all the way back to Chrome 23, so I do not suspect that it is a regression related to WebComponents/Custom Elements.
The issue was originally found as part of diagnosing https://webcompat.com/issues/9719
,
Sep 13 2017
Able to reproduce the issue using #62.0.3202.18 on Mac 10.12.6, Win 7, and Linux Ubuntu 14.04 and Android #62.0.3202.19 on 8.0.0 ; Pixel Build/OPR1 170623.027. Observed no "TEXT word is appeared on the page. Observing the same behavior since M50. Hence removing bisect label, please add it back if required. Please find the screenshot. Thanks!!
,
Sep 13 2017
,
Sep 18 2017
Removing <div></div> inside <custom-element> like below, working as expected.
<custom-element>
TEXT
</custom-element>
,
Apr 5 2018
Friendly ping. Is there any update on this issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by pbomm...@chromium.org
, Sep 12 2017Labels: Needs-Bisect Needs-Triage-63 OS-Android OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)