Intent to implement and ship: force flattening of transform-style:preserve-3d when opacity is applied
52 views
Skip to first unread message
Matt Woodrow
unread,
Jul 1, 2016, 7:42:46 AM7/1/16
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dev-pl...@lists.mozilla.org
Summary:
The editors draft of the 3d transforms spec [1] has been updated to say
that we need to flatten preserve-3d when the element also has an opacity
of < 1, whereas the previous spec [2] made no mention of opacity.
The current behaviour (in Gecko, WebKit and blink) is to drop the
'group' nature of opacity, and propagate the opacity effect down on to
the leaves of the preserve-3d tree. This is non-intuitive, not specified
at all, and has slightly differently rendering in all browsers (based on
the specifics of what compositable layers get created I believe - see
layout/reftests/opacity-preserve3d-N.html reftests).
The blink team intend to change their behaviour to match the new spec,
even though it might break webcompat in some cases. The initial
www-style discussion [3] and their intent to implement thread [4] covers
their motivations for wanting to do this.
Given that the existing behaviour appears to be used incredibly rarely
[5] and that it moves us to well specified behaviour that is easy to
conform to, then I think we should do the same.