[Bug 13582] HTML5 suggestion: Elements of HTML section: Scripting and Document Metadata subsections

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13582

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |travil@microsoft.com
         Resolution|---                         |NEEDSINFO

--- Comment #9 from Travis Leithead [MSFT] <travil@microsoft.com> ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:


   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Additional Information Needed
Change Description: No spec change
Rationale:

I believe the general idea is sound and backwards compatible (which is really
necessary for something like this). However, there are a number of pieces that
are missing in order to land this as a new feature. Notably, the details in how
a library can be installed, such that these new script element attributes take
effect.

Some additional questions to ponder:
* Is there new API needed for a script library to register itself as such?
* Can new versions of a library auto-update the old versions?
* How do you install a library so that the name attribute can be associated
with the library?
* How do you avoid collisions with different libraries registering for the same
name? How do you deal with modules/sub-modules?
* How do the use cases for this feature relate to the browser's cache, the
current practice of hosting libraries on CDNs, etc.
* What are the potential security implications?

I'd encourage you to consider writing this up as an extension specification to
HTML. Here's some details to get you started:
http://www.w3.org/html/wg/wiki/ExtensionHowTo

Thanks!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 8 March 2013 23:09:51 UTC