Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upConstructor called in one window that came from another window isn't finding the prototype WPT expects it to #25044
Labels
Projects
Comments
|
#25039 might share a cause, but that one is seeing constructors equal when they should be unequal and this one is the other way around. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WebIDL/ecmascript-binding/constructors.html fails various cases with messages like
expected object "[object DOMParserPrototype]" but got object "[object DOMParserPrototype]", the problem being that it's seeing the prototype that belongs to one global as opposed to another.https://wpt.fyi/results/WebIDL/ecmascript-binding/constructors.html?label=experimental&label=master&aligned Servo is not alone here; WPT's specific ideas about which prototype should be used when are not currently shared among non-Firefox browsers.