- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Sep 2013 20:33:11 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23170
Scott Miles <sjmiles@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sjmiles@chromium.org
--- Comment #5 from Scott Miles <sjmiles@chromium.org> ---
We will have to think about the various ramifications of this change, but my
knee-jerk reaction is that this might be a great simplifier.
To restrict the notion of `inertness` (aka: no defaultView)to templates could
clarify several ancillary issues.
> What about stylesheets, images, videos, and other assets
Polymer team wants stylesheets to be 'live' as if they were in the main
document, would having a proper defaultView in the import make this easier?
As for those other elements, seems like they can do whatever they normally
would do. If you don't want them to do work you should put them in a template.
E.g. this might be a nice way to preload images: shove a bunch of image tags in
an import.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 5 September 2013 20:33:13 UTC