RESOLVED CONFIGURATION CHANGED Bug 256430
[css-transforms-2] ::before pseudo element does not participate in 3d rendering context extended by parent
https://bugs.webkit.org/show_bug.cgi?id=256430
Summary [css-transforms-2] ::before pseudo element does not participate in 3d renderi...
Johannes Odland
Reported 2023-05-07 10:22:35 PDT
Created attachment 466262 [details] Screengrab of the issue ::before and ::after pseudo elements are not included in the 3d rendering context extended by the parent element. Steps to reproduce: 1. Open test on https://johannesodland.github.io/browserbugs/2023/safari-3d-rendering-context-pseudo-element-issue.html Expected result: Both borders in the test are drawn in the same position, with the red border hidden behind the green border. Actual result: The border of the ::before element is not participating in the 3d rendering context, and is not perspective transformed. The borders of the two elements are drawn in different positions, and both are visible.
Attachments
Screengrab of the issue (18.03 KB, image/png)
2023-05-07 10:22 PDT, Johannes Odland
no flags
Expected result (13.30 KB, image/png)
2023-05-07 10:23 PDT, Johannes Odland
no flags
Johannes Odland
Comment 1 2023-05-07 10:23:26 PDT
Created attachment 466263 [details] Expected result
Ahmad Saleem
Comment 2 2023-05-08 02:54:08 PDT
I am not able to reproduce this bug in Safari Technology Preview 169. Can you try to see if this is reproducible for you in STP169?
Johannes Odland
Comment 3 2023-05-08 03:02:13 PDT
(In reply to Ahmad Saleem from comment #2) > I am not able to reproduce this bug in Safari Technology Preview 169. > > Can you try to see if this is reproducible for you in STP169? Tested on TP169 now. The issue seems to be resolved.
Ahmad Saleem
Comment 4 2023-05-08 03:03:20 PDT
(In reply to Johannes Odland from comment #3) > (In reply to Ahmad Saleem from comment #2) > > I am not able to reproduce this bug in Safari Technology Preview 169. > > > > Can you try to see if this is reproducible for you in STP169? > > Tested on TP169 now. The issue seems to be resolved. Thanks for confirming. Marking this as "RESOLVED CONFIGURATION CHANGED", when it will land in Safari release version, I don't have any information. :-)
Note You need to log in before you can comment on or make changes to this bug.