Search and Top Navigation
#5201 closed bug (notabug)
Opened February 19, 2010 12:56PM UTC
Closed March 28, 2011 08:06AM UTC
Hover + backgroundColor animation fails to update viewport in IE8
Reported by: | Kanuck | Owned by: | Kanuck |
---|---|---|---|
Priority: | minor | Milestone: | 1.9.0 |
Component: | ui.effects.core | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I am using
animate()to change a background colour. Here is the relevant snippet:
.hover(function() { $(this).find("a") .stop().animate({'backgroundColor' : '#DCDDDF'}, 100); }, function() { $(this).find("a") .stop().animate({'backgroundColor' : '#F2F2F3'}, 250); })
Unfortunately, in IE8—and only IE8—the effect does not work.
The value of background-color is being changed in the DOM, but the viewport isn't being updated; as soon as any other animation effect kicks in, the viewport updates.
I think the bug is in the UI effects core because changing
backgroundColorto, say,
opacityeliminates the issue. Animating
opacityis handled by jQuery natively, whereas animating
backgroundColoris handled by jQuery UI.
I've found a workaround that might shine some light on an eventual fix: chaining
.fadeTo(1, 1)in front of the first
stop()gives the renderer the kick in the pants it needs to work correctly. I expect it's causing core jQuery to do something necessary that jQuery UI is failing to do.
IE8 affected. IE7 mode, IE7, IE6, Safari, Firefox, Chrome all immune.
Attachments (0)
Change History (5)
Changed February 19, 2010 12:57PM UTC by comment:1
Changed March 10, 2010 05:09PM UTC by comment:2
milestone: | TBD → 1.8 |
---|
Changed March 13, 2011 09:01AM UTC by comment:3
owner: | → Kanuck |
---|---|
status: | new → pending |
http://jsfiddle.net/gnarf/vK3bA/ I used this url to test and did not see this bug in IE8... Do you have a different test case, or is this bug not affecting 1.8.9?
Changed March 13, 2011 09:03AM UTC by comment:4
priority: | major → minor |
---|
Changed March 28, 2011 08:06AM UTC by comment:5
resolution: | → invalid |
---|---|
status: | pending → closed |
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!
Ah yes, I almost forgot to mention: changing
to also eliminates the problem, so it seems to be something particular to the interaction between and .