Bugzilla

(In reply to James Graham [:jgraham] from comment #71)
> A question for the people doing diagnosis: is there a simple change we could suggest to the site authors that would fix this issue (without regressing Chrome or other browsers)? It seems like their code is racy _and_ poking at underdefined parts of the platform, so irrespective of whether we can implement behaviour that aligns with Chrome/others, ultimately the current situation is best fixed by the site making changes.

I think the most straightforward fix would be to ignore mousemove events whose target is the document in the handler that closes the menu when the mouse is outside of it. I've tried this fix (adding `t.target.nodeType !== 9` to the condition in the handler) and it fixed the issue for me.

(In reply to James Graham [:jgraham] from comment #71)
> A question for the people doing diagnosis: is there a simple change we could suggest to the site authors that would fix this issue (without regressing Chrome or other browsers)? It seems like their code is racy _and_ poking at underdefined parts of the platform, so irrespective of whether we can implement behaviour that aligns with Chrome/others, ultimately the current situation is best fixed by the site making changes.

I think the most straightforward fix would be to ignore mousemove events whose target is the document in the handler that closes the menu when the mouse is outside of it. I've tried this fix (adding `t.target.nodeType !== 9` to the condition in the handler) and it fixed the issue for me.

Note that there seems to be another issue with the same symptoms on intelligentretail.com: the menu also closes sometimes when the mouse moves from the button over it but on that site it also happens in Firefox Stable and Chrome and my proposed fix doesn't fix the issue there.