Home Dashboard Directory Help
Search

Internet Explorer and HTML5 content editors by Real McCoy


Status: 

Closed
 as External Help for as External


Type: Bug
ID: 805319
Opened: 10/14/2013 5:15:13 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Mercury (https://github.com/jejacks0n/mercury) is a light-weight content editor.

Checkout the live demo here http://jejacks0n.github.com/mercury/

With IE11, when we click on the editable region and select "Link" from top nav to insert the link, an empty dialog appears and stay empty forever. In console, we have this message:

SCRIPT5007: Unable to get property 'cloneContents' of undefined or null reference
File: mercury.min.js, Line: 466, Column: 25786

In non-IE browsers, the same script runs without any issue.


Last year you guys postponed the request for IE 9 and IE10 - https://connect.microsoft.com/IE/feedback/details/747092/problems-with-popups-iframe-based-rich-text-editors

Do you have plan to fix this essential part of web -- HTML5 content editing -- in IE11? Or you still expect us to tweak our scripts for IE11, because IE fails to handle JS like every other browser does... Please don't close this one unless its really fixed!

JavaScript team @Microsoft: thanks for all the great work you have done in IE 9, 10 and 11. But with issues like these, where the BASIC use cases are failing its "too much for nothing".
Details
Sign in to post a comment.
Posted by Microsoft on 1/8/2014 at 7:49 AM
Thank you for your feedback. This issue is currently caused by issues external to Internet Explorer.

The site http://jejacks0n.github.io/mercury/ thinks that IE does not support the required parts of the HTML5 spec. When the 10 ua string is pushed, it tells that a different browser needs to be used. It's not clear what part of the spec they require.

If you believe the problem is due to Internet Explorer, please file a new feedback with additional information.

Best regards,
The Internet Explorer Team
Posted by Microsoft on 10/22/2013 at 11:27 AM
Thank you for your feedback. We will be investigating this issue further.

Best regards,

The Internet Explorer Team
Sign in to post a workaround.