- From: Peter Rushforth <notifications@github.com>
- Date: Tue, 09 Aug 2016 07:22:02 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 9 August 2016 14:22:39 UTC
Hi, I made a comment over in #110, perhaps that was out of place - sorry for the noise. I am working on a customized built-in <map> element in Polymer, and it is working quite nicely so far. I am a bit surprised at the neg on is=".. here. But mostly, I want to say that I want to provide enhanced behaviour for the <map> and <area> elements, which I guess are related/similar to <a> so I'm adding this comment here. My element demo can be found here: http://maps4html.github.io/Web-Map-Custom-Element/ or http://maps4html.github.io/Web-Map-Custom-Element/map-vs-web-map.html or a few other pages in that gh-pages branch. If attachShadowRoot is not permitted for these elements, I am thinking that the idea of a customized built-in <map> element is not going to be possible, is that correct? That would be a shame as it takes away a great fallback behaviour that I am looking for - that of the existing <map> and associated <area> elements. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/511#issuecomment-238568482
Received on Tuesday, 9 August 2016 14:22:39 UTC