Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constructor called in one window that came from another window isn't finding the prototype WPT expects it to #25044

Open
pshaughn opened this issue Dec 3, 2019 · 1 comment

Comments

@pshaughn
Copy link
Member

@pshaughn pshaughn commented Dec 3, 2019

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.

@jdm jdm added this to To do in web-platform-test failures via automation Dec 3, 2019
@pshaughn
Copy link
Member Author

@pshaughn pshaughn commented Dec 3, 2019

#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
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.