Add bug reports from WebKit and Firefox #11
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The two Firefox bugs seem to be the only ones which actually affect Firefox users. There's also bug 1740721, but that one seems more like a bug report filed after performing differential testing between browsers.
Bug 1797223 is also kind of interesting for cross-browser compatibility: A website was using
"CST"as a time zone identifier."CST"isn't a valid IANA/CLDR time zone identifier, so it should be rejected by implementations, but ICU actually supports"CST"for backward compatibility reasons. So when implementations directly call ICU without any additional pre- or post-processing to handle ICU zones,"CST"is incorrectly accepted.Not sure if it's worth to document bug 1679532 or bug 1802942, which are both examples where the Windows time zone identifier to IANA/CLDR time zone identifier mapping wasn't working correctly. (The mapping is defined in CLDR at https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZones.xml.) Bug 1802942 is probably still an issue, at least the comments in the Windows Daylight Saving Time & Time Zone blog indicate that some Windows users in Mexico still can't select their correct time zone, but I can't verify this right now.