| CARVIEW |
Every repository with this icon (
) is private.
Every repository with this icon (
) is public.
| Description: | jQuery JavaScript Library edit |
| Homepage: | https://jquery.com/ edit |
| Public Clone URL: |
git://github.com/jquery/jquery.git
Give this clone URL to anyone.
git clone git://github.com/jquery/jquery.git
|
| Your Clone URL: |
Use this clone URL yourself.
git clone git@github.com:jquery/jquery.git
|
Comments for jquery's jquery
It might be valuable to use:
git clone --depth 1
Why the ^ is removed from the rtrim?
Great. I was wondering why it wasn't there before
"Text node was retrieved from .text()."
I understand IE can bother you but this one is ok :-)
OK
No? I mean, otherwise we would be checking for every possible input and that doesn't really make much sense - I mean if someone wants to try and use jQuery in a non-standard way, we shouldn't really stop them (unless it's in an unintended way - such as passing in a null or undefined).
There are jokers who pass number to $(). For some devious reasons. Can/should we add :
if ( "number" === typeof arguments[0] ) return ;
Into the $(), itself ?
Sorry, the change proposed by Andrea is in the first message of the thread: https://groups.google.com/group/jquery-dev/browse_thread/thread/5f23ae0f85bebb89/2b014e7e55cb32c7
I'm not a fan of that particular change - it as assumes that all arry indexOf checks actually have the indexOf method (which is not the case for NodeLists, arguments objects, etc.).
I backed out symlink change (not sure how that got in there), it should be working again. Also just change the git pull to "git pull origin master" which should work for everyone.
Andrea Giammachi suggested a larger change which would speed up inArray with other Array-like objects, see
https://groups.google.com/group/jquery-dev/browse_thread/thread/5f23ae0f85bebb89/2b014e7e55cb32c7?lnk=gst&q=indexOf#2b014e7e55cb32c7
This fails for me... test/qunit symlinks to /Users/jeresig/Code/QUnit!
I majorly dig that. Keeping submodules up to date is a pain.
awesome :D
Good catch - I backed it out, found a test case, and fixed it.
I mis-typed in the commit message, it's "Fixed the case where getComputedStyled was assumed to exist if getBoundingClientRect doesn't" (since, naturally, the code already worked in IE).
Aha, real tabs are used.
Strange. I wonder how additional spacing was generated.
The issue https://dev.jquery.com/ticket/5443 presented more than 1 issue with 0 reproducible tests. How would this fix the FF issue (which the ticket is about) if this is in the
document.attachEventbranch ? The IE issue wasn't attributed to style sheet order and while this addition is harmless I would dig seeing an actual reproducible test to verify the issue before just throwing code at it.
