WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#30407 closed enhancement (wontfix)

Add keyboard shortcut for switching between Visual & Text editors

Reported by: UaMV Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords:
Focuses: Cc:

Description

I propose adding a keyboard shortcut for switching between the visual editor and the text editor which would benefit those who prefer to use the visual editor, but need to momentarily switch to the text editor to check classes, customize code, and perform similar tasks.

Change History (15)

#1 @iseulde
5 years ago

  • Version 4.0 deleted

#2 follow-up: @iseulde
5 years ago

  • Keywords 2nd-opinion added

This would probably depend on #29492. I'm not sure if I like the idea though. If other people like this idea, please leave a comment. :)

#3 @joedolson
5 years ago

I'm uncertain how valuable this is; I'd love to hear some feedback from people about whether they would use this feature.

To me, it feels like it's adding something fairly unnecessary - but that might just be bias from my own workflow.

#4 @melchoyce
5 years ago

If I knew it was there, I'd probably use it. I do a lot of toggling back and forth.

#5 @iseulde
5 years ago

  • Keywords close added

#29492 is wontfixed.

#6 in reply to: ↑ 2 @UaMV
5 years ago

Replying to iseulde:

This would probably depend on #29492. I'm not sure if I like the idea though. If other people like this idea, please leave a comment. :)

I wouldn't say this is dependent upon #29492. If this keyboard toggle was available without the ability of editors to maintain position, it would still serve the purpose of switching editors without having to consult your mouse or trackpad. Which would be super handy for those who prefer keyboard only navigation.

#7 @helen
5 years ago

I don't know what keyboard shortcut we could use that's actually available. As it is, we have difficulties.

#8 follow-up: @iseulde
4 years ago

I think we should look at the reasons why people are toggling back and forth, not add a shortcut to ease the pain.

#9 in reply to: ↑ 8 @UaMV
4 years ago

Replying to iseulde:

I think we should look at the reasons why people are toggling back and forth, not add a shortcut to ease the pain.

Excellent point! Here are a few reasons I often switch ...

  • To reposition shortcoded or oEmbedded content. Although images can easily be repositioned by dragging, captioned images, galleries, youtube videos, etc. cannot be easily repositioned by dragging. Hmmm ... just realized cut/paste for these elements works swimmingly on the Visual editor – a welcome revelation! For some reason, I was assuming I had to go to the text editor to make this happen.
  • To add a custom classes to elements
  • To see how the HTML is stacking up.

Honestly, the first one was the major issue for me, but seems to be a non-issue now. I think I was misled by knowing I couldn't drag those elements.

#10 follow-up: @iseulde
4 years ago

Although images can easily be repositioned by dragging, captioned images, galleries, youtube videos, etc. cannot be easily repositioned by dragging.

See #28272, #28003 and #28826

To add a custom classes to elements

I wonder how common that is. What do you add classes to?

To see how the HTML is stacking up.

Not sure if this is a good way to see that as the P tags are removed and the content runs through auto-P again before it is displayed on your site.

Last edited 4 years ago by iseulde (previous) (diff)

#11 in reply to: ↑ 10 @UaMV
4 years ago

Replying to iseulde:

Although images can easily be repositioned by dragging, captioned images, galleries, youtube videos, etc. cannot be easily repositioned by dragging.

See #28272, #28003 and #28826

Nice. Thanks for sharing. I don't follow tickets as well as I might. Seems like folks are on this one.

To add a custom classes to elements

I wonder how common that is. What do you add classes to?

Most often, I'll be adding a class to an unordered list or adding in a span, div or sup with classes.

To see how the HTML is stacking up.

Not sure if this is a good way to see that as the P tags are removed and the content runs through auto-P again before it is displayed on your site.

Yeah, I realize that p tags have been removed. It's still much quicker than previewing the source, then returning for edits. I just fill in the blanks.

#12 follow-up: @melchoyce
4 years ago

To add a custom classes to elements

I would love to find a more user-friendly way to do this. It would be especially useful for adding button styles to links, adding pull-quotes, etc.

#13 in reply to: ↑ 12 @afercia
4 years ago

Replying to melchoyce:

To add a custom classes to elements

I would love to find a more user-friendly way to do this. It would be especially useful for adding button styles to links, adding pull-quotes, etc.

Someway related: TinyMCE allows to have custom CSS classes, see screenshot about some typography experiments I was working on a while ago. For existing elements (e.g. paragraphs) it's very easy but if you want to style only a portion of text it's not so friendly. You'd need to have an element to style first, e.g. a span.
What I usually do is to apply "underline" to my text selection (that creates a span) then apply the class and then remove the underline. It would be nice if the spans were created automatically. Maybe something worth considering? :) cc @iseulde and @azaozz

https://cldup.com/td6JH0HdD8.png

Last edited 4 years ago by afercia (previous) (diff)

#14 @helen
4 years ago

Before this veers further off-topic: what keyboard shortcuts are even left available to us for use? Once you factor in everything used on the system, browser, and navigation technology levels, there typically isn't a whole lot left.

#15 @chriscct7
4 years ago

  • Focuses ui accessibility removed
  • Keywords 2nd-opinion close removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Comment:3 and comment:7 imo provide a good basis for why this should be closed. There's not many possible combinations left, and the number of people who would have a use for this would be incredibly small.

The CSS classes stuff should get split off into it's own ticket (but that discussion should continue).

For the basis of the original ticket (adding a shortcode), closing as wontfix

Note: See TracTickets for help on using tickets.