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

Don't set custom element state redundantly #253

Merged
merged 1 commit into from
Jun 1, 2016
Merged

Don't set custom element state redundantly #253

merged 1 commit into from
Jun 1, 2016

Conversation

domenic
Copy link
Member

@domenic domenic commented May 24, 2016

As of whatwg/html#1309, this is no longer necessary, as it is taken care of in the Construct(C) step.

Ideally don't merge this until that PR is merged.

@dominiccooney
Copy link

This LGTM.

Am I right in understanding that I can review the .bs files and ignore the HTML files in these PRs, because presumably the HTML file is generated by a tool?

@domenic
Copy link
Member Author

domenic commented May 31, 2016

Yep, exactly

@domenic
Copy link
Member Author

domenic commented May 31, 2016

@annevk I rebased this and the requisite HTML PR is merged so it should be good to go.

As of whatwg/html#1309, this is no longer necessary, as it is taken care of in the Construct(C) step.
@annevk annevk merged commit d077da1 into master Jun 1, 2016
@annevk annevk deleted the fix-ce-state branch June 1, 2016 11:22
@annevk
Copy link
Member

annevk commented Jun 1, 2016

I should not have attempted to fix the date. That took so much longer than anticipated...

@domenic domenic added the topic: custom elements Relates to custom elements (as defined in DOM and HTML) label Aug 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: custom elements Relates to custom elements (as defined in DOM and HTML)
Development

Successfully merging this pull request may close these issues.

3 participants