- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Nov 2019 21:17:05 +0000
- To: public-css-archive@w3.org
I made the intentional choice to include both atan() and atan2() to coincide with JS; I've since made sure that the functions agree with JS in as many additional ways as possible, most particularly their corner-case behavior for NaN/Infinity/zero in various spots. Sticking close to JS for these functions is, I think, better. And as long as we're keeping atan2() around anyway (as your issue suggests we do), I don't think diverging from JS to allow atan() to copy the functionality makes a lot of sense; it doesn't add any new functionality, and there's no guarantee it would accord in all the corner cases with the 1-or-2-args versions of atan in other programming languages. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4485#issuecomment-554531731 using your GitHub account
Received on Friday, 15 November 2019 21:17:07 UTC