CKEditor treats button element as resizable image in IE11

[Mike]

When using CKEditor and IE11, a <button> element inside the CKEditor's contents is displayed in a way that button appears to be a resizable image. In fact, the handles can be dragged to resize the button. This behavior does not occur in Firefox or Chrome. This behavior complicates editing because multiple clicks are required when I want to edit the button's text in WYSIWYG mode.

Steps to reproduce

1. Use any CKEditor build with IE1
2. Set an editor instance's contents to "<button>Button</button>".
3. Click, double-click, and triple-click the button to see that the button will be outlines with dragging handles.

Expected result

The button should appear as a typical button that is not resizable and does not require multiple clicks to focus on the editable text of the button.

Actual result

The button shows resizing handles and outlines the button as if it were an image.

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

1. This only happens in IE11.
2. Windows 7
3. CKEditor v4.5.6
4. Plugins: any combination of installed plugins; removing all standard plugins with removePlugins option will not fix this behavior

[Mike]

IE11 button example

[Mike]

Chrome Button example

[kkrzton]

I was able to reproduce this issue using Button dialog on IE11 and Windows 10 with CKEditor 4.5.6.

[kkrzton]

There were similar issues caused by the same problem in the past: #9317 (and ​all related).

It is much wider issue concerning many elements and for now it has not been solved for IE11 (​#12772#comment1). The cause is in native implementation and there were some fixes for MS Edge but not IE11 (​https://connect.microsoft.com/IE/feedback/details/907422/ie11-unable-to-disable-resize-helper-for-images-inputs-etc-inside-contenteditable, ​https://connect.microsoft.com/IE/feedback/details/742593/please-respect-execcommand-enableobjectresizing-in-contenteditable-elements).

There is also a ​very comprehensive description of this issue on SO by Reinmar.

[Marek Lewandowski]

True, there's nothing we can do about it in IE11 as Microsoft team does not want to fix this issue. They only allege it's fixed for Edge.