15439 - right-clicking on link puts it into :focus state forever

Status: RESOLVED WORKSFORME

(Core :: XUL, defect, P3)

Description

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

DESCRIPTION:  Right-clicking on a link puts it permanently into a state that
matches ":hover" in CSS.

STEPS TO REPRODUCE:
* Load http://www.fas.harvard.edu/~dbaron/
* Right click on a link

ACTUAL RESULTS:  The link's background changes to maroon, and it stays that way.

EXPECTED RESULTS:  The link's background should only be maroon while the mouse
pointer is over the link.

DOES NOT WORK CORRECTLY ON:
 * Linux, apprunner, 1999-10-03-08-M11

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Changing component to "XP Toolkit/Widgets" since this has to do with context
menus and I think that's the right place...

Comment 2

[Peter Trudelle]

reassigning to saari as p3 for m15

Comment 3

[Eli Goldberg]

[Contextual menu bug --- QA Assigning to self.]

Comment 4

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

It's actually the :focus state, not the :hover state (the :focus and :hover
colors on the given page are the same - I quickly changed one of them to test).

Comment 5

[sairuh (rarely reading bugmail)]

reassign QA contact to me & updated component.

Comment 6

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

I think this is either fixed or it's a duplicate of bug 21363.

Comment 7

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

But right clicking on a link does put it into :focus.  Should it?

Comment 8

[leger]

BULK MOVE: Changing component from XP Menus to XP Toolkit/Widgets: Menus.  XP 
Menus component will be deleted.

Comment 9

[saari (gone)]

Pink, I think this is actually the bug with mouse events going to the parent
window instead of the popup.

Comment 10

[Mike Pinkerton (not reading bugmail)]

no, it has nothing to do with parent/child as far as i can tell. it's also XP, 
though the mac seems to make the link active as well while the other platforms 
don't.

Comment 11

[Mike Pinkerton (not reading bugmail)]

post beta

Comment 12

[Mike Pinkerton (not reading bugmail)]

moving all defects not directly related to P0 beta2 features off to M18.

Comment 13

[Peter Trudelle]

Mass moving M18 bugs to M19

Comment 14

[Peter Trudelle]

mass-moving all bugs to m21 that are not dogfood+ or nsbeta2+ or nsbeta2-

Comment 15

[sairuh (rarely reading bugmail)]

*spam*: transferring current XP Menu bugs over to jrgm, the new component owner.
feel free to add me to the cc list (unless am the Reporter) of any of these, if
you have any questions/etc.

Comment 16

[Mike Pinkerton (not reading bugmail)]

futuring. it's easy to get out of this state, and mostly harmless.

Comment 17

[Mike Pinkerton (not reading bugmail)]

i suspect this is because we eat the event that dismisses the popup and don't
let it through to gecko. As a result, the click to take it out of the focus
state never gets through. Is this that bad? *shrug*

Comment 18

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

As noted in the 7-25 comment above, this bug is less serious than it was when it
was originally filed.

Comment 19

[Jesse Ruderman]

I think this should be wontfix, because removing focus from the link (and 
putting it where?) would make it impossible to focus a link using the mouse.  
In IE, I can right-click a link and then click on the title bar to give the 
link focus.

What's the bug number for eating clicks that dismiss context menus?

Comment 20

[Jesse Ruderman]

Hmm, maybe I misinterpreted the bug.  I'm still confused about what the current 
problem is.

Comment 21

[Jesse Ruderman]

Ok, I guess the question is whether a left-click that cancels a context menu 
should move focus.  I say it shouldn't, because it would be confusing to move 
focus without also activating the element clicked on.

See bug 21390 for a discussion of whether a click cancelling a menu should "go 
through".

Comment 22

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Agreed.  The originally reported bug is fixed, and maybe there's nothing else to
do here.

Comment 23

[Jesse Ruderman]

Ok, wfm then.