Add HTMLInputElement.select() #2033

Open
jmm opened this Issue Oct 14, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@jmm

jmm commented Oct 14, 2015

The key thing to document is support for each state (@type value). For example, according to the WHATWG HTML5 spec it applies to type=number, while according to the W3C version of the spec it doesn't. type=number is my suggestion of where to start if it's not comprehensive.

Thanks!

@cvrebert

This comment has been minimized.

Show comment
Hide comment
@cvrebert

cvrebert Oct 16, 2015

Contributor

The non-Draft W3C version is always outdated.
http://www.w3.org/html/wg/drafts/html/master/semantics.html#input-type-attr-summary matches WHATWG.

Contributor

cvrebert commented Oct 16, 2015

The non-Draft W3C version is always outdated.
http://www.w3.org/html/wg/drafts/html/master/semantics.html#input-type-attr-summary matches WHATWG.

@jmm

This comment has been minimized.

Show comment
Hide comment
@jmm

jmm Oct 16, 2015

@cvrebert Ah, thank you! Wow, I thought I was confused before with WHATWG HTML5 and W3C HTML5. I've pretty much just been ignoring the W3C version in favor of WHATWG for years and didn't even realize W3C has an "HTML 5.1". It's a side issue obviously to documenting actual support, but that is great that they're in sync on that feature.

jmm commented Oct 16, 2015

@cvrebert Ah, thank you! Wow, I thought I was confused before with WHATWG HTML5 and W3C HTML5. I've pretty much just been ignoring the W3C version in favor of WHATWG for years and didn't even realize W3C has an "HTML 5.1". It's a side issue obviously to documenting actual support, but that is great that they're in sync on that feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment