You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, the test itself probably could use type="textarea", but we don't check the type to determine if it can have children (we probably should, it would be simple since we use the type to determine the tag and if the tag is input, we should not allow children).
Activity
TheSharpieOne commentedon Feb 27, 2018
They should when the "input" is a
<select>or<textarea>, which theInputcomponent can render giventype="select"ortype="textarea"respectfully.jhsware commentedon Feb 27, 2018
The default input type is
textso the test should be something like this:<Input type="select">Yo!</Input>Are you sure
type="textarea"is allowed children? The React-clone Inferno.js complains if textarea has children.TheSharpieOne commentedon Feb 27, 2018
Sounds like a defect for inferno.
<textarea>is not a void element, it allows content within it. See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textareaYes, the test itself probably could use
type="textarea", but we don't check the type to determine if it can have children (we probably should, it would be simple since we use the type to determine thetagand if thetagis input, we should not allow children).jhsware commentedon Feb 27, 2018
React doesn't follow HTML-specs in that regard: https://reactjs.org/docs/forms.html
Only
<select>should have children from what I can tell.TheSharpieOne commentedon Feb 27, 2018
Yeah, looks like they are removing the ability for
<textarea>s to have children in react 17: react/react#11639jhsware commentedon Feb 27, 2018
I have made a port of Reactstrap to Inferno.js so I get stuck in the middle at times... :D