Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(332)

Issue 2711503002: Compute a more correct "screen scope" transform for SVGSVGElement (Closed)

Created:
3 years, 10 months ago by fs
Modified:
3 years, 10 months ago
Reviewers:
pdr., Stephen Chennney
CC:
fs, blink-reviews, chromium-reviews, krit, fmalita+watch_chromium.org, gyuyoung2, kouhei+svg_chromium.org, pdr+svgwatchlist_chromium.org, rwlbuis, Stephen Chennney
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Compute a more correct "screen scope" transform for SVGSVGElement For getScreenCTM, only the position (translation) of the outermost svg element was computed - any additional transform data was dropped. Use LayoutObject::localToAbsoluteTransform to compute the full transform rather than just the position of the layout box. Since using this method works for any (attached) element, implement getScreenCTM without using computeCTM, and get rid of the ScreenScope variant of the latter. This also allows us to simplify SVGSVGElement::localCoordinateSpaceTransform a bit, and drop the CTMScope argument from the localCoordinateSpaceTransform declaration(s). It's not clear from [1] how elements which are not in the rendering tree (i.e has 'display: none' or similar) should be handled. With this implementation we will return an identity matrix in those cases, which doesn't seem unreasonable. (The option would be to return 'null', which is how elements not in the document should be treated, but we don't have that semantic implemented yet.) [1] https://svgwg.org/svg2-draft/types.html#__svg__SVGGraphicsElement__getScreenCTM BUG=678167 Review-Url: https://codereview.chromium.org/2711503002 Cr-Commit-Position: refs/heads/master@{#451938} Committed: https://chromium.googlesource.com/chromium/src/+/2ad2a9bf7205ec77843cf27a7964fda92df386b2

Patch Set 1 #

Patch Set 2 : Tweak test #

Messages

Total messages: 19 (13 generated)
fs
3 years, 10 months ago (2017-02-21 16:54:00 UTC) #9
Stephen Chennney
lgtm
3 years, 10 months ago (2017-02-21 18:46:54 UTC) #10
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2711503002/20001
3 years, 10 months ago (2017-02-21 21:56:53 UTC) #12
commit-bot: I haz the power
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
3 years, 10 months ago (2017-02-22 00:00:57 UTC) #14
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2711503002/20001
3 years, 10 months ago (2017-02-22 08:45:25 UTC) #16
commit-bot: I haz the power
3 years, 10 months ago (2017-02-22 08:51:10 UTC) #19
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/2ad2a9bf7205ec77843cf27a7964...

Powered by Google App Engine
This is Rietveld 408576698