You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should the definition of getScreenCTM() make any comment on how 3D transforms on ancestor (HTML) elements should be handled? From my experimentation, it seems Chrome does attempt to support this (but is currently bugged). Firefox does not seem to have updated getScreenCTM() for SVG2 yet.
We do have another issue with vector-effects where this question came up. During the testing, it seemed like browsers do cross the pseudo-3D boundaries. Needs testing.
https://svgwg.org/svg2-draft/single-page.html#types-__svg__SVGGraphicsElement__getScreenCTM
Should the definition of
getScreenCTM()
make any comment on how 3D transforms on ancestor (HTML) elements should be handled? From my experimentation, it seems Chrome does attempt to support this (but is currently bugged). Firefox does not seem to have updatedgetScreenCTM()
for SVG2 yet.https://jsfiddle.net/r8887x05/1/
Chrome results (bug? scale transform is reflected in e and f, but not a and d):
Firefox results (ancestor transforms have no effect):
The text was updated successfully, but these errors were encountered: