Ticket #9509 (closed bug: invalid)
CSS extremely slow in IE9
| Reported by: | artur.herczeg@… | Owned by: | artur.herczeg@… |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | css | Version: | 1.6.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
The following function is extremely slow in IE9 compared to IE7 and IE8. All the dependent functions are slow as well.
css: function( elem, name, extra ) { // Make sure that we're working with the right name var ret, origName = jQuery.camelCase( name ), hooks = jQuery.cssHooks[ origName ]; name = jQuery.cssProps[ origName ] || origName; // If a hook was provided get the computed value from there if ( hooks && "get" in hooks && (ret = hooks.get( elem, true, extra )) !== undefined ) { return ret; // Otherwise, if a way to get the computed value exists, use that } else if ( curCSS ) { return curCSS( elem, name, origName ); } }
Change History
comment:1 Changed 2 years ago by addyosmani
- Owner set to artur.herczeg@…
- Priority changed from undecided to low
- Status changed from new to pending
- Component changed from unfiled to css
comment:2 Changed 2 years ago by trac-o-bot
- Status changed from pending to closed
- Resolution set to invalid
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Thanks for submitting a ticket to the jQuery Project!. Do you have any tests or performance measurements you can share which confirm how slow you're finding css()?.
If not and this is a generic observation, it would be useful to see a test case (ideally on http://jsfiddle.net) that we can use to evaluate whether we can reproduce the same performance issues you're experiencing.