- From: Hwang, Dongseong <dongseong.hwang@intel.com>
- Date: Thu, 20 Mar 2014 20:14:49 +0200
- To: Justin Novosad <junov@google.com>
- Cc: WHAT Working Group <whatwg@whatwg.org>
I totally agree on Justin.
On Thu, Mar 20, 2014 at 7:52 PM, Justin Novosad <junov@google.com> wrote:
> Hello all,
>
> The recently added currentTransform attribute on CanvasRenderingContext2D
> gives shared access to the rendering context's transform. By "shared", I
> mean:
>
> a) this code modifies the CTM:
> var matrix = context.currentTransform;
> matrix.a = 2;
>
> b) In this code, the second line modifies matrix:
> var matrix = context.currentTransform;
> context.scale(2, 2);
>
Sharing internal c++ object and javascript object seems to prevent further
optimization. SVG dev seems to feel that exposing SVG object is mistake
even if exposed SVG object is readonly.
For example,
interface SVGTransform {
readonly attribute SVGMatrix matrix;
}
> This behavior is probably not what most developers would expect.
> I would like to propose changing this to a getter method instead. We
> already have a setter method (setTransform).
>
> In another thread entitled "Canvas Path.addPath SVGMatrix not optimal",
> Dirk Schulze proposed using the name getCTM, which would be consistent with
> the SVGLocatable interface, where getCTM returns an SVGMatrix. On the other
> hand, we could call it getTransform to be consistent with the existing
> setTransform on CRC2D.
getTransform looks nice.
DS
Received on Thursday, 20 March 2014 18:19:41 UTC