Editor Issues with Firefox 17

[Jeremy]

Currently when using the Editor within Firefox 17, it does not gain focus nor permit any kind of editing. This issue does not appear with either the latest Chrome or IE.

Currently using the Build: v2012.3.1114 with MVC 4.

Other factors is that this is being used as part of an Popup-editor template with Kendo Grid.

Cheers,
Jeremy

[Jeremy]

Never mind! Latest Hotfix fixed all issues.

 EDIT: Nope, still not working properly, nothing displays still and nothing gains focus.

[Daniel]

Hello Jeremy,

This is a known issue in Firefox when using the Editor in a Window. The browser reloads the Editor iframe so the HTML is cleared and the content becomes not editable. We are currently investigating what is causing this behavior and will do our best to fix it for the next releases. A workaround for now is to trigger the "DOMNodeInserted" event on the container in the edit event:

function edit(e) {
    e.container.trigger("DOMNodeInserted");
}

This will cause the editor content to be recreated and it should work as expected.

Regards,
Daniel
the Telerik team

[John]

Still not working for me. I'm using the editor in a pop-up editortemplate.

Has this been resolved yet?

[Alex Gyoshev]

Hello Jeremy,

We are currently looking into solutions for this problem. I will update this thread with our findings tomorrow.

Greetings,
Alex Gyoshev
the Telerik team

[Alex Gyoshev]

Hello Jeremy,

We have introduced the refresh method that allows re-initialization of the editing area. It will be available in the next internal build. If you wish, you could request a new internal build through a support ticket.

Greetings,
Alex Gyoshev
the Telerik team

[John]

I am using kendo editor as well in firefox and am noticing this bug. However in my case I am not using the popup editor but moving the textarea around. I have tried to call editor.refresh() after moving the textarea but that didn't seem to fix the problem.

Currently using build 2013.1.319.3

Has this issue been resolved?

[Alex Gyoshev]

Hello John,

Please try upgrading to the latest internal build or to the official service pack that will be released this week. The refresh method is part of the internal builds and the service pack.

Regards,
Alex Gyoshev
the Telerik team

[John]

thank you for the quick reply.

I have updated to the latest internal build and the editor is now receiving focus from mouseclicks in firefox. However, when I call the editor.focus() function, the editor does not receive the cursor in chrome or firefox. Is this a known issue?

[Alex Gyoshev]

Hello John,

We were not aware of this issue. We will attempt correcting this in the editor code -- you can work-around it by calling the selectRange method with the editor selection, as shown in this jsBin:

editor.selectRange(editor.getRange());

Kind regards,
Alex Gyoshev
the Telerik team

[Colin]

I don't quite understand at what point I'm meant to call refresh. If I create the editor and then call refresh, the result is the same as before in FireFox.

e.g.

    $(document).ready(function () {
        $("#myEditor").kendoEditor({
            tools: [
                "bold",
                "italic",
                "underline",
                {
                    name: "myPlaceholder",
                    template: $("#myPlaceHolderTemplate").html()
                }]
        });

        var editor = $('#myEditor').data("kendoEditor");
        editor.refresh(); // This doesn't do anything that I can see at this point.

        $("#refreshOnFFButton").click(function () {
            // click event of an input button
            console.log("refresh button pressed");
            editor.refresh(); // This allows the editor to work. 
        });
} // NOTE: Some code omited for brevity.

If I put a button on the pop-up dialog and press it then everything works correctly. At some point between the code that creates the editor and the code that handles the button click is the point that I should be calling refresh (I obviously, don't want to have to tell the users to press a button just to get the editor to work)

Is there some event I should be subscribing to that tells me when everything is in place and I can refresh the editor?

[Alex Gyoshev]

Hello Colin,

The method should be called after the editor has been moved in the DOM, due to a firefox bug. It all depends on the code, so you might want to do it after the editor has just been shown to the user.

Greetings,
Alex Gyoshev
the Telerik team

[Colin]

Yes, I realise that. However, what I'm asking is how do I determine that? There seems to be nothing to say, "Yes, I'm ready to be refreshed now"

At the moment the workaround that I'm using is that when the dialog appears I force the focus to the first textbox, when that loses focus (blurs) I call refresh because by that point I know that the Editor has now fully rendered. This is fine if the user tabs off the text box as there are other controls between it and the edit area. However, if they click directly in the editor area it hasn't been refreshed yet so they have to click a second time which is rather annoying.

You say "so you might want to do it after the editor has just been shown to the user" - Is there an event that says "I've just been shown to the user"? If I put refresh in right after creating the Editor nothing happens that I can see. If there isn't an event like that, is there any other way to determine that?

[Alex Gyoshev]

Hello Colin,

Since you are showing the editor in a dialog, a convenient time to refresh the editor would be when the dialog appears (in case you are using the Kendo window, you can do so in the activate event).

All the best,
Alex Gyoshev
the Telerik team