W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > April 2018

[fxtf-drafts] [geometry] Matrix method inverse() doesn't suggest an inverse algorithm

From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
Date: Sun, 15 Apr 2018 17:35:05 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-314435328-1523813704-sysbot+gh@w3.org>
dirkschulze has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [geometry] Matrix method inverse() doesn't suggest an inverse algorithm ==
Original post by Adenilson Cavalcanti on https://www.w3.org/Bugs/Public/show_bug.cgi?id=26374:

>A quick look into wikipedia lists about 8 different methods for calculating a matrix inverse.
>
>It might be appropriated to suggest which algorithm should be used to help different UAs to come to similar results.

Response from @zcorpan 
>Dirk, Rik, do you know how to test this to tell which algorithm an implementation uses?

Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/271 using your GitHub account
Received on Sunday, 15 April 2018 17:35:07 UTC

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