This question is locked. New answers and comments are not allowed.
Brian Adle
Top achievements
Rank 1
Rank 1
Brian Adle
asked on 31 Mar 2011, 04:03 PM
I can reproduce this on the demo page: http://demos.telerik.com/aspnet-mvc/editor. Steps to reproduce are:
1. Delete all content from the editor.
2. Click in the editor, type some text
3. Click on the font size and change the font size.
4. JS Error: Line: 1
Error: Invalid argument.
I've run a test app locally and the error comes down to the line of code in telerik.editor.min.js "a2.moveToElementText(a7)" a2 is object with two values which equal the text that as already been written and A7 has an outer html = "<A></A>"
This is consistent and repeatable for me.
1. Delete all content from the editor.
2. Click in the editor, type some text
3. Click on the font size and change the font size.
4. JS Error: Line: 1
Error: Invalid argument.
I've run a test app locally and the error comes down to the line of code in telerik.editor.min.js "a2.moveToElementText(a7)" a2 is object with two values which equal the text that as already been written and A7 has an outer html = "<A></A>"
This is consistent and repeatable for me.
10 Answers, 1 is accepted
0
Hello Brian,
What browser are you using? I could not reproduce the problem in Firefox, nor IE9 (standards and compatibility view).
All the best,
Alex Gyoshev
the Telerik team
What browser are you using? I could not reproduce the problem in Firefox, nor IE9 (standards and compatibility view).
All the best,
Alex Gyoshev
the Telerik team
0
Brian Adle
Top achievements
Rank 1
Rank 1
answered on 04 Apr 2011, 01:41 PM
Check the title of the bug. "IE8"
0
Brian Adle
Top achievements
Rank 1
Rank 1
answered on 04 Apr 2011, 01:42 PM
The trick seems to be that your cursor needs to be at the end of the entered text in the text area and then change font.
0
Hi Brian Adle,
Atanas Korchev
the Telerik team
I managed to reproduce the reported bug. I am sending you a hotfix build which resolves it.
I also updated your Telerik points.
Atanas Korchev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Brian Adle
Top achievements
Rank 1
Rank 1
answered on 05 Apr 2011, 03:18 PM
This latest code you've sent me has broken a feature I've been using for several versions. I was previously able to create a Telerik Window in JS and assign it HTML and a contentURL and it would display the HTML while the contentURL loaded. This allowed me to get a faux loading message. Is there a work around for this? I have some windows that take 4-5 seconds to load and having now feedback for the user is a bad experience.
0
Hello Brian Adle,
Atanas Korchev
the Telerik team
This is not a known issue. Could you send me the code which you are using so we can debug it ? We fixed a problem with contentUrl and the fix may have broken your scenario.
Regards,Atanas Korchev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Brian Adle
Top achievements
Rank 1
Rank 1
answered on 05 Apr 2011, 03:28 PM
createDialog: function (contentUrl, name, height, width, modal, onCloseFunction) { if (!jQuery.isFunction(onCloseFunction)) { onCloseFunction = function () { }; } var html = '<div class=" ZoneDefaultText " style="width:' + width + 'px; text-align:center; ">Loading ' + name + '...<br /><img src="images/loading.gif" height="20px" alt="" /></div>' var window = $.telerik.window.create({ title: name, html: html, contentUrl: contentUrl, modal: modal, resizable: false, draggable: true, height: height, width: width, onClose: onCloseFunction }); return window },There's some App specific code in here but I think you can get the basic idea of what we were doing.
0
Hello Brian Adle,
Thank you for reporting this -- it seems that this was a regression due to a bug fix (when contentUrl is a remote URL, the window displays an iframe). It is now fixed and your scenario is backed by a unit test -- the attached build contains the fix.
Kind regards,
Alex Gyoshev
the Telerik team
Thank you for reporting this -- it seems that this was a regression due to a bug fix (when contentUrl is a remote URL, the window displays an iframe). It is now fixed and your scenario is backed by a unit test -- the attached build contains the fix.
Kind regards,
Alex Gyoshev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Brian Adle
Top achievements
Rank 1
Rank 1
answered on 07 Apr 2011, 03:37 PM
This is getting comical... The 407 build fixes the window issue but the editor JS error is back that was fixed in 405.
0
Hello Brian Adle,
It seems that this is a timing issue and depends on how fast you perform the steps. The attached build addresses this.
Best wishes,
Alex Gyoshev
the Telerik team
It seems that this is a timing issue and depends on how fast you perform the steps. The attached build addresses this.
Best wishes,
Alex Gyoshev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items