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

Point to HTML for DOMStringList #385

Merged
merged 2 commits into from
Jan 13, 2017
Merged

Point to HTML for DOMStringList #385

merged 2 commits into from
Jan 13, 2017

Conversation

zcorpan
Copy link
Member

@zcorpan zcorpan commented Dec 15, 2016

@domenic
Copy link
Member

domenic commented Dec 15, 2016

Note that per whatwg/html#2179 we might want to move it back to HTML. Merging this seems fine in the meantime.

@annevk
Copy link
Member

annevk commented Dec 16, 2016

You think DOMStringList should be in HTML? I was thinking DOM, but I don't really care. Anyway, I'd rather we make a plan and then update all the specifications together than point temporarily to Indexed DB.

@domenic
Copy link
Member

domenic commented Dec 16, 2016

Since HTML is the one that would be using it, I was thinking HTML.

@annevk
Copy link
Member

annevk commented Dec 17, 2016

Sounds good. I'm happy to work on that unless someone else volunteers. Shall I just add a section after "2.6.2 Collections" called "2.6.3 The DOMStringList interface"?

@annevk
Copy link
Member

annevk commented Dec 17, 2016

whatwg/html#2192 has a PR for that.

@annevk annevk changed the title Point to IndexedDB for DOMStringList Point to HTML for DOMStringList Jan 10, 2017
@zcorpan
Copy link
Member Author

zcorpan commented Jan 13, 2017

LGTM

@annevk annevk merged commit 3fde24e into master Jan 13, 2017
@annevk annevk deleted the zcorpan/domstringlist-note branch January 13, 2017 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants