Progress® Telerik® UI for ASP.NET AJAX Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 17 Oct 2014 11:20 by Shahinur
ADMIN
Joana
Created on: 15 Sep 2014 12:53
Category: Editor
Type: Bug Report
0
FIX: AW Snap error is thrown after clicking anywhere on a page that contains RadEditor and another iframe under Chrome
Here is the simplest sample we have managed to isolate this issue to: 

        <iframe id="Iframe1" runat="server" src="http://bing.com"></iframe>
        <telerik:RadEditor ID="RadEditor1" runat="server">
        </telerik:RadEditor>

1. Run this code in Chrome

2. Click anywhere on the page except for the iframe.

Please check the attached workaround (chrome_editor_iframe_workaround.js) and add the script to the end of the page.

An official fix will be available in the Q3 2014 release.
Attached Files:
6 comments
Shahinur
Posted on: 17 Oct 2014 11:20 
The latest version of Chrome seems to have fixed this.
ADMIN
Niko
Posted on: 18 Sep 2014 15:56 
Hi Amit,

This fix is already part of the codebase and will be available with the next internal release, or the next official release. The change is minor, but the impact seems enormous. The calls to the configureFrameHandlers have been pushed to the end of the respective execution blocks. It seems that Chrome does not break gracefully, when attempt is made for a x-origin attempt and this results in some event handlers not being attached or detached on time. Why this would result in a browser crash, I don't know, but it works :)
No functionality has been removed, stopped or prevented. The Editor should work fine.

Regards,
Niko
Amit
Posted on: 18 Sep 2014 13:43 
Hi,
After running some tests, it seems to prevent the error. Could you please elaborate on what is being done in this script? Is any RadEditor functionality lost? Will this fix be added to a future version?
Thanks
Amit
Posted on: 18 Sep 2014 13:41 
deleted by amitb
ADMIN
Niko
Posted on: 18 Sep 2014 12:10 
Please, check the attached workaround under the name chrome_editor_iframe_workaround.js. Just make sure the script is loaded on page after the editor scripts.

Regards,
Niko
Ludovic
Posted on: 16 Sep 2014 16:26 
Hello,

The problem occurs to me too.
But I have a even more simple example... No need to have an UpdatePanel.

For information, if you use an Iframe with sandbox allowing script (<iframe id="frameBing" src="http://www.bing.com" sandbox="allow-scripts"></iframe>), the problem does not occur.

Unfortunatly, this sandbox mode is too restritive in my situation. I need sandbox="allow-scripts allow-same-origin"... In this mode, the problem is back.

Hope it will help to find a solution.

Regards
Attached Files:
Create an account Log In
View
Type
Status
Category