we tried chasing this code, you're welcome to join the hunt if you like.

one case i found that's interesting is double click, but i think it's the wrong
case.

http://timeless.justdave.net/mxr-test/garage/source/browser/mozilla/trunk/microb-eal/src/gmozillaengine.c

is most of the code.
The approach I had in hunting was to try to find the paths that start or stop
the animation handler.

stop_cursor_animation_handler seems like a reasonable function, and you can
find most of the relatives that way.

http://timeless.justdave.net/mxr-test/garage/source/browser/mozilla/trunk/microb-engine/microb-engine/debian/patches/gtkmozembed/gtkmozembed.diff#983

ends up being one of the fun code paths.

I think that the code path that's the most interesting is indeed the one that
triggers focus, because, if it's like the one that handles double click, maybe,
just maybe it stops the event.

The menu itself should trigger in:
dom_mouse_long_press_cb
http://timeless.justdave.net/mxr-test/garage/source/browser/mozilla/trunk/microb-eal/src/gmozillaengine.c#2480

this just kills it, but i think it's not the case I seek:
dom_mouse_dbl_click_cb 
http://timeless.justdave.net/mxr-test/garage/source/browser/mozilla/trunk/microb-eal/src/gmozillaengine.c#2517

The old start page seems to work as a testcase slightly.

it's definitely easiest to reproduce on a freshly loaded page, and it's best if
the link doesn't have focus.

when the animation does trigger, i can see it visibly jumping around, which to
me indicates that reproducing it should involve a sharp unmoving press and that
the reason the problem isn't always happening must relate to hearing a
move/second tap at different coords.

but we really don't get it.

a reduced testcase (if at all possible) should be very helpful. Note that this
code is a minefield, partly because of panning, and partly because of web page
heuristics. So probably the best testcase would be something like:

<script>function
handler(event){document.getElementById("handler").value+="\n"+event.type+Date.now();}</script><a
href="javascript:handler(event);return false;"><img width=500 height=200
src=about:logo></a><textarea id=output>

I don't have time to work on this atm, we spent a while just reading through
the code and picking out various other bugs along the way.

Comment 2 Frantisek Dufka (reporter) 2007-11-27 01:14:43 UTC

FWIW just confirming that it still happens with OS2008 beta for N800.

Comment 3 Andre Klapper 2008-11-25 19:02:38 UTC

timeless: Is there an internal ID for this, or is this even WONTFIX for Diablo?
I think I also see this issue in latest Diablo.

Comment 4 Andre Klapper 2009-06-09 20:11:10 UTC

WONTFIX for Diablo (as Diablo will only receive critical updates if at all).
So far I haven't seen this issue in Fremantle yet.

Comment 5 Andre Klapper 2009-06-19 18:48:15 UTC

*** Bug 2078 has been marked as a duplicate of this bug. ***

Since 2078 is now listed as a duplicate of this bug, I thought I'd replicate my
reply over here.  I suggested that, for my specific case (wanting to easily
open links in a new window), just adding one or two new items to the Navigation
menu might be a useful work-around.  I was then asked:


> > Or, why not add the 2 items to the navigation menu?
> 
> Navigation currently has 7, I'm not sure what 2 you'd add (please specify, I
> don't mind talking/listening, it's the only way to get ideas somewhere people
> can see them).
> 
> Note that typically the context menu and the edit menu have some similarity,
> however, id on't know of any way to combine them that wouldn't upset everyone.
> 

The two items I would add to the navigation menu are:

Open in New Window
Open in New Tab (assuming tabs are enabled, I think they were in microb)

Comment 7 Andre Klapper 2009-07-15 15:25:29 UTC

(In reply to comment #4)
> WONTFIX for Diablo (as Diablo will only receive critical updates if at all).
> So far I haven't seen this issue in Fremantle yet.

Tried to reproduce in Fremantle for the last five weeks but I haven't run into
this in the (not yet public) browser.
I consider this FIXED in Fremantle but as I don't know of an exact code fix I
prefer to call it WORKSFORME (very well).

As already written this is a WONTFIX for Diablo as Diablo is in maintenance
mode and Nokia will only provide bugfixes for critical issues if at all.
For your interest the Mer project aims to provide a community backport of
Fremantle for N8x0 devices. See http://wiki.maemo.org/Mer for more information.