-
Notifications
You must be signed in to change notification settings - Fork 81
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
type attribute is valid for more than just input #45
Comments
You are right! I am a bit conflicted on this, I like that |
Do you have any suggestions on what should be the the property? I have a couple myself but I don't care which one gets in because I think I need to make a choice and if it is really bad (I doubt it) then it can be re-worked later I am thinking
Even with these, @cmeeren @MangelMaxime what do you think? |
Of those, I like
I suggest dropping You could also have a |
|
@cmeeren I like this idea because it is not good if we keep both |
Looking at the MDN HTML attribute reference, I see that the
type
attribute is valid not only forinput
, but also for e.g.button
andmenu
. Thebutton
values are (at the time of writing) a subset of theinput
values, but themenu
props are currently not covered.type
is also a free-text attribute forembed
,source
,object
, andstyle
(containing MIME types).In any case, it might be weird calling it
inputType
when it's relevant for more than justinput
.Related: #13 and #43
The text was updated successfully, but these errors were encountered: