Broken dialogs under Chrome

4 posts, 0 answers
  1. Telerik Admin
    Telerik Admin avatar
    1572 posts
    Member since:
    Oct 2004

    Posted 20 Nov 2013 Link to this post

    Chrome 31 causes (some of) the RadEditor dialogs to break - they become very small and unusable when the content is received: http://screencast.com/t/XYWdPxSYloE.

    This seems to be a browser issue and it does not manifest with the next official beta. The investigation is ongoing and if the problem is not fixed in the next official Chrome release fixes will be considered in our source code.

    In the meantime, there are two possible workarounds:

    1) force a resizing of the dialog when the command is executed:
    <telerik:RadEditor runat="server" ID="RadEditor1"
        OnClientCommandExecuted="editorCommandExecuted">
    </telerik:RadEditor>
    <script type="text/javascript">
        function editorCommandExecuted(editor, args) {
            if (!$telerik.isChrome)
                return;
            var dialogName = args.get_commandName();
            var dialogWin = editor.get_dialogOpener()._dialogContainers[dialogName];
            if (dialogWin) {
                var cellEl = dialogWin.get_contentElement() || dialogWin.ui.contentCell || dialogWin.ui.content,
                frame = dialogWin.get_contentFrame();
                frame.onload = function () {
                    cellEl.style.cssText = "";
                    dialogWin.autoSize();
                }
            }
        }
    </script>


    OR

    2) use browser windows instead of RadWindows for the dialogs:
    <asp:ScriptManager runat="server" />
    <telerik:RadEditor runat="server" ID="RadEditor1"
        OnClientLoad="OnClientLoad">
    </telerik:RadEditor>
    <script type="text/javascript">
        function OnClientLoad(editor) {
            if ($telerik.isChrome)
                editor.set_useClassicDialogs(true);
        }
    </script>

  2.
  3. MailUp Dev
    MailUp Dev avatar
    6 posts
    Member since:
    Nov 2009

    Posted 08 Jan 2014 Link to this post

    Workarounds are not useful, I would not release this upgrade with this sort of problem, half of our clients are currently using Chrome.

    Unresolved problems:

    1) The first workaround keeps the "Image editor" broken (still very small and unusable, like the "Image Manager" before the workaround).
    2) The second workaround (popup) is really bad looking and applies to all the modal windows, not only the Image Manager: not usable.
  5. Marin Bratanov
    Admin
    Marin Bratanov avatar
    5347 posts

    Posted 10 Jan 2014 Link to this post

    Hi Alberto,

    We had tested the workaround and it worked on our end. Moreover, Chrome 32 is being pushed already and  the issue is resolved there. I am attaching here videos from the behavior on my end.

    A suggestion you can try is adding a timeout around the autoSize() call and/or using autoSize(false).

    As for the second workaround - the classic dialogs are not designed at present and are primarily an accessibility fallback in case the developer does not want to use HTML/JS based popups. The issues with the image manager dialog under Chrome 31 is not isolated and it spans to other dialogs as well.


    Regards,
    Marin Bratanov
    Telerik
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
  7. MailUp Dev
    MailUp Dev avatar
    6 posts
    Member since:
    Nov 2009

    Posted 13 Jan 2014 Link to this post

    Thank you Marin,

    the first workaround works, but we don't like having (eventually multiple) pop-ups in our application. 

    Also with Chrome 32 beta everything works fine.
    We will wait until Chrome 32 is released before installing the new Telerik library version. Hope soon, I can't find info about release schedule.

    Best regards,
    Nazzareno
  8.
Back to Top