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
Feature request: Common super-type of input, select, textarea elements #12585
Comments
Added this to the M7 milestone. |
Should be able to add a common interface for these. Removed this from the M7 milestone. |
Issue #4113 has been merged into this issue. |
Added Community-StarterBug label. |
Basic API set that I believe would be on this: bool disabled; String name; bool get willValidate; bool checkValidity(); void setCustomValidity(String error); String get validationMessage; ValidityState get validity; Elements which this would apply to: button fieldset input keygen object output select textarea |
This comment was originally written by @budde377 It would be really nice to get String value in this as well, even through this might mean omitting some of the elements you mention. |
Removed Area-HTML label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
This issue was originally filed by @budde377
Right now if you want to iterate elements, containing a name and a value, in a form, you have to cast each element to its respective type or choose to ignore the types, which result in some problems when compiling (and/or running) the checked-mode dart2js produced javascript code.
A solution to this problem would be to create a common supertype to input, select and textarea, which contains their common properties.
The text was updated successfully, but these errors were encountered: