ain't executing links as it should some times

Bug #67633 reported by Anders Strömer
4
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I use Ubuntu 6.10 Edgy and FF with the Swedish translation.
I have found this little annoying fenomen i firefox 2.0.
If I try too following a link from a web page
sometime I just end up at the top of the same page,
instead of going to the new location.
It only happen if I have scrolled down a bit on the page.
It will not happen if I click in the page with the mouse first.

Revision history for this message
Miguel Martinez (el-quark) wrote :

I confirm this behaviour.

My firefox (spanish translation with the extensions "adblock filterset.G updater", "adblock plus" and "flashblock") also ocasionally goes to the top of the page when clicking a link. So far I haven't experienced the same with epiphany, although I have used it for a couple of minutes.

BTW: Can the affected package be chaged to "firefox"?

Revision history for this message
Anders Strömer (anders-stromer) wrote : Re: [Bug 67633] Re: ain't executing links as it should some times

Miguel skrev:
> I confirm this behaviour.
>
> My firefox (spanish translation with the extensions "adblock filterset.G
> updater", "adblock plus" and "flashblock") also ocasionally goes to the
> top of the page when clicking a link. So far I haven't experienced the
> same with epiphany, although I have used it for a couple of minutes.
>
> BTW: Can the affected package be chaged to "firefox"?
>
>
After running FF in safe-mode with all extensions disabled I can still
recreate the bug.
But I can't say if this is only affecting the Ubuntu-build of FF 2.0.
/Anders

Revision history for this message
Miguel Martinez (el-quark) wrote :

I've been trying (not too hard, though) to get a pattern for replication, but without success. About "stock" firefox, I had no "links scroll to top of the page" incidents, but I had only one yesterday with the ubuntu build. Any news?

Revision history for this message
Anders Strömer (anders-stromer) wrote :

Today I got an update of FF to 2.0.0.1 and with some other updates related to FF it now seems like this annoying bug is gone.

Revision history for this message
VF (vfiend) wrote :

Closing as per comment that it's already fixed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.