- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Aug 2013 17:06:39 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19870 --- Comment #14 from Elliott Sprehn <esprehn@gmail.com> --- (In reply to comment #13) > ... > > My first reaction to tying the desired behavior described above to ShadowDOM > is that it seems like an unfortunate coupling; what if I don't use ShadowDOM? > > Perhaps a scoped <base> element would make Morrita-san's approach more > general. > Yeah I don't think we should add magic arguments to ShadowRoot for templating.. smells like the <element> stuff we removed. I do like the idea of allowing <base> in a ShadowRoot, then polymer could be smart and put a <base> for the import origin in the custom element <template>. This is still going to be fraught with peril: XHR uses the <base> of the main document, so does new Image().src or new Audio() etc. That's going to be confusing. If you create a canvas, then do new Image().src to load an image to draw it'll not be the same as if you had appended the image to the ShadowRoot and assigned a src. Making you append the node to the ShadowRoot is sad, now you're causing style recalcs just to draw into a canvas. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 16 August 2013 17:06:40 UTC