- From: <bugzilla@jessica.w3.org>
- Date: Mon, 11 Mar 2013 19:52:10 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21253 Bug ID: 21253 Summary: [Components]: Consider adding an optional name attribute and using it in the loading algorithm Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: sorvell@chromium.org QA Contact: public-webapps-bugzilla@w3.org Blocks: 20683 The spec currently requires that 2 components have knowledge of the same url to share a dependency. This is often inconvenient and it's common for module loaders to use a name as a component identifier instead of a url (http://requirejs.org/docs/api.html#jsfiles) to avoid this problem. Here some options for addressing this limitation: Option 1: <link rel="component" name="foo-component" href="..."> To support this type of usage, we could modify the "component location" concept to be "component identifier." We would allow an optional name attribute to be on the component link tag. The component identifier definition would be something like this: "component identifier The component identifier must be the value of the link element's name content attribute. If that attribute does not exist or is empty string, it is the result of resolving the URL given by link element's href content attribute, relative to the element, or empty string if that fails." Option 2: <component name="foo-componnet"> (inside the component) We could also allow components to specify an identifier for themselves. This might be done by using a <component> tag with name attribute inside the component. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 11 March 2013 19:52:15 UTC