Ticket #17992 (reopened defect (bug))
Wrong Tooltip in the Editor
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | TinyMCE | Version: | 3.2 |
| Severity: | minor | Keywords: | dev-feedback |
| Cc: |
Description
In the new Fullschreen-Editor, the Upload/Insert Media Button has, referring to the Tooltip, the Shortcut Alt+Shift+M. When I press this Combo, the wrong Dialog opens.
I'm not sure, if the Tooltip is wrong or the Shortcut wrongly assigned...
Attachments
Change History
comment:2
SergeyBiryukov — 9 months ago
In trunk, "Insert/edit image" button doesn't seem to work at all in DFW.
comment:4
follow-up:
↓ 6
solarissmoke — 8 months ago
- Keywords has-patch dev-feedback added
The button wasn't working because the IDs have changed on the main editor buttons (not sure why, maybe a change in TinyMCE), which the DFW button Javascript was using. Patch fixes that.
Regarding Alt+Shift+M, even in normal editing mode that produces a different dialog box to what the add/image button does. I'm not sure what the original intention was, but it seems we should remove that from the tooltip at least, seeing as the button doesn't do the same thing?
comment:5
SergeyBiryukov — 8 months ago
- Milestone changed from Awaiting Review to 3.3
Related: #17144
Replying to solarissmoke:
The button wasn't working because the IDs have changed on the main editor buttons
Meant to fix this on #17144, it's broken as the editor together with all links/buttons around it supports multiple instances now.
Regarding Alt+Shift+M, even in normal editing mode that produces a different dialog box to what the add/image button does.
The shortcuts in TinyMCE execute internal commands. Will change this one to open the new Link popup.
- Owner set to azaozz
- Status changed from new to closed
- Resolution set to fixed
In [18710]:
comment:8
follow-up:
↓ 9
SergeyBiryukov — 8 months ago
- Keywords has-patch removed
- Status changed from closed to reopened
- Resolution fixed deleted
In trunk, pressing Alt+Shift+M shows inconsistent behaviour in different browsers:
- Firefox 6 & 7 — Visual/DFW mode: thickbox + quicktags dialog; HTML mode: nothing
- Chrome 14, IE 8 — Visual/DFW mode: thickbox dialog; HTML mode: quicktags dialog
- Opera 11 — Visual/DFW mode: thickbox dialog; HTML mode: nothing
One of the options would probably be to remove the quicktags img dialog shortcut.
Replying to SergeyBiryukov:
Think I fixed some or all of these in a different ticket. Could you re-test it again, seem fine here.
comment:10
follow-up:
↓ 11
SergeyBiryukov — 8 months ago
Updated to r18803, cleared the cache. Still the same. Here are some steps to reproduce:
In Firefox 7:
- Switch to HTML tab.
- Press Alt+Shift+M. quicktags dialog won't open.
- Switch to Visual tab.
- Press Alt+Shift+M. Both thickbox and quicktags dialog will be opened at the same time.
In Opera 11.51, quicktags dialog won't open in step 2. thickbox in step 4 is fine.
In Chrome 14 and IE 8, both dialogs are fine.
SergeyBiryukov — 8 months ago
-
attachment
17992.both-dialogs.png
added
Screenshot of both dialogs at the same time
comment:11
in reply to:
↑ 10
azaozz — 8 months ago
Replying to SergeyBiryukov:
In Firefox 7:
- Switch to HTML tab.
- Press Alt+Shift+M. quicktags dialog won't open.
- Switch to Visual tab.
- Press Alt+Shift+M. Both thickbox and quicktags dialog will be opened at the same time.
The problem with FF is that it uses Alt+Shift+[letter] to activate the accesskey attribute for links and buttons and it doesn't seem to be able to cancel it. On top of that it doesn't trigger properly the click event when executing the accesskeys, so instead of opening the dialog it highlights the button and the user has to press Enter to "execute" it.
Surprisingly all the accesskeys are triggered when the HTML editor is hidden...
I'm not sure we can do much from JS to fix this behavior (it doesn't trigger any of the other buttons too). We could remove all the accesskey attributes when in FF since they trigger errors when the HTML editor is hidden. The other option would be to load another JS that assigns new/different keys in Quicktags in FF.
comment:12
azaozz — 6 months ago
- Milestone changed from 3.3 to Future Release
Not a regression, affects only FF, moving to 3.4.
