Remove mention of Firefox 'nan' vs. 'NaN' inconsistency. #38
Conversation
|
Thank you! I merged 2fde8b5 yesterday which removes another difference from the list. I would like to have it consistent so we should decide on removing it or adding a link to the issue etc. @terinjokes @domenic @frewsxcv do you have any opinions what might work best? |
|
I like removing in general, but maybe some kind of appendix of "recently fixed bugs" or similar would be interesting. Alternately we could just rely on the Git history. |
|
My preference is to remove it with good commit messages, and relying on the file's Git history. |
|
@frewsxcv is it OK for you to delete the entry and add a good commit message (maybe also mentioning in which FF version it was fixed and the link https://bugzilla.mozilla.org/show_bug.cgi?id=1239506) or is that completely impractical for you? |
As per https://bugzilla.mozilla.org/show_bug.cgi?id=1239506, Firefox will start printing 'NaN' instead of 'nan' when formatting `NaN` values starting in Firefox 47.
|
@robertkowalski Let me know how that looks |
frewsxcv
changed the title
|
LGTM thank you! 👍 |
As per https://bugzilla.mozilla.org/show_bug.cgi?id=1239506, Firefox will start printing 'NaN' instead of 'nan' when formatting `NaN` values starting in Firefox 47. PR: #38 PR-URL: #38 Reviewed-By: Robert Kowalski <rok@kowalski.gd>
|
merged as d9e224a |
No description provided.