I did run some quick (successful) tests with paper-input.  Keep in mind 
that your paper-inputs must have a "name" attribute in order to be 
submitted along with other form fields inside of an ajax-form.  This 
requirement is consistent with the way a native form treats fields that 
lack a name attribute (it ignores them).  

ajax-form 1.0.0 will "submit" any custom element in the form if it contains 
a name attribute and has a value.  The next step is to respect any 
constraints attached to a custom form field element. 
 core/paper-input exposes an "invalid" property to determine if the field 
is valid.  In v 1.1.0, ajax-form will likely check this property on all 
custom form fields (in addition to validation checks iaja-form already runs 
on native form fields) to determine if the form can be "submitted".  It 
seems reasonable to carry this convention forward and expect all future 
custom form fields to contain an "invalid" property to make this 
determination as well.



On Friday, August 22, 2014 9:00:09 AM UTC-5, Rob Dodson wrote:
>
> Hey folks,
>
> Just wanted to put this on your radars. A lot of folks have asked how to 
> submit paper-inputs using the form element. Ray Nicholus, creator of 
> ajax-form, has recently added form support for any custom element that 
> has a name and value attribute 
> <https://github.com/garstasio/ajax-form/issues/19>. I'm running around on 
> conference wifi and haven't had a chance to take it for a spin yet, but I 
> *hope* this will help some of you get unstuck so you can start submitting 
> those sweet, sweet, paper-* elements to your backends. Please give it a 
> shot and comment on the issue if it doesn't work. Thanks!
>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/fac53ae1-b3ef-46ab-8b57-0b800e6d1daf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to