This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
test: fix ms edge failures #13686
Closed
Closed
test: fix ms edge failures #13686
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
846c0af
refct(privateMocks): remove unused argument from `createMockStyleShee…
gkalpak bee6650
test(sniffer): properly determine expected `vendorPrefix` for MS Edge
gkalpak 327efa7
test(input):fix failing test on MS Edge
gkalpak 0515451
test($sanitize): fix failing tests on MS Edge
gkalpak a798ebf
test($animateCss): fix failing animation tests on MS Edge
gkalpak ff44c1c
test($compile): skip failing `foreignObject` test on MS Edge
gkalpak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
an explanation would be nice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't feel like an explanation was required in the actual code, so I put it on the commit message instead. The problem is, I don't really know why MS Edge doesn't like the original Data, nor could I reproduce it independently (outside of the tests), but I figured it is not worth investigating further.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It probably has something to do with how MS Edge handles UTC -> local datetime conversion while overflowing 9999. E.g. with my UTC+2 timezone, the UTC value
9999-12-31T21:59:59.999
(which corresponds to9999-12-31T23:59:59.999
local time) is fine, but the UTC value9999-12-31T22:00:00.000
(which corresponds to+10000-01-01T00:00:00.000
local time) "confuses" MS Edge.It may also have something to do with ISO 8601 defaulting to min. 4 digits per year, but permitting the expansion of the year representation but only by prior agreement between the sender and the receiver (whatever that means).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This worries me...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked a little more into this: MS Edge does not seem to support years > 9999 after all.
(Demo: it's not possible to set the year to > 9999 on Edge)
So, I think this test fix is fine (since
9999
doesn't have any significant value for the test - we just need a later date).Yet, while investigating this, I realized that our internal implementation of date-family inputs, do not support years > 9999.
I will make an issue for that (unless it's so on purpose).