Bug 79661 - overflow: hidden disables backface-visibility: hidden
Summary: overflow: hidden disables backface-visibility: hidden
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.7
: P2 Minor
Assignee: Nobody
URL: http://bl.ocks.org/1921370
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-27 05:01 PST by David DeSandro
Modified: 2022-12-05 07:44 PST (History)
4 users (show)

See Also:


Attachments
overflow hidden toggler with backface visibility (1.78 KB, text/html)
2012-02-27 05:01 PST, David DeSandro
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David DeSandro 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
Comment 1 Shane Stephens 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).
Comment 2 remy.damour 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
Comment 3 Brent Fulgham 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.
Comment 4 Ahmad Saleem 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".