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

should incumbent settings object be relevant settings object? #53

Closed
equalsJeffH opened this issue Jan 8, 2017 · 3 comments
Closed

Comments

@equalsJeffH
Copy link
Collaborator

incumbent settings object is utilized in several places in the spec, although there's this warning in the HTML spec here (scroll down below the example):

Warning: The incumbent and entry concepts should not be used by new specifications, as they are excessively complicated and unintuitive to work with. We are working to remove almost all existing uses from the platform:​ see issue #1430 for incumbent, and issue #1431 for entry.

Should this spec be using the relevant settings object instead?

@domenic
Copy link

domenic commented Jan 8, 2017

Thanks for filing! This is very important to fix. I've added it to our master list at whatwg/html#1430.

@battre
Copy link
Collaborator

battre commented Feb 15, 2017

Talked to Mike, this should be current settings object.

@equalsJeffH
Copy link
Collaborator Author

in examining index.src.html in the master branch (at commit 1c700aa), it seems to me this issue has been fixed. yes?

@battre battre closed this as completed Jun 29, 2017
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

No branches or pull requests

3 participants