Jeff Graham
Top achievements
Rank 1
Rank 1
Jeff Graham
asked on 28 Jan 2010, 07:58 PM
I am working on a project that will embed the RadEditor in a JQuery dialog. I have this working successfully in IE and Firefox, but not in Chrome, Safari, or Opera.
The issue seems to be a javascript error in the the Telerik script resource files. Line 5404 has this:
var d=this._textIframe.contentWindow.document;
Chrome stops on this line and reports that the contentWindow is null. I dont have a javascript debugger for Safari or Opera, but I imagine it is the same issue there as well.
I've attached a screenshot that includes the javascript callstack.
The issue seems to be a javascript error in the the Telerik script resource files. Line 5404 has this:
var d=this._textIframe.contentWindow.document;
Chrome stops on this line and reports that the contentWindow is null. I dont have a javascript debugger for Safari or Opera, but I imagine it is the same issue there as well.
I've attached a screenshot that includes the javascript callstack.
3 Answers, 1 is accepted
0
Hi Jeff,
Could you please open a support ticket and send a sample working project that demonstrates this error? This will be the fastest way to investigate the problem and if possible to provide a solution.
Kind regards,
Rumen
the Telerik team
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.
Could you please open a support ticket and send a sample working project that demonstrates this error? This will be the fastest way to investigate the problem and if possible to provide a solution.
Kind regards,
Rumen
the Telerik team
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.
0
Jeff Graham
Top achievements
Rank 1
Rank 1
answered on 02 Feb 2010, 03:54 PM
Just opened: Ticket ID
278424
0
Hi Jeff,
I already answered to your questions in the support ticket, but I will also provide the response here so it is available to our community.
There is a known issue that occurs when the editor is moved in the DOM - [the movement] makes the editor's content area non editable. The solution to the problem is to execute the client-side method onParentNodeChanged() right after the changes to the DOM. Unfortunately, this does not solve it for Opera and we brought it to the attention of our developers. We will do our best to fix this for one of the upcoming releases.
Sincerely yours,
Dobromir
the Telerik team
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.
I already answered to your questions in the support ticket, but I will also provide the response here so it is available to our community.
There is a known issue that occurs when the editor is moved in the DOM - [the movement] makes the editor's content area non editable. The solution to the problem is to execute the client-side method onParentNodeChanged() right after the changes to the DOM. Unfortunately, this does not solve it for Opera and we brought it to the attention of our developers. We will do our best to fix this for one of the upcoming releases.
Sincerely yours,
Dobromir
the Telerik team
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.