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

Assert Symbol.toStringTag value in assert_class_string #23108

Closed

Conversation

shvaikalesh
Copy link
Member

@shvaikalesh shvaikalesh commented Apr 20, 2020

Superseded by #23140.

@domenic
Copy link
Member

domenic commented Apr 22, 2020

Please don't do this. We have significant interoperability issues with toStringTag (see whatwg/webidl#357), and don't want to change every assert_class_string to be based on a spec that doesn't have consensus, causing thousands of failures.

In fact any testing of toStringTag was specifically removed from assert_class_string some years ago, for this reason. (I can't find it in Git history since it appears to have been when testharness.js was still a submodule.)

@shvaikalesh
Copy link
Member Author

shvaikalesh commented Apr 22, 2020

Thank you for early feedback.

#23140 is even more preferable since it won't require syncing idlharness.js, which is a bit time-consuming for WebKit. Let's revisit this when we have the spec and 2 implementations ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants