Steps to reproduce
[LegacyWindowAlias] extended attribute in WebIDL
webkitURL in window, like Chromium and WebKit, but in a different way. The test fails because the property is enumerable in EdgeHTML. (I haven’t checked if there are other differences, but the test checks the relevant aspects.) This should be changed to follow the requirements for LegacyWindowAlias to be interoperable with Chromium/WebKit.
Result in Edge for /url/interfaces.any.html:
URL interface: legacy window alias FAIL assert_false: webkitURL is enumerable expected false got true
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “James M.”
Changed Assigned To to “Travis L.”
Changed Status to “Confirmed”
Changed Title from “window.webkitURL should not be enumerable / implement WebIDL [LegacyWindowAlias]” to “window.webkitURL should not be enumerable / implement WebIDL [LegacyWindowAlias]”
Changed Assigned To from “Travis L.” to “Kris K.”
Changed Status from “Confirmed” to “Fixed”
Changed Status from “Fixed” to “Fixed, not yet flighted”
Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and will be available in an upcoming build.
The MS Edge Team