W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2010

[Bug 11402] One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of

From: <bugzilla@jessica.w3.org>
Date: Tue, 30 Nov 2010 22:05:49 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PNYKb-00048e-B8@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11402

--- Comment #8 from Kornel Lesinski <kornel@geekhood.net> 2010-11-30 22:05:48 UTC ---
(In reply to comment #7)

> If that's the primary use, then you can make it simpler.  Just have browsers
> agree on a set of standard library names to prepackage, then use something like
> 
> <script src="scripts/jquery-1.4.2.js" library="jquery-1.4.2"></script>
> 
> and browsers would agree on what the exact file for "jquery-1.4.2" is, bit for
> bit.  So basically, instead of a general-purpose sharing scheme, just develop
> the notion of a standard library for JS.

Libraries simply bundled with browsers would be annoying just like outdated
browsers themselves &#8212; webmasters would again face choice between forgoing
this feature and sticking to a buggy version that was shipped with the browser
years ago.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 30 November 2010 22:05:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 November 2010 22:06:06 GMT