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

[fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D

From: Simon Pieters via GitHub <sysbot+gh@w3.org>
Date: Fri, 12 May 2017 08:47:39 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-228226585-1494578858-sysbot+gh@w3.org>
zcorpan has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D ==
https://drafts.fxtf.org/geometry/#dommatrix-attributes

> The isIdentity attribute must return true if m12 element, m13 element, m14 element, m21 element, m23 element, m24 element, m31 element, m32 element, m34 element, m41 element, m42 element, m43 element are 0  and m11 element, m22 element, m33 element, m44 element are 1\. Otherwise it must return false\.

Should this treat 0 and -0 as equal or different? Also for the logic for `is2D`...

https://drafts.fxtf.org/geometry/#webidl-unrestricted-double-same treats them as different, but that's more of a side-effect of the definition; the purpose was to treat NaN as equal to NaN. This could be changed to check for NaN specifically, and then doing an equality check where 0 and -0 are equal.

Opinions?

Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/152 using your GitHub account
Received on Friday, 12 May 2017 08:47:46 UTC

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