Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

test: fix ms edge failures #13739

Closed
wants to merge 2 commits into from

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Jan 11, 2016

This is a backport of #13686 to v1.4.x.
It includes exactly the same changes with the exception of the fixes to $sanitizeSpec, which do not apply to v1.4.x (and were omitted). Unit-tests pass on MS Edge.

Includes the following fixes (per component):

* `$sniffer`: Properly determine the expected `vendorPrefix` for MS Edge
* `input`: MS Edge does not support dates with years with more than 4 digits.
      Trying to set the value of an `input[datetime-local]` to `9999-12-31T23.59.59.999` throws an
      error (probably related to converting the date to one with a year with more than 4 digits,
      due to timezone offset).
* `$animateCss`: Although the detected `vendorPrefix` for MS Edge is "ms", it doesn't seem to
      recognize some vendor-prefixed CSS rules (e.g. `-ms-animation-*`). Other browsers (currently)
      recognize either vendor-prefixed rules only or both.
      Fixed by adding and retrieving styles using both prefixed and un-prefixed names.
* `$compile`: Skip failing `foreignObject` test on MS Edge.
      For unknown reasons, an `<svg>` element inside a `<foreignObject>` element on MS Edge has no
      size, causing the included `<circle>` element to also have no size and thus fails an
      assertion (relying on the element having a non-zero size).
      This seems to be an MS Edge issue; i.e. it is also reproducible without Angular.
      (Tested with MS Edge version 25.10586.0.0 on Windows 10.)

Closes angular#13686
@gkalpak
Copy link
Member Author

gkalpak commented Jan 11, 2016

Merged as da04571 and 0a641c0.

@gkalpak gkalpak closed this Jan 11, 2016
@gkalpak gkalpak deleted the backport-13686-to-v1.4.x branch January 13, 2016 08:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants