Yes, this is precisely what we usually do. Of course, when vending something to the world at large, we will encounter folks who for whatever reason will insist on native <form>, so this is good to be aware of ahead of time. =P
On Wed, Apr 9, 2014 at 11:57 AM, 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. > > > 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/5ac3f65c-1b83-4997-888a-2cb5740d2d45%40googlegroups.com<https://groups.google.com/d/msgid/polymer-dev/5ac3f65c-1b83-4997-888a-2cb5740d2d45%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > 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/CAHbmOLb-094YuNFKEgZ7eVuEXWvA4DgGy6ui1-k04cL%2BjrM7hA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
