- 04 Apr, 2011 33 commits
-
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
No longer need to check for objects or string of null with the special form treatment and updates to removeAttr
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
Fix #6562, tighten up the special code for form objects, add name attrHook for IE6/7, and don't check for undefined with getting hook'd attr
-
timmywil authored
- Forms with an input that has either name="action" or name="some-other-attr-on-the-form" caused problems in IE6/7. This is fixed. - Changed check in $.attr for ret === null to typeof ret === "object" to catch any inputs that are accidentally retrieved in IE6/7, since attributes cannot be set to objects and typeof null === "object"
-
timmywil authored
- Remove an unnecessary var - Use variable in removeAttr for better minification
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
Restored 6 tests that I had commented to come back to later to split up between prop and attr. All tests still pass in all browsers. - I should make it clear that I have not removed any tests, but only moved some attr tests to prop where I thought it was appropriate.
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
-
timmywil authored
Full test suite now passes in all browsers! There are probably some tweaks we can make to shorten and simplify. - removeAttr now only uses setAttribute if camelCase setAttribute is not supported + Might want to rename jQuery.support.getSetAttribute - tabIndex is a special case now for hooks where undefined should be returned. + Should we be checking if hooks returns undefined? undefined might be the desired return value in future hooks. As of now, tabIndex is the only one that needs it, but the test suite will still pass if we don't check if hooks are undefined. -
timmywil authored
Continuing IE7 testing, conditional attr fixes and hooks with feature testing. Will figure out a way to shorten after the test suite passes.
-
timmywil authored
-
timmywil authored
-
timmywil authored
First proposed solution for IE6/7 get/setAttribute quirks. Needs more testing, but solves some issues
-
timmywil authored
-
timmywil authored
-
timmywil authored
+ Added hooks for selected, checked, readonly, disabled to removeAttr if set to falsey + Removed all attrs from attrFix, these aren't needed for setAttribute + If prop is used for class, do we want a propFix for class? - We could just assume the user should know to use className with prop. I've done the latter for now. + Created tests for $.fn.prop and $.fn.removeProp - Actually all I did was change broken attr tests to prop where it made sense.
-
jeresig authored
Very crude first pass at splitting apart the attr/prop logic. Also adding in attrHooks/propHooks. All of it is completely untested.
-
- 01 Apr, 2011 2 commits
-
-
John Resig authored
-
John Resig authored
-
- 31 Mar, 2011 5 commits
-
-
-
Dave Methvin authored
Followup commit for #7340 test case; make sure second test fires properly on IE by focusing to another element rather than blurring off the first.
-
timmywil authored
- Removed special page, just needed another test in the fixed offset tests - Checks it's position related to scrolling
-
Dave Methvin authored
-
-