- From: <bugzilla@jessica.w3.org>
- Date: Sat, 20 Jul 2013 02:02:57 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21253
William Chan <willchan@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |willchan@chromium.org
--- Comment #2 from William Chan <willchan@chromium.org> ---
RequireJS doesn't try to globally address resources by content/id. Instead, it
relies on a component identifier + baseURL as described in Steve's link which
says: "RequireJS loads all code relative to a baseUrl." What this encourages is
every website self-hosting its own web components if they want to use these
component identifiers. If we want to allow this to be done globally, then we
start running afoul of security concerns, some of which are fixable by a hash,
but there's also the Content-Security-Policy issue. See
https://news.ycombinator.com/item?id=4516193 for details with explanations from
agl & abarth.
AIUI, the main value of this proposal is making component loading easier for
web developers. And I agree strongly with this. Component loading with explicit
URLs can often be a PITA.
One downside of the RequireJS approach is that the module loading is all done
in JS and is opaque to the rendering engine's preloader. It'd be great if any
solution we propose here enables the preloader to understand the resource
loading so it can issue resource requests sooner.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 20 July 2013 02:02:59 UTC