[Bug 457343] Review Request: jquery - Fast, concise library that simplifies how you use javascript

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 19 15:25:46 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=457343

--- Comment #8 from François Kooman <fkooman at tuxed.net> 2011-08-19 11:25:41 EDT ---
I would like to take over if I can figure out how to solve the Sizzle "problem"
and some other issues....

I'm not a huge fan of requiring a modification to all software that depends on
jquery.js to now all of a sudden also require an extra <script> tag to import
sizzle.js (as suggested by Steven) and possibly break compatibility (update
sizzle while not updating jquery, or the other way around). Just changing the
path to the jquery JS file seems a little bit more reasonable...

2) The static linking idea is interesting, but I guess we then might as well
just leave the "original" bundled jquery in the package to be sure it works as
the developers intended.

3) Maybe somehow all versions can be made available in the package?

- The jquery package can just contain the minified versions of all jquery
versions ever released (like what is available on the Google CDN)? 
- Or maybe have two packages. The jquery package (containing only the latest
version) and a compat-jquery package (containing all? the previous versions)?
- Or implement a CDN api like Google for JS containing all jquery (and other js
libs) versions?

4) It would be interesting to pull jquery from git and build it locally (using
the Makefile). This pulls in Sizzle and Qunit from git. Possibly something can
be done there to unbundle? Furthermore it would require nodejs (not packaged
yet?) to minify jquery...

5) It seems to be impossible to test all software after upgrading jquery to a
newer version (see jquery 1.6.1 .attr() problem for instance). Should there be
test procedures? updates-testing is time enough for package maintainers/users
to check software against the latest version of jquery? How to avoid negative
karma if stuff breaks? :)

6) How to fix all local copies of jquery in packages from being used? Use a
(Apache) rewrite rule that redirects all */jquery*.js calls to /js/jquery.js?
:-)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the package-review mailing list