| 2006-05-03 16:42:00 |
Tessa |
bug |
|
|
added bug |
| 2006-05-12 14:43:28 |
Ian Jackson |
firefox: status |
Unconfirmed |
Needs Info |
|
| 2006-05-12 14:43:28 |
Ian Jackson |
firefox: statusexplanation |
|
|
|
| 2006-10-06 20:40:44 |
Lakin Wecker |
firefox: status |
Needs Info |
Confirmed |
|
| 2006-10-06 20:40:44 |
Lakin Wecker |
firefox: statusexplanation |
|
I'm still seeing this on an up to date dapper with firefox on an amd64. It is an amd64 issue. If I download and install firefox 1.5.0.7 (32 bit version) from the firefox site, everything works fine.
For me, I see this with moo.fx, scriptaculous, dojo and a number. I'm willing to provide more information as needed.
What I see is that the effects like "Fade" or "moving elements" don't work unless you keep trying to click on them. It's as if their are some timeout functions that aren't working properly.
I'm confirming it, as it seems that most of the questions asked have been answered. |
|
| 2007-02-19 15:16:43 |
Alexander Sack |
firefox: status |
Confirmed |
Needs Info |
|
| 2007-02-19 15:16:43 |
Alexander Sack |
firefox: assignee |
|
mozillateam |
|
| 2007-02-19 15:16:43 |
Alexander Sack |
firefox: statusexplanation |
I'm still seeing this on an up to date dapper with firefox on an amd64. It is an amd64 issue. If I download and install firefox 1.5.0.7 (32 bit version) from the firefox site, everything works fine.
For me, I see this with moo.fx, scriptaculous, dojo and a number. I'm willing to provide more information as needed.
What I see is that the effects like "Fade" or "moving elements" don't work unless you keep trying to click on them. It's as if their are some timeout functions that aren't working properly.
I'm confirming it, as it seems that most of the questions asked have been answered. |
is this still an issue for you? Can you still reproduce with latest firefox?
In case, how can I see that its broken. Need a testcase. Thanks. |
|
| 2007-02-24 04:39:54 |
David Farning |
firefox: assignee |
mozillateam |
mozilla-bugs |
|
| 2007-02-24 04:39:54 |
David Farning |
firefox: statusexplanation |
while i cannot deny that this might have been caused by some ubuntu/debian specifics in 1.5, iceweasel has never been released from 1.5. So the observation that firefox 2.0 in edgy fixes is not at adds with your observation that iceweasel has never had this issue.
For dapper, I am not sure ... need a detailed working testcase or some tester who can help to sort this out on irc: on freenode -> #ubuntu-mozillateam.
|
|
|
| 2007-06-30 11:48:09 |
John Vivirito |
firefox: assignee |
mozilla-bugs |
gnomefreak |
|
| 2007-06-30 11:48:09 |
John Vivirito |
firefox: statusexplanation |
|
Im gonna see if i can reproduce this with testcases that are here but if there is a better one please drop it in bug report. |
|
| 2007-06-30 12:50:00 |
John Vivirito |
firefox: assignee |
gnomefreak |
mozilla-bugs |
|
| 2007-06-30 12:50:00 |
John Vivirito |
firefox: statusexplanation |
Im gonna see if i can reproduce this with testcases that are here but if there is a better one please drop it in bug report. |
|
|
| 2008-10-10 03:59:03 |
Erich Jansen |
firefox: status |
Incomplete |
Fix Released |
|
| 2008-10-10 03:59:03 |
Erich Jansen |
firefox: statusexplanation |
|
Closing at request of submitter |
|
| 2008-10-10 04:03:35 |
Erich Jansen |
firefox: status |
Fix Released |
Invalid |
|
| 2008-10-10 04:03:35 |
Erich Jansen |
firefox: statusexplanation |
Closing at request of submitter |
|
|
