Opened 8 years ago
Closed 7 years ago
#3528 closed Bug (fixed)
CKEditor : Context Menu issue
| Reported by: | Senthil | Owned by: | tobiasz.cudnik |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.1 |
| Component: | General | Version: | |
| Keywords: | Oracle Confirmed Review+ | Cc: | Senthil |
Description
Shift + F10 -> Opens the Context menu, outside the RTE editing area(Sometimes it opens the File menu from the browser main menu)
Attachments (1)
Change History (7)
comment:1 Changed 8 years ago by fredck
- Milestone changed from CKEditor 3.0 to CKEditor 3.1
comment:2 Changed 7 years ago by tobiasz.cudnik
- Owner set to tobiasz.cudnik
- Status changed from new to assigned
comment:3 Changed 7 years ago by tobiasz.cudnik
- Keywords Review? Confirmed added
comment:4 Changed 7 years ago by garry.yao
- Keywords Review+ added; Review? removed
viewport(0,0) is not the standard context menu behavior there, checking the browser context menu of the textarea will show it's at textarea(0,0), so I think Tobias's alignment is a better choice for this.
comment:5 Changed 7 years ago by garry.yao
But please fix patch path issue as well as the changelog position.
comment:6 Changed 7 years ago by tobiasz.cudnik
- Resolution set to fixed
- Status changed from assigned to closed
Fixed with [4131].
Changed 7 years ago by tobiasz.cudnik
Note: See
TracTickets for help on using
tickets.
Having it at the top left corner of the browser viewport is not a big issue, as it simply reproduces the normal context menu behavior. The only problem is that it's getting opened at the 0,0 coordinates, so it may not be visible if the page is scrolled down.
The context menu key is the preferred way to open it though, leaving SHIFT+F10 to those without that key. As this action is usually related to accessibility for visually impaired users, it's not a big issue to not have it visible in this specific case, as it still works.