Side navigation
#7985 closed bug (worksforme)
Opened January 16, 2011 04:24AM UTC
Closed January 16, 2011 10:52AM UTC
fadeTo callback fires before
| Reported by: | Kelvne M. | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | effects | Version: | 1.4.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Tested in Firefox 4.0+ and Chrome 10+
For some reason, ONLY ON CHROME, the callback have been called before the fadeTo
This is the code:
$("#fuzz").fadeTo('slow', 0.7565, function(){
$("#alertmessage").fadeIn('1300')
})
Do anyone knows why?
Attachments (0)
Change History (1)
Changed January 16, 2011 10:52AM UTC by comment:1
| component: | unfiled → effects |
|---|---|
| description: | Tested in Firefox 4.0+ and Chrome 10+ \ \ For some reason, ONLY ON CHROME, the callback have been called before the fadeTo \ \ This is the code: \ \ $("#fuzz").fadeTo('slow', 0.7565, function(){ \ $("#alertmessage").fadeIn('1300') \ }) \ \ Do anyone knows why? → Tested in Firefox 4.0+ and Chrome 10+ \ \ For some reason, ONLY ON CHROME, the callback have been called before the fadeTo \ \ This is the code: \ {{{ \ $("#fuzz").fadeTo('slow', 0.7565, function(){ \ $("#alertmessage").fadeIn('1300') \ }) \ }}} \ Do anyone knows why? |
| priority: | undecided → low |
| resolution: | → worksforme |
| status: | new → closed |
Thanks for taking the time to contribute to the jQuery project by writing a bug report.
Following your report I made this test case. Which seems to work just fine in Opera 11, FF 3.6.13 (also FF4bX) and Chrome 8.
So I'm inclined to believe that this is a problem of the Chrome 10+ version and not of jQuery. Note that Chrome 10.X is a bleeding edge development version and not officially supported by jQuery.
I think you should try to reproduce this error without the use of jQuery and file this against the Chrome (maybe WebKit) bug tracker.
But if you indeed can prove this is a jQuery bug (with a reduced test case) and it is reproducible on one of the officially supported browser we will be more then happy to reopen this ticket and investigate this issue further.