- From: Dirk Schulze <dschulze@adobe.com>
- Date: Thu, 4 Sep 2014 08:41:01 +0000
- To: FX <public-fx@w3.org>
Hi, It was brought up[1] that the inverse() method for DOMMatrix[2] does not specify the used algorithm. The bug report mentions different ways to compute the inverse of a matrix. Some include computing the determinant which was removed from the spec recently on request because of its potential numeric instability. The editors intentionally left the choice of the used algorithm to the user agents. There might be implementation details influencing the decision. With this email I seek for input from implementers: Should the editors continue to let implementations chose the used algorithm? Do implementations want or even need a specific algorithm? If implementations do want or need the algorithm, do you have a preference? Greetings, Dirk [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26374 [2] http://dev.w3.org/fxtf/geometry/#dom-dommatrixreadonly-inverse
Received on Thursday, 4 September 2014 08:41:31 UTC