- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Aug 2013 16:51:49 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19870 --- Comment #13 from Steve Orvell <sorvell@chromium.org> --- I think I can described the desired behavior more simply: (1) it needs to be easy to use elements in imports in the main document (one shouldn't have to do path fixup to make url's work); (2) imports also need to be portable so authors must be able to specify paths relative to imports. 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. For background, here's how the Polymer HTML Imports polyfill (https://github.com/Polymer/HTMLImports) handles url's in imports: 1. When an import is loaded, all attributes and css that contain relative url's are re-written to be relative to the main document. 2. Imports are given a <base> element with that has the main document's url. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 16 August 2013 16:51:50 UTC