There are some relevant W3C issues for this: * https://github.com/w3c/csswg-drafts/issues/413 * https://github.com/w3c/csswg-drafts/issues/6320 * https://github.com/w3c/csswg-drafts/issues/6346
<rdar://problem/85197362>
Created attachment 445729 [details] Patch
Comment on attachment 445729 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=445729&action=review > Source/WebCore/platform/graphics/transforms/PerspectiveTransformOperation.h:68 > + return m_interoperabilityState == TransformInteropabilityEnabled ? std::max(1.0f, returnValue) : returnValue; Not sure if it's worth plumbing ScriptExecutionContext all the way through just to check the setting here. I bet we could do this without undue compat risk.
Created attachment 445848 [details] Patch
Created attachment 446028 [details] Patch
(In reply to Simon Fraser (smfr) from comment #3) > Comment on attachment 445729 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=445729&action=review > > > Source/WebCore/platform/graphics/transforms/PerspectiveTransformOperation.h:68 > > + return m_interoperabilityState == TransformInteropabilityEnabled ? std::max(1.0f, returnValue) : returnValue; > > Not sure if it's worth plumbing ScriptExecutionContext all the way through > just to check the setting here. I bet we could do this without undue compat > risk. Thanks for the review. I've updated the patch to remove the plumbing and also updated the WebKit-specific tests that were failing.
Created attachment 446131 [details] Patch
Committed r286591 (?): <https://commits.webkit.org/r286591> All reviewed patches have been landed. Closing bug and clearing flags on attachment 446131 [details].