On Wednesday, April 9, 2014, Günter Zöchbauer <[email protected]> wrote:
> I guess the most elegant way would be than to create a custom form element > <my-form> and provide it with the capabilities the DOM form element has and > in addition with support for custom input elements like core-input. > Custom input elements would just need to implement a specific interface. > I've been using custom interfaces for handling forms in this manner in my own custom elements and it works. It's not the most elegant of patterns :) I think Dominic's suggestion of inserting <input> fields into yet another Shadow DOM layer should work, but you'd need to craft some additional plumbing in order to hook the values up correctly. Scott, I wonder if there's any value in us putting together some samples of how to handle forms in custom elements just for reference. There may already be good core-* elements that demonstrate this. > > > On Wednesday, April 9, 2014 8:40:20 PM UTC+2, Scott Miles wrote: >> >> `core-input` was just born yesterday, and this was a tricky decision. >> It's not set in stone. >> >> 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/CAAKPnK9ZC2%3DuMbncgxfPp%3D5B6i2q2m9fdKFH4cY8z7kJ2DJuVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
