Attributes hoisted to paragraph are not converted when selection is in another place

[Reinmar]

This leads to breaking the X position of the caret:

The <strong> element should always be in that paragraph. That would allow the selection to natively land in there when pressing up/down arrows so we wouldn't need to fix it (breaking the X position).

[Reinmar]

The problem here is that we're converting attributes of the selection (which inherits attributes from the paragraph once it lands there). We'd need to somehow convert element attributes to attribute elements (fun with words!) too so those attribute elements don't disappear.

[scofalik]

I've pushed branch t/1071 ckeditor/ckeditor5-engine@3b797c6 with one of possible solutions. The solution is so that we make sure that we don't touch attribute elements created for stored attributes during selection conversion.

I don't like this solution much, I have a feeling that it is unstable / uncomplete (although it works and makes sense). It uses the same flow for selection conversion as it did, but:

• it takes extra care now when breaking attributes (effectively removing empty attribute elements),
• and when wrapping elements when similar element is next to wrapped position (this is a "no change" in view, but in fact a new view element is created and it makes a difference for view->dom conversion).

We could try creating attribute elements for stored attributes during "normal conversion". It also makes sense and sounds more stable. But there is still problem with breaking and wrapping attributes because we have to do it if element is not empty. So I am afraid that we would need the same conditions anyway.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).