Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clicking the "Keyboard Shortcuts" button in the Classic block does nothing. #9748

Closed
kjellr opened this issue Sep 10, 2018 · 8 comments
Closed
Labels
[Block] Classic Affects the Classic Editor Block [Feature] Blocks Overall functionality of blocks Needs Design Feedback Needs general design feedback. [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Status] In Progress Tracking issues with work in progress [Type] Bug An existing feature does not function as intended

Comments

@kjellr
Copy link
Contributor

kjellr commented Sep 10, 2018

Describe the bug

Clicking the "Keyboard Shortcuts" button in the Classic block has no effect.

To Reproduce

  1. Insert a classic editor block.
  2. Expand the classic block controls to show the second line.
  3. Click the question mark icon.
  4. Nothing happens.

Expected behavior

It seems like (most of?) the classic editor shortcuts work, so I'd expect that the keyboard shortcuts modal shows up.

Screenshots

screen shot 2018-09-10 at 9 42 06 am

Tested in:
Mac OS 10.13.6, Safari 11.1.2, Chrome 69.0.3497.81

@kjellr kjellr added [Component] TinyMCE [Feature] Blocks Overall functionality of blocks labels Sep 10, 2018
@ianbelanger79 ianbelanger79 added the [Type] Bug An existing feature does not function as intended label Sep 10, 2018
@ianbelanger79
Copy link
Contributor

I can confirm that the "Keyboard Shortcuts" button does nothing when clicking on it.

Tested in Windows 10, Chrome and Firefox

@ellatrix ellatrix added [Block] Classic Affects the Classic Editor Block and removed [Component] TinyMCE labels Oct 31, 2018
@mtias mtias added this to the WordPress 5.0 RC milestone Nov 12, 2018
@mtias mtias added the [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later label Nov 12, 2018
@mtias
Copy link
Member

mtias commented Nov 13, 2018

Should we remove this button here given there's a more general one?

@mtias mtias added the Needs Design Feedback Needs general design feedback. label Nov 13, 2018
@chrisvanpatten
Copy link
Contributor

Does the Classic block/TinyMCE have its own set of shortcuts that aren't included in Gutenberg's Keyboard Shortcuts modal?

@mtias mtias added the [Status] In Progress Tracking issues with work in progress label Nov 15, 2018
@tofumatt
Copy link
Member

Does the Classic block/TinyMCE have its own set of shortcuts that aren't included in Gutenberg's Keyboard Shortcuts modal?

They aren't labelled, but yes.

@karmatosed
Copy link
Member

Should we remove this button here given there's a more general one?

To me yes this feels the right move.

@tofumatt what ones are missed and could when classic block is active those appear in the modal? I maybe am asking for a complicated check, but the idea we have 2 places for same thing here is awkward.

@tofumatt
Copy link
Member

I don't see any keyboard shortcuts on the TinyMCE buttons:

screenshot 2018-11-19 11 45 13

screenshot 2018-11-19 11 45 07

But actually I don't see too many we're missing from https://www.tiny.cloud/docs/advanced/keyboard-shortcuts/

What you're talking about doing (having keyboard shortcuts vary based on block selection) is bad UX to me. Keyboard shortcuts should be global and the Classic Block isn't a UX I think we want to advertise, right? It taking up space in the global shortcuts just adds noise and having it contextually appear seems like a lot of added complexity for a UX that won't be clear. Would that extend to other blocks? Would a custom block be able to add to the shortcuts modal (but only when selected).

I think we should just remove the button. If the Classic Block has extra features we aren't advertising I think that's fine. Classic Block is already quite "expert mode". 🤷‍♂️

@mtias
Copy link
Member

mtias commented Nov 19, 2018

Related #6195.

@youknowriad
Copy link
Contributor

closed in #11856

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Classic Affects the Classic Editor Block [Feature] Blocks Overall functionality of blocks Needs Design Feedback Needs general design feedback. [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Status] In Progress Tracking issues with work in progress [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

8 participants