-
Notifications
You must be signed in to change notification settings - Fork 16
New core element suggestion: <core-form> #15
Comments
I've been working on something like this, stay tuned. |
Also, check out: https://github.com/garstasio/ajax-form |
Great! I'll keep an eye out. Ajax-form looks interesting as well. |
Hey, the ajax-form WebComponent was really useful. Thanks. :D |
@sjmiles any updates on core-form? |
@chrisconover I think there was initially an attempt to do this in the easyform repo, but that seems to have stalled in September. Is there something missing from ajax-form? That seems to be the recommended element to use for such a thing going forward. Disclaimer: I'm the author of ajax-form. |
Anything new in Polymer 1.0.0 as an alternative for this ? |
We've added iron-form as a Polymer 1.0 element. It's brand new, so it would be awesome if you could take it for a spin and tell us how it fares :) |
I wasn't sure the best place to put this suggestion, so I'm starting here :)
One feature I like about Angular is how easy it is to disable a submit button if a form has any invalid inputs.
Since
<core-input>
already has theinvalid
boolean attribute if an input has therequired
orvalidate
attributes set / falsy, it seems like it wouldn't be too hard to create a<core-form>
element to replace a standard<form>
that would observe all it's inputs and aggregate their invalid attributes to it's owninvalid
attribute.I noticed while reviewing the Topeka project they currently list all the individual inputs on whether to show the "check" button. Since it's using a
<core-selector>
for the avatar selection, I'm not sure how best that would tie into a<core-form>
parent tag.https://github.com/Polymer/topeka-elements/blob/master/topeka-profile.html#L160
Thoughts?
The text was updated successfully, but these errors were encountered: