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.

Sign up for GitHub

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

Jump to bottom

Why are unknown assertions a host decision? #102

Closed
annevk opened this issue Sep 30, 2020 · 2 comments · Fixed by #103
Closed

Why are unknown assertions a host decision? #102

annevk opened this issue Sep 30, 2020 · 2 comments · Fixed by #103

Comments

@annevk
Copy link
Member

annevk commented Sep 30, 2020

Given whatwg/html#5640 (comment) it seems we could devise a construct whereby the host indicates the assertions it supports and ECMAScript only gives it the intersection between those and the assertions found. That way hosts don't even have the option of failing upon unknown assertions and ensures more consistency across hosts.
@littledan
Copy link
Member

Sure, that sounds like a good idea to me. Does anyone want to write this up as a PR?

@dandclark dandclark mentioned this issue Nov 10, 2020
Merged
@dandclark
Copy link
Collaborator

I took a crack at this in #103.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@littledan @annevk @dandclark