forms plugin adds context menu listener for unsupported input types

[mark]

I've been building a plugin to add file input fields into the content. Once a file input field is added, the context menu gives a "Text field properties" option. Within the Forms plugin, it appears there is a default case for the context menu listener that adds this menu option. This should be replaced with "case 'text':case 'password'" to prevent intercepting subsequent listeners for more specific field types. It could be extended to include the HTML5 types "numeric", "email" etc as well.

[Jakub Ś]

1. This is not a bug but a feature request
2. These new field types you talk about are HTML5 - ​http://www.w3schools.com/tags/att_input_type.asp
3. CKEditor 3.x is XHTML 1.1 ("extended" HTML 4) compilant while CKEditor 4.x is intended to be fully HTML5 compilant thus this will probably be implemented in CKE 4.x

[mark]

1. I consider this a bug and not a feature request as I had to modify the ckeditor source to implement a file input field plugin with a functioning context menu. The change was however trivial - replace "default :" on line 169 of _source/plugins/forms/plugin.js with the supported types - "case 'text' : case 'password':".

2. The <input type="file"> is not a new HTML5 feature. (However The same issue that is causing problems with the file input type could cause problems with these HTML5 types as well, so fixing this the right way would also allow support for HTML5 elements in plugins).

3. This doesn't really help in supporting file inputs via a CKeditor plugin, but it is good to see that HTML5 support is on the roadmap! I might give CKeditor 4 beta a try.

[Jakub Ś]

Note: besides input type="file" all field types available in HTML4 are handled by form plugin in v3 and v4.

There were new field types introduced in HTML5. Since CKEditor 4.x is meant to be HTML5 compliant this feature should have version 4 set (I doubt it will be implemented in v3).

This is not a regression but something that will probably be implemented only in v4.

[mark]

Note: input type='file' is incorrectly handled by the form plugin.

Ignoring any HTML5 input fields, the form plugin prevents writing your own plugin to handle the HTML4 file input. The fix for file inputs is trivial (and might also allow some HTML5 input support to be added on using plugins as an added bonus).

Unless maybe I'm missing something and it is possible for a plugin to override a core plugins context menu listeners I can't see why this change would not be for the better.

[Alfonso Martínez de Lizarrondo]

Proposed patch

[Alfonso Martínez de Lizarrondo]

I've used this ticket as a little test to check if I've understood the way to do pull requests and branches in v4.

The patch attached here fixes the problem for v3 and it should be safe to add it, and ​https://github.com/ckeditor/ckeditor-dev/pull/11 tries to do the same thing for v4 (although I understand that if the bug is fixed in v3 then the patch will be merged along with all the other v3 fixes, so it will be another step with git: learn how to discard a rejected pull request)

[Piotrek Koszuliński]

Pushed ​git:cf006be (​t/9503@cksource).

I added support for tel, email, search and url types to Alfonso's patch. These inputs are basically textfields, so they can be inserted with the current textfield dialog.

Other input's types have to handled by new dialogs in forms plugin or completely new plugins.

[Olek Nowodziński]

Force pushed rebased branch.

[Olek Nowodziński]

t/9503 is alright, but it'd be great to have tests for it. At the moment, tests basically check whether inputs are being correctly created. Testing this feature in the opposite direction would also be beneficial: select text field, open dialog and validate if attributes have been correctly imported into dialog logic.

[Piotrek Koszuliński]

Pushed t/9503@tests.

[Piotrek Koszuliński]

Masterised ​git:45dd07d.