Ticket #4607 (new defect)

Opened 9 months ago

Last modified 2 weeks ago

Editor: provide a mode to allow use of tab key within editor

Reported by: becky Owned by: becky
Priority: normal Milestone: 1.2
Component: Accessibility Version: 0.9
Severity: normal Keywords:
Cc: alex, liucougar

Description (last modified by becky) (diff)

#3812 implements tab/shift-tab key navigation into/out of the rich text editor to make it keyboard accessible

There are people who are concerned about this change since it eliminates the use of tab/shift-tab within the editor to indent/outent items. Would like to provide a mode to allow this behavior when the rich text editor is the only item on the page and thus keyboard navigation out of the editor may not necessary. Although I'm not sure there is ever a case when navigation out of the editor is not necessary - the user needs some mechanism to save or send the current editor contents. So, may need to provide a different keyboard mechanism for getting into /out of the editor or a different way to indent/outdent

Attachments

4607.patch (8.5 kB) - added by becky 3 weeks ago.
4607a.patch (10.5 kB) - added by becky 3 weeks ago.
udated to add ctrl+m key combo to invoke and move tab handling to editor.js

Change History

  Changed 5 months ago by becky

  • milestone changed from 1.1 to 1.2

  Changed 3 weeks ago by becky

  • cc alex, liucougar added
  • description modified (diff)

Changed 3 weeks ago by becky

follow-up: ↓ 4   Changed 3 weeks ago by bill

  • summary changed from provide a mode to allow use of tab key within editor to Editor: provide a mode to allow use of tab key within editor

Hopefully Cougar can review this but I have a few comments.

First, presumably if a developer uses this plugin, it prevents a keyboard user from getting to the Toolbar, so the ticket description (about using this when there is nothing else on the page) seems disingenuous. Even in that case it will mess up keyboard users, so might be better to rephrase as "if you don't need full keyboard support in your app" (and to document that in the plugin).

As for technical issues, it seems like you shouldn't need the isTabIndent parameter to the Editor; shouldn't just including the plugin (in extraPlugins) be enough?

Also BTW there's a little weird indenting in the patch itself, probably used spaces instead of tabs.

in reply to: ↑ 3   Changed 3 weeks ago by liucougar

Replying to bill:

First, presumably if a developer uses this plugin, it prevents a keyboard user from getting to the Toolbar, so the ticket description (about using this when there is nothing else on the page) seems disingenuous.

One way around this is to provide a default shortcut key to toggle the action as well as a toolbar button

As for technical issues, it seems like you shouldn't need the isTabIndent parameter to the Editor; shouldn't just including the plugin (in extraPlugins) be enough?

there is currently no way of changing execCommand behavior in an editor plugin without hijack that function in Editor (which is dangerous if user has subclass of Editor). So I guess we have to leave that code in RichText/Editor?

Changed 3 weeks ago by becky

udated to add ctrl+m key combo to invoke and move tab handling to editor.js

  Changed 3 weeks ago by becky

I added 4607a.patch to move the tab handling code into editor.js before the undo code. I also added ctrl+m as a key combination to enter and exit tab editing mode. I could just add this key combination when the tabIndent plugin is used but it seemed worthwhile to add in general.

  Changed 2 weeks ago by liucougar

looks ok, we can fine tune it once it is committed

  Changed 2 weeks ago by becky

(In [14056]) refs #4607 added support for a mode to use the tab and shift-tab keys to indent outdent list items. Also added ctrl+m as keyboard shortcut for this behavior. Created a simple icon which needs additional work. Needs more work in FF2 on OSX

Note: See TracTickets for help on using tickets.