Clarify how LayoutSVGResourceMarker's m_viewport interacts with refX/refY

Clarify how LayoutSVGResourceMarker's m_viewport interacts with refX/refY

Because refX and refY are in the coordinate space of each marker instance,
they are included in markerTransformation() instead of being part of the
marker viewport. As a result, only a viewport size is maintained in
LayoutSVGResourceMarker. This patch makes this distinction a little
clearer by refactoring m_viewport to m_viewportSize, as well as adding
some comments.

No new tests; no change in behavior.

Committed: https://crrev.com/db41bb454ddbdd14f8187e50638b64d290d64ccd
Cr-Commit-Position: refs/heads/master@{#437803}

[pdr., 2016-12-10 05:27:03]

The CQ bit was checked by pdr@chromium.org to run a CQ dry run

[pdr., 2016-12-10 05:27:08]

pdr@chromium.org changed reviewers:
+ fs@opera.com

[commit-bot: I haz the power, 2016-12-10 05:27:15]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-10 06:59:34]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-10 06:59:34]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[fs, 2016-12-10 09:12:00]

lgtm

[pdr., 2016-12-11 18:48:23]

The CQ bit was checked by pdr@chromium.org

[commit-bot: I haz the power, 2016-12-11 18:48:38]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-11 20:45:11]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481482103578410, "parent_rev":
"1b3cf5aeb5f27264bc8258cc0fb48f78fb413060", "commit_rev":
"2023e7a758019e086c2ee939bbcaa81676dd0faf"}

[commit-bot: I haz the power, 2016-12-11 20:45:44]

Description was changed from

==========
Clarify how LayoutSVGResourceMarker's m_viewport interacts with refX/refY

Because refX and refY are in the coordinate space of each marker instance,
they are included in markerTransformation() instead of being part of the
marker viewport. As a result, only a viewport size is maintained in
LayoutSVGResourceMarker. This patch makes this distinction a little
clearer by refactoring m_viewport to m_viewportSize, as well as adding
some comments.

No new tests; no change in behavior.
==========

to

==========
Clarify how LayoutSVGResourceMarker's m_viewport interacts with refX/refY

Because refX and refY are in the coordinate space of each marker instance,
they are included in markerTransformation() instead of being part of the
marker viewport. As a result, only a viewport size is maintained in
LayoutSVGResourceMarker. This patch makes this distinction a little
clearer by refactoring m_viewport to m_viewportSize, as well as adding
some comments.

No new tests; no change in behavior.

Review-Url: https://codereview.chromium.org/2567853002
==========

[commit-bot: I haz the power, 2016-12-11 20:45:45]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-12 15:10:03]

Description was changed from

==========
Clarify how LayoutSVGResourceMarker's m_viewport interacts with refX/refY

Because refX and refY are in the coordinate space of each marker instance,
they are included in markerTransformation() instead of being part of the
marker viewport. As a result, only a viewport size is maintained in
LayoutSVGResourceMarker. This patch makes this distinction a little
clearer by refactoring m_viewport to m_viewportSize, as well as adding
some comments.

No new tests; no change in behavior.

Review-Url: https://codereview.chromium.org/2567853002
==========

to

==========
Clarify how LayoutSVGResourceMarker's m_viewport interacts with refX/refY

Because refX and refY are in the coordinate space of each marker instance,
they are included in markerTransformation() instead of being part of the
marker viewport. As a result, only a viewport size is maintained in
LayoutSVGResourceMarker. This patch makes this distinction a little
clearer by refactoring m_viewport to m_viewportSize, as well as adding
some comments.

No new tests; no change in behavior.

Committed: https://crrev.com/db41bb454ddbdd14f8187e50638b64d290d64ccd
Cr-Commit-Position: refs/heads/master@{#437803}
==========

[commit-bot: I haz the power, 2016-12-12 15:10:04]

Patchset 1 (id:??) landed as
https://crrev.com/db41bb454ddbdd14f8187e50638b64d290d64ccd
Cr-Commit-Position: refs/heads/master@{#437803}