Disable uiElement API has changed - no longer works as expected

[Teresa Monahan]

The APIs for disabling uiElements in plugins/dialog/plugin.js has changed. It previously disabled the input element. However it now sets the disabled attribute on the uiElement itself. Therefore even though a uiElement is disabled, it is still possible to enter text in it's associated input element.

An example of this can be seen on the table dialog.

1. Create a table
   
2. Right click on the table and select Table Properties from the context menu.
   
3. Notice that the Rows and Columns fields look disabled.
   
4. Place the cursor in either the Rows or Columns field and type some text.
   

Problem: You should not be able to type in these fields. The input elements should be disabled directly instead of disabling the parent div element.

Apart from allowing users to type into disabled fields, the 3.6.1 implementation of this also has an accessibility impact. Disabling the parent div element means that the child input element is not properly disabled and it is therefore still exposed as a focusable and editable field to accessibility APIs. Also disabled is not a supported attribute on div elements in the HTML specifications.

[Teresa Monahan]

Actually it looks like this new issue was introduced as a result of Ticket #6657. We would still like the behaviour described in ticket #6657 i.e that the cke_disabled CSS class gets added to the UI Element's div rather than the field's input element. However we believe the disabled attribute should be set directly on the input element as described in this ticket.

[Frederico Caldeira Knabben]

Replying to tmonahan:

Your comments describes it properly. The current way is definitely wrong.

[Garry Yao]

Fixed with [6947], sorry for messing up the commit message.