W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > August 2017

[fxtf-drafts] [geometry] Why does DOMMatrixReadOnly.scale() take an origin, but rotate() does not?

From: Paul LeBeau via GitHub <sysbot+gh@w3.org>
Date: Tue, 22 Aug 2017 14:42:25 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-251981276-1503412937-sysbot+gh@w3.org>
BigBadaboom has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [geometry] Why does DOMMatrixReadOnly.scale() take an origin, but rotate() does not? ==
I am in the process of implementing geometry-1.  I notice that, in `DOMMatrixReadOnly`, `scale()` takes an optional origin

    scale(scaleX, scaleY, scaleZ, originX, originY, originZ)

but `rotate()` does not

    rotate(rotX, rotY, rotZ)

Is that an oversight, or is there a reason for that?


Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/213 using your GitHub account
Received on Tuesday, 22 August 2017 14:42:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 November 2018 00:45:59 UTC