Bug 44751

Summary:

3D clipping on reverse-ordered z-indices

Product:

WebKit

Reporter:

Aaron Wheeler <fightinjoe+webkit>

Component:

CSS

Assignee:

Brandon <brandonstewart>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

709922234, ahmad.saleem792, bfulgham, brandonstewart, karlcow, mattwoodrow, simon.fraser, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Mac (Intel)

OS:

OS X 10.6

URL:

http://gist.github.com/552970

Attachments:

Description	Flags
screenshot of bug	none
Test Case	none
rendering in safari, firefox, chrome	none

Aaron Wheeler

Reported 2010-08-27 00:22:51 PDT

Created attachment 65684 [details] screenshot of bug Clipping of 3d CSS rotations of an element occurs when a previous sibling in the DOM has a lower z-index than the element. For an example, see here: http://gist.github.com/552970

Attachments
screenshot of bug (19.39 KB, image/png) 2010-08-27 00:22 PDT, Aaron Wheeler	no flags	Details
Test Case (1.02 KB, text/html) 2022-07-12 13:32 PDT, Brent Fulgham	no flags	Details
rendering in safari, firefox, chrome (826.66 KB, image/png) 2025-04-17 02:36 PDT, Karl Dubost	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Brent Fulgham

Comment 1 2022-07-12 13:32:35 PDT

Created attachment 460822 [details] Test Case

Brent Fulgham

Comment 2 2022-07-12 13:32:56 PDT

This works properly in Firefox and Chrome, but fails in Safari.

Radar WebKit Bug Importer

Comment 3 2022-07-12 13:33:06 PDT

<rdar://problem/96907282>

Matt Woodrow

Comment 4 2022-09-01 14:41:55 PDT

This happens because WebKit considers the two elements to be sharing a 3d rendering context, and thus computes intersections in 3d space. The other two implementations consider only the element with preserve-3d to be creating a 3d rendering context, and so no intersections happen.

Ahmad Saleem

Comment 5 2025-04-17 01:25:41 PDT

All browsers are rendering this same (Safari Technology Preview 217, Chrome Canary 137 and Firefox Nightly 139). Seems to be fixed in Safari 18.4 as well. It seems to be fixed now. @Karl - want to double check?

Karl Dubost

Comment 6 2025-04-17 02:36:35 PDT

Created attachment 474941 [details] rendering in safari, firefox, chrome Chrome and Safari renders the same Firefox is different. But this differences are unrelated to this bug (and probably partially due to -webkit- prefixes. ) So this is solved

Note You need to log in before you can comment on or make changes to this bug.