insertHtmlIntoRange

[Piotr Jasiun]

When image is uploaded (#11461) we need to replace uploading image with the final one, so we need to insert html in the given range (not in the editors selection). Because of this situation we need to introduce insertHtmlIntoRange methods.

[Piotr Jasiun]

There were some conceptual problems with this ticket. The main reason is that insertHtml is high-level method: it fixes selection, scroll viewport and can make snapshots if widget was inserted. The insertHtmlIntoRange, in contrast, is low-level method: it just insert HTML without any additional operations. But in both cases we need to make some operations after insertion (ex. checkWidgets). To solve the problem I introduced afterInsert event with the intoRange parameter which is true if this is low level method.

Changes in ​t/12448.

[Piotrek Koszuliński]

I rebased ​branch:t/12448 and pushed additional commit.

• insertElement and insertElementIntoRange don't need to fire the afterInsert event. These methods are very different from insertHtml and insertText, because they can't trigger data processor. Also the insertion algorithm is much different.
• Since the behaviour is so different, I think that it will be better to rename the event to afterInsertHtml so in the future we can have one specific for insertElement. The goal is to have a total separation between methods inserting elements and methods inserting HTML/text.
• data.intoRange should carry the range.
• Please complete editor.insertHtml/Text and editable.insertHtmlIntoRange docs with information that these methods fire the editor.afterInsertHtml event. In editor.inserHtml/Text/Element you can also mention the editor.insertHtml/Text/Element events because I see that they are not mentioned there.

[Piotrek Koszuliński]

I also noticed a difference between:

• insertElement(element, range) chooses between insertElementIntoRange and insertElementIntoSelection based on the range argument.
• For HTML there's only insertHtml and insertHtmlIntoRange.

Although, I find the two methods better than three, but wouldn't it be better to do it the same way as element methods for consistency reasons?

[Piotr Jasiun]

Replying to Reinmar:

I also noticed a difference between:

• insertElement(element, range) chooses between insertElementIntoRange and insertElementIntoSelection based on the range argument.
• For HTML there's only insertHtml and insertHtmlIntoRange.

I find the two methods better than three, but wouldn't it be better to do it the same way as element methods for consistency reasons?

We agreed that these methods only look similar, but work differently, so there is no reason do make then look event more similar. It may suggest that then have something common. Especially when the third method is useless.

I fixed rest of issues. Changes in ​t/12448.

[Piotr Jasiun]

Replying to pjasiun:

Replying to Reinmar:

I also noticed a difference between:

• insertElement(element, range) chooses between insertElementIntoRange and insertElementIntoSelection based on the range argument.
• For HTML there's only insertHtml and insertHtmlIntoRange.

I find the two methods better than three, but wouldn't it be better to do it the same way as element methods for consistency reasons?

We agreed that these methods only look similar, but work differently, so there is no reason do make then look event more similar. It may suggest that then have something common. Especially when the third method is useless.

I fixed rest of issues. Changes in ​t/12448.

After the discussion we decided to organized insertHtml methods the same way insertElement is organized. I also fixed and added test and rebased branch on the newest major.

[Piotrek Koszuliński]

Merged to major with ​git:18d651ad.