Fix #11115: remove boolHook (where feasible) #1066
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This one is much less clear-cut than #12600, upon which it depends. It's just a matter of picking inconsistencies: because IE<8 is incapable of differentiating the relevant properties and attributes, the oldest of the oldIEs must necessarily get left behind in order to correctly draw a distinction between boolean them.
If we accept this, it means that modern browsers and IE8+ will correctly interpret selectors referencing boolean attributes from jQuery 1.9 on, and most of this code will be removed in jQuery 2.0.
If we don't, we either commit to incorrectly interpreting those selectors indefinitely or we introduce this as a documented inconsistency between 1.9 and 2.0.
IOW:
ROCK
jQueryHARD PLACE
Sizes - compared to 12600 @ f9e0e510cb01daab6348e849fbec6836060190d4