On Tuesday, October 22, 2013 5:39:16 PM UTC-4, Joern Turner wrote: > > > >> >> Web Components are much simpler: they always have one name. The prefix is >> part of the name. A specific element can't appear in two places with >> different prefixes; there's no namespace URI. There's no declaration of the >> prefix anywhere. >> > Right - because they are simply part of HTML - so no mixing of namespaces. > However we'll see if this will hold in the long run when dozens of e.g. > layout components from different origins pop up and name clashes become > more likely. One day we probably need an answer to this or live with > clashes. >
Personally, I think they need to bind document.registerElement and HTMLImport <link /> tag. This way the page designer can set the name tag for conflicts. i.e. <link rel="import" href="component1.html" for="mine"> <link rel="import" href="component2.html" for="theirs"> <mine-toolbar/> <theirs-toolbar/> so when registerElement is called, it prepends the for with a dash, in the component.html files. The component writers are not going to know the ultimate goal of the plugin or even how it will be extended, but the end user page designer will. - Jeremy > 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/d7ee58e4-e40f-42bb-afeb-67a034d43616%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
