Slightly confusing API (editor.ui.view.editable.element VS editor.ui.view.editable.editableElement)

[wwalc]

When trying to set an attribute on the editable element in #670 I noticed that there are two attributes which point to the same element (editor.ui.view.editable.element VS editor.ui.view.editable.editableElement). I was immediately confused which one should I choose and if there will be any unexpected implications if I use the wrong one.

[oleq]

It looks like the editableElement property is no longer needed.

[Reinmar]

editableElement was meant to give you the right element in case of iframed editables.

So, for normal editables, editableElement == element. But for iframes that will be different. element will equal the iframe and editableElement the body inside.

[Reinmar]

We could remove editableElement for now but we'll need to add it one day anyway. And it may be better to have that standard access from the beginning.

[oleq]

That's a good point. Let's get back to this issue when (if) we develop an iframe–based editor.

[Reinmar]

What we can do now is review these prop API docs. But I know that it will be confusing 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).