[Edge] Editor scrolls down when trying to edit inline widget.

[Tade0]

Steps to reproduce

1. Open ​http://tests.ckeditor.dev:1030/tests/plugins/widget/manual/inline in Edge
2. Double-click on a placeholder widget(e.g. Dwight Hooker?) to edit it.

Expected result

The edit dialog appears.

Actual result

The edit dialog does not appear, the editor is scrolled down.

Other details (browser, OS, CKEditor version, installed plugins)

Browser: Edge.

[Jakub Ś]

There is similar ticket #13577

[Tade0]

Findings so far: To reproduce the error cut & paste internally the image widget that's in the editor.

After this clicking on any widget will scroll down, but not completely, because just after pasting the string "Lena Söderberg image widget" was appended to the end of the editor and that's where the editor scrolls.

[Tade0]

Apparently this is one of those situations, where Edge behaves differently than IE, but since CKEDITOR.env.ie is true, the code is executed through a path, that causes errors.

Changing how the hidden selection container is generated partially mitigated the problem (see ​branch:t/14742), but this is not enough to solve this bug.

[Marek Lewandowski]

Moving to 4.6.2 minor release, as 4.6.1 is mostly about polishing 4.6.0.

[Tade0]

There seems to be some kind of race condition enabling this bug, because adding the debugger statement in each paste listener and observing the state of the editor was enough to make the bug not appear.

[Tade0]

The problem is in the way the paste event is handled in the widget plugin.

The data is modified using a regex that in Edge results in malformed content.

[Tade0]

Previous comment is wrong.

The real problem happens in this method: ​http://docs.ckeditor.com/#!/api/CKEDITOR.editable-method-insertHtml

Somehow what eventually gets selected is not the content in the supplied range.

[Tade0]

Some conclusions:

• The text that appears at the end of the editable after pasting is the ARIA label of the widget. It's not the hidden selection container - just its content.
• Putting a breakpoint anywhere will make this bug not appear - either there's some asynchronous even going on, or it's a browser bug.

Added a minimal manual test for this case.

[Tade0]

Rebased with current major and it seems the problem... went away?

[Tomasz Jakut]

It seems that bug is really gone – I can't reproduce it even on 4.5.11 version. Maybe some update for Edge fixed it?

[Marek Lewandowski]

Well done!!! :P