Opened 16 years ago
Last modified 14 years ago
#3507 confirmed Bug
[IE] Context menu always opens next to mouse cursor
Reported by: | Tobiasz Cudnik | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | |
Keywords: | IE | Cc: |
Description (last modified by )
Context menu always opens next to mouse cursor, even after being triggered by key press. This is usability issue in my opinion, because mouse can be anywhere withing the browser's viewport.
I see following options:
- Distinguish between key press and mouse click. Probably impossible, but i'm not 100% sure.
- Simply check if mouse is inside editor's viewport and then if yes - open menu next to cursor; if not - open it next to the carret.
- Always open context menu next to the carret.
Attachments (1)
Change History (6)
comment:1 Changed 16 years ago by
Keywords: | Pending added |
---|
comment:2 Changed 16 years ago by
Keywords: | Confirmed IE added; Pending removed |
---|
It's hard to provide a TC for it Garry. It's a kind of strict browser UI issue.
I'm able to reproduce this problem with IE only. In Firefox, the context menu appears in the exact position the default context menu would appear. so, it looks like the Firefox DOM events send the context menu coordinates for the contextmenu event, instead of the mouse coordinates, which is cool.
comment:3 Changed 16 years ago by
I don't see much chances to have it fixed though. We should be able to take the position of the start boundary of the selection and place the context menu relatively to it, if not using the mouse click to open the context menu.
Let's leave it opened for future investigation, but for now get Firefox ;)
comment:4 Changed 16 years ago by
Description: | modified (diff) |
---|---|
Summary: | Context menu always opens next to mouse cursor → [IE] Context menu always opens next to mouse cursor |
Indeed it works for FF and thats a good news. I'm attaching a screenshot for easier understanding of the issue. There's also a small correction - that's not accessibility problem, but usability instead.
I'm actually not cleared about the problem here, could you please provide a TC to support it?