FLUID-3865: Rich text inline edit demo does not contain focus styling for TinyMCE toolbar items

Metadata

Source
FLUID-3865
Type
Bug
Priority
Major
Status
Closed
Resolution
Cannot Reproduce
Assignee
N/A
Reporter
Jonathan Hung
Created
2010-11-30T10:31:25.062-0500
Updated
2014-07-18T09:36:23.346-0400
Versions
  1. 1.3
  2. 1.3.1
  3. 1.4
Fixed Versions
N/A
Component
  1. Demos
  2. Inline Edit

Description

Using FF 3.6, when focus is placed on the TinyMCE toolbar, it is invisible. Thus attempting to use keyboard navigation by tabbing through appears to be doing nothing, but in fact focus is being placed on toolbar items. The lack of focus styling is confusing and gives the wrong impression that the demo has broken.

To reproduce:
1. Start Firefox 3.6
2. Load the demo: http://build.fluidproject.org/infusion/demos/inlineEdit/rich/html/inlineEdit.html
3. Begin editing the first paragraph.
4. While still editing, tab repeatedly through the document and attempt to reach the editor that is still open.
5. You will discover that you will be stuck on an invisible, empty element just before the editor.

Affects both FF 3.6 on Windows and Mac OS X. IE8 on Windows is not affected.

The example on the TinyMCE website does not appear to have this problem.
http://tinymce.moxiecode.com/examples/full.php#

Keyboard work-around:
You can hit "enter" to select an item in the toolbar. This would put you back into the textarea, from which you could tab out. You could also hit "esc", which would close the RichText Inline edit and give you back your proper tab navigation.

Environments

Firefox 3.6, Windows, Mac OS X
IE8 Windows 7
IE6 Win XP

Comments

  • Anastasia Cheetham commented 2011-10-17T13:28:54.409-0400

    I think the issue is not so much that there isn't focus styling, it's that you can't properly tab to the toolbar: Try clickin in the toolbar area and then tabbing - you do get a focus highlight. Still a problem, but a different problem.

  • Justin Obara commented 2014-07-18T09:36:23.296-0400

    The focus styling appears. I've tried with Chrome 35, FF 30, Safari 7 (Mac OS 10.9) and IE 11 (Win 7).