Closed
Bug 386637
Opened 17 years ago
Closed 17 years ago
Getting the wrong context menu sometimes on certain pages
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ria.klaassen, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
12.75 KB,
image/png
|
Details |
Since some days I suddenly get the wrong context-menu when I select text in Gmail or the bug number on top of this page. When I load the Add-ons window over it, it gets the normal context menu back. It also happens with disabled extensions. On the following URL the links on the left side sometimes don't work anymore (although I see a hand cursor), but I can't intentionally reproduce it: http://goedgezien.nl/salontafelserielinteloo.htm I *think* this was caused by bug 237964 but there is no way to prove it nor can I offer a way to reproduce this consistently. And maybe I'm wrong. Sorry for the vague report.
Reporter | ||
Comment 1•17 years ago
|
||
Getting the "page" context menu instead of the "selection" context menu.
Comment 2•17 years ago
|
||
This wouldn't per chance be Bug 385478? I think there are multiple ways to trigger that problem because I was seeing it without doing the steps given. But that's the only way that has been noted to reproduce it.
Reporter | ||
Comment 3•17 years ago
|
||
(In reply to comment #2) It is in fact the opposite so maybe they are related. Only, I would have noticed it if it happened longer than a few days ago. Maybe it has the same basic cause but something is triggering it easier in the last few days.
Reporter | ||
Comment 4•17 years ago
|
||
Bug 385478 has in common with this bug that you can correct the wrong behaviour by loading another window over it. Un-blocking Bug 237964 for now.
No longer blocks: contenteditable
Comment 5•17 years ago
|
||
Is this still a problem?
Reporter | ||
Comment 6•17 years ago
|
||
(In reply to comment #5) > Is this still a problem? > No, forgot to close it, thanks
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•