Provided by wwalc (CTO of CKEditor) at #1894644-39: Unidirectional editor configuration -> filter settings syncing:

Styles combo configuration: too restrictive (?), too cryptic error message

2) When specifying styles for the Styles combo I got a very cryptic error message:

The provided list of styles is syntactically incorrect.

Maybe it would be good to display the line that is invalid?

In my case the problem was in... code|Computer Code

Note that CKEditor works fine if just a tag is used to style text.
For example this is a small part of the default (sample) styles.js file:

{ name: 'Computer Code',	element: 'code' },
{ name: 'Keyboard Phrase',	element: 'kbd' },
{ name: 'Sample Text',	 element: 'samp' },
{ name: 'Variable',	 element: 'var' },

Impossible/hard to drag buttons to the end of a toolbar row

4) Maybe some day in the future: dragging buttons at the end of the toolbar is a bit cumbersome. Whenever I try to do this, it goes back to available buttons. I want to add it at the end so I slowly move it to the right outside of the active toolbar, and then I drag the button down to the right place (it does not work).

It's a bit counterintuitive that to add the button at the end, one have to move it exactly over the last button.

Drag-and-drop edge cases

5) The form in admin/config/content/formats/basic_html is quite big so I have a scrollbar on the right side on this page. It looks like this is causing some problems with d&d operations.

When I scroll the page down and back, then start dragging buttons, strange issues start happening like: dragged button is not visible at all, dragged button appears 200px above the mouse pointer etc.

Depressingness of "Allowed HTML tags" field

[OT]

The little "Allowed HTML tags" field is depressing for anyone that actually cares what's there ;)

Comments

wim leers’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +Spark, +CKEditor in core
RE: Styles combo configuration: too restrictive (?), too cryptic error message
That validation error only happens on saving. This is only targeted at advanced users, and an example is provided. AFAIK quicksketch explicitly wanted to avoid this to be used for just about any element by enforcing the use of a class. After all, this is about "styles", which implies many elements having a specific style, which leads to classes.
RE: Impossible/hard to drag buttons to the end of a toolbar row
+1
RE: Drag-and-drop edge cases
Note that this only happens if you've given focus to a field outside of your viewport while dragging a button.
RE: Depressingness of "Allowed HTML tags" field
Care to clarify? :)
wwalc’s picture

Sorry for the whole bunch of off-topic issues in #1894644: Unidirectional editor configuration -> filter settings syncing. I was too focused on my overall impression while using the new administration area in D8 that I forgot we're tracking just one particular feature there ;)

Depressingness of "Allowed HTML tags" field

This is totally off topic, the field i so small, that is very hard to control what's there. I guess everyone got used to this fact, but now, considering that new tags will be added there automatically, a better way of displaying all tags could be helpful.

wim leers’s picture

RE: Styles combo configuration: too restrictive (?), too cryptic error message
See above.
RE: Impossible/hard to drag buttons to the end of a toolbar row
I said "+1", but now I honestly don't see the problem with this.
RE: Drag-and-drop edge cases
See above. I think #1834682: Consolidate filter options in the UI when configuring a format would go a long way in improving this.
RE: Depressingness of "Allowed HTML tags" field
Thanks for the clarification!
#1894644: Unidirectional editor configuration -> filter settings syncing ensures new tags are added automatically. You're right that if the list grows large, it's a PITA to use though. But, making the UX of that will only benefit <0.01% of the users, and it's unrelated to "CKEditor in core". So let's ignore that for now :)

So, I don't think we really need to work on any of this. The returns are marginal at best IMO.

wwalc’s picture

I'm okay with closing this. As explained in second comment I reported too much there :-)
After trying again to D&D a button at the end of the toolbar my impression is that it does not work that bad, the rest of your answers make a lot of sense, so ya, let's have this ticket closed simply.

wim leers’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

Alright :)