- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 Sep 2013 20:46:10 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19870 --- Comment #23 from Dimitri Glazkov <dglazkov@chromium.org> --- We chatted a bit about this with Polymer folks, just to get some inspiration. Here are the key insights we sussed out: * Shadow trees definitely need to have a base URL. This is bug 22255. * We could probably get away with cloning being the place where URLs are magically resolved. The nature of the magic is less clear (see next bullet point). * Tying urls from imports to shadow trees seems too limiting. For instance, a hypothetical developer Scott may want to have a library of images stored as <img> tags in an import, using relative URls. Upon cloning that node into a document, Scott fully expects the right image to load. Unfortunately, this is not how <img> works today, so either we need to rewrite href attribute upon cloning or ... -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 4 September 2013 20:46:12 UTC