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

Re: [fxtf-drafts] [geometry] Use of SameValueZero in "validate and fixup" doesn't make sense

From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
Date: Sat, 14 Apr 2018 13:17:44 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-381328601-1523711863-sysbot+gh@w3.org>

I have no idea, actually.  Constructing ES number values is probably simple enough...

-- 
GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/232#issuecomment-381328601 using your GitHub account

Received on Saturday, 14 April 2018 13:17:47 UTC

This message: [ Message body ]
Next message: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping"
Previous message: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [geometry] Difficulties with DOMMatrixReadOnly.is2D and other users of it"
Maybe in reply to: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [geometry] Use of SameValueZero in "validate and fixup" doesn't make sense"
Next in thread: Tab Atkins Jr. via GitHub: "Re: [fxtf-drafts] [geometry] Use of SameValueZero in "validate and fixup" doesn't make sense"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:22 UTC