- 16 Jun, 2006 12 commits
-
-
John Resig authored
-
John Resig authored
-
John Resig authored
IE is now forced layout if it doesn't have it (such that opacity now works as expected). (Ticket #4).
-
John Resig authored
-
John Resig authored
-
John Resig authored
-
John Resig authored
-
John Resig authored
-
John Resig authored
-
John Resig authored
$.css() now accounts for borders in addition to padding when calculating the height/width of an element.
-
John Resig authored
-
John Resig authored
Fake trigger events now get passed through $.event.fix() first, to give them an extra layer of authenticity.
-
- 15 Jun, 2006 6 commits
-
-
Gilles van den Hoven authored
-
John Resig authored
-
John Resig authored
-
John Resig authored
-
John Resig authored
Adding in the brand new, working, IE DOM Ready code. Plus I made it such that if you bind a ready() function after the DOM has loaded, it will fire the function instantly.
-
John Resig authored
-
- 13 Jun, 2006 3 commits
-
-
John Resig authored
Added in some revised DOM Ready code, I've removed all the kludgey stuff. I'd prefer to have predictable, slow, code that unpredictable fast code.
-
John Resig authored
-
John Resig authored
-
- 12 Jun, 2006 4 commits
-
-
John Resig authored
-
John Resig authored
I've completely resolved the known issues with document ready. I use the known DOM ready functions that Mozilla and IE provides. For Opera and Safari I fall back to the original hack, but ignore it, and fall back to window.onload, if there are scripts embedded in the DOM.
-
John Resig authored
-
John Resig authored
Fixed an issue with #id expression parsing, an issue with formatting, and removed the try{} block from around event firings.
-
- 11 Jun, 2006 3 commits
-
-
John Resig authored
-
Michael Geary authored
-
Michael Geary authored
-
- 09 Jun, 2006 4 commits
-
-
Gilles van den Hoven authored
-
Gilles van den Hoven authored
-
Gilles van den Hoven authored
-
Gilles van den Hoven authored
- I've renamed $.eval to $.execute (since $.$$exec is allready there?) - Commited sam's form function - Removed $.fn.formValues() - Removed $.fn.update() - Removed $.fn.serialize()
-
- 06 Jun, 2006 2 commits
-
-
Gilles van den Hoven authored
-
John Resig authored
-
- 03 Jun, 2006 2 commits
-
-
Gilles van den Hoven authored
-
Gilles van den Hoven authored
-
- 02 Jun, 2006 2 commits
-
-
Gilles van den Hoven authored
-
Gilles van den Hoven authored
--no commit message
-
- 01 Jun, 2006 1 commit
-
-
Gilles van den Hoven authored
-
- 31 May, 2006 1 commit
-
-
Gilles van den Hoven authored
Gets form values and creates a key=>value array of the found values. What's new? - Only does this for ENABLED elements. - Keeps the same order of the form. - Optionally adds the button which is clicked (marks that name with an 'x' in the list) example: $('#frmLogin').formValues('oButton'); $.fn.update (PREVIOUSLY: $.update, so beware!!!!) Calls sURL with sAction (method) and sends the aValues. Puts the results from that call in the jQuery object and calls fCallback if provided. What's new? - Renamed $.update to $.fn.update, since it is more obvious to call $('someJQueryObject').update(...) then $.update($('someJQueryObject'), ...). It's also more jQuery-ish - Added the method you want to use, since i used post before, now you can select between either GET or POST. example: $('someJQueryObject').update('sURL', 'sAction', 'aValues', 'fCallback'); $.fn.serialize Calls the form's action with the correct method and the serialized values. Optionally adds the button which is clicked if you provide it. When there are results, the fCallback function is called. What's new? - The entire function example: $('someForm').serialize('sButton', 'fCallback');
-