On Mac OS X builds (currently at least), click-and-hold on a link causes the standard link context menu to pop up. However, if there's also a marquee operating on the page, then the context menu selection flickers, the mouse pointer flickers back and forth between the arrow and the hand, and the status bar continually flickers between "Done" and the URL. Please see the attachment which I'll add next. Of note, this only happens while the mouse is still being clicked. If you move the mouse outside the context menu and release it, then the context menu stays open and the menu no longer behaves strangely. The same is true if you open it by right- or control-click. As to when this bug began... the situation is complicated. It definitely didn't occur before June, 2004. But apparently some time in that month, the context menu completely stopped appearing if you clicked-and-held on a link in the presence of a marquee. As the menu didn't appear at all, it was impossible to test for flickering after that point. The context menu finally reappeared in the 20050330 build, and the "flicker" problem was present at that stage. Not sure if something in between those dates caused this bug, or if the initial disappearance is the true cause, and it was partially fixed by something on the latter date.
Created attachment 216175 [details] Page with simple marquee and link. Click and hold on link to observe 'flicker'.
This may or may not be dependent on two things. 1) If/When click-and-hold context menus are turned off by default, this issue won't show again (bug 301758). 2) The move (on the trunk) to cocoa widgets may fix this, though it's hard to tell since Camino doesn't have click-and-hold menus turned on.
(In reply to comment #2) > This may or may not be dependent on two things. > 1) If/When click-and-hold context menus are turned off by default, this issue > won't show again (bug 301758). I considered that, but it looks like that bug proposes retaining click-and-hold functionality as a preference (off by default), so it'll still need to work. > 2) The move (on the trunk) to cocoa widgets may fix this, though it's hard to > tell since Camino doesn't have click-and-hold menus turned on. Can hope so! Though that'll be well after Firefox 2. Still, it's not like this is a glaring bug for most people, and it's been present in Fx 1.5 for some time (it didn't creep into the 1.0 releases).
You need to log in before you can comment on or make changes to this bug.