Move (get|extract)SelectedHtml to selection

[Piotr Jasiun]

Now we have:

editor.getSelection().getSelectedText()
editor.editable().getSelectedHtml()

We can not move getSelectedText() because of backward compatibility so we should move getSelectedHtml(). And if we move getSelectedHtml we should also move extractSelectedHtml.

Changes in ​t/12878.

[Piotr Jasiun]

I see that editor.getSelection().getSelectedHtml() method already exist and use native cloneContents which works badly. I believe it should be replaced with the new method. The old method is since 4.4 so I hope we will not break anything and having 2 methods with seems to be the same but works differently is very confusing.

[Piotr Jasiun]

After discussion with @Reinmar we decided that the behavior of the functions in editor, editable and selection is different:

• selection should know nothing about editor, config or editable, it contains only wrappers for the native methods and getSelectedText is such wrapper so it goes to selection,
• editable knows about editor and the config so it may contains method which behavior depends on configuration, also it contains lower level methods then editor so (get|extract)HtmlFromRange methods go there,
• editor contains high level API, methods user may often want to use, which works the way user expect, so (get|extract)selectedHtml goes there.

The original idea was to put (get|extract)selectedHtml into editable and link it in editor, but in fact these methods do nothing but join selection (which is property on the editor not editable) and (get|extract)HtmlFromRange so in my opinion there is no point in having them in the editable.

Changes in ​t/12878.

[Piotrek Koszuliński]

Fixed on major with ​git:b7a30dd.