Divarea vs inline editor - styling problems

[Piotrek Koszuliński]

1. To style both focused editables - normal inline one and created with divarea I had to write to selectors: ​https://github.com/ckeditor/ckeditor-dev/commit/16f0f5c Nothing really serious, but other selectors may have to be doubled too and maybe this wasn't intended :).
2. I also noticed that divarea inherits the same box-shadow: inset huge rule which styles other inline editors. This shows power of inline editing, but also doesn't look very well - maybe we want to disable this rule somehow.

[Piotrek Koszuliński]

I've found another issue. Sourcearea has cke_editable class, so it inherits the same box-shadow as in 2). Basing on existing classes if I want to style only content of inline editor, I have to use .cke_editable[contenteditable=true] selector which isn't supported in old IEs. I believe we should do some clean up in these classes, to allow writing simple selectors for all type of editables (with special conditions for focused or not, ltr/rtl, etc).

[Garry Yao]

Proposed creator specific class name on editable, to provide better flexibility when styling editable.

[Piotrek Koszuliński]

Masterised with ​https://github.com/ckeditor/ckeditor-dev/commit/43a28ff after few tweaks.

[Garry Yao]

"pointer" is not the correct cursor shape, fixed into "default" instead.

​https://github.com/ckeditor/ckeditor-dev/commit/62bca77ecc2a9923bf83eb5b69cb0953348d3e26

[Piotrek Koszuliński]

"pointer" is a correct cursor shape. It points that this box can be clicked. That this will be followed by some reaction. The default cursor shows nothing at all - default means that there's no special thing about these boxes.

Please revert your change.

[Garry Yao]

The editable is not an interactive element of the page, but by it's nature an editable section, and it does not react to mouse click, upon mouse down it will be enough to show the cursor, so I dont consider "hand" to be the proper cursor here.

[Frederico Caldeira Knabben]

I have reverted the cursor to pointer with f3257dc because in fact the editable is a very interactive element and it makes more sense in that way. It's easier to discover the editable and it reacts to the click.