Hi Folks, Long time listener, first time caller ;-) I'm working on a project in the dart version of Polymer but I think my question applies to web components in general and is not Dart specific. Are there any plans or perhaps work-arounds for tabindexing. Currently I have a component which in itself is a form with fields that contain tabindexes. And on its own it works great. However it appears that tabindexes break encapsulation of the component as when I have multiple instances of the component loaded, instead of respecting the tabindex on a component by component basis, it will instead navigate by hitting each tabindex=1 on the page, then each 2, etc.
Is my only option to completely re-layout my inputs so they are declared in the desired tabindex order and just drop the attribute altogether? Is there another work around or the chance of this being considered as something which will be added to the shadow dom of an object. See my related SO question here: http://stackoverflow.com/questions/21266016/how-can-tabindex-be-used-in-a-polymer-component-that-is-used-multiple-times-in-a Thanks for any feedback you can provide. Matt 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/de260af0-8a75-4fb8-8efc-3d737e078395%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
