Bug 79661

Summary: overflow: hidden disables backface-visibility: hidden
Product: WebKit Reporter: David DeSandro <desandrocodes>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Minor CC: ahmad.saleem792, bfulgham, remy.damour, shanestephens
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.7   
URL: http://bl.ocks.org/1921370
Attachments:
Description Flags
overflow hidden toggler with backface visibility none

David DeSandro
Reported 2012-02-27 05:01:23 PST
Created attachment 129017 [details] overflow hidden toggler with backface visibility Steps to reproduce: * Open the attached test case * Click "Toggle overflow: hidden" Expected result: * Blue "Back" face should still be visible Actual result: * Reversed red "Front" face is revealed. Notes: * Bug is present when parent's overflow: hidden interferes with child's backface-visibility: hidden. * Reproducible on Safari 5.1.3 and WebKit (r108935) on Mac OS X 10.7.3. * Possible duplicate of #43958
Attachments
overflow hidden toggler with backface visibility (1.78 KB, text/html)
2012-02-27 05:01 PST, David DeSandro 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Shane Stephens
Comment 1 2012-02-29 19:42:53 PST
Seems to: Fail some time ago (e.g. Safari 5) work _almost_ in head (tested in Chrome 19.0.1049.1 Canary, Chrome 19.0.1056.0 canary, Chrome 17.0.963.56) Fail in head (tested in WebKit nightly 109280).
remy.damour
Comment 2 2013-04-15 05:25:11 PDT
Similar issue on chrome v25.0.1364.160 overflow:hidden set on parent node interferes with -webkit-backface-visibility:hidden
Brent Fulgham
Comment 3 2022-07-12 16:57:37 PDT
WebKit, Blink, and Gecko have the same behavior on this test case. I don't believe there is a compatibility issue here.
Ahmad Saleem
Comment 4 2022-12-05 07:44:57 PST
(In reply to Brent Fulgham from comment #3) > WebKit, Blink, and Gecko have the same behavior on this test case. I don't > believe there is a compatibility issue here. Safari 16.1, Chrome Canary 110 and Firefox Nightly 109 agrees and work same on the attached testcase. Marking this as "RESOLVED CONFIGURATION CHANGED".
Note You need to log in before you can comment on or make changes to this bug.