Telerik RadEditor Image Manager Window Not Displaying Properly

4 posts, 0 answers
  1. Joel
    Joel avatar
    2 posts
    Member since:
    Apr 2014

    Posted 12 Dec 2014 Link to this post

    I am using the Telerik RadEditor and am seeing some strange behavior with the Image Manager window, shown in the attached image.  The tabs such as SiteCopy, Body Setup, Header Setup, etc. are all from the page that should be behind the window, yet they are somehow showing through. Clicking and dragging the window to another location on the screen fixes that issue, however, the window cannot be closed using either the X or Cancel. This only seems to happen in Chrome when I am zoomed in a bit on the page. Is this a bug with the Image Manager or is there something that can be done to prevent this behavior?
    Thanks
  2. Ianko
    Admin
    Ianko avatar
    1535 posts

    Posted 15 Dec 2014 Link to this post

    Hi Joel,

    The problem most probably stems from z-index values, i.e., the z-index of the TabStrip's tabs are with higher value than the one of the RadEditor dialogs.

    In a plain scenario, without any custom CSS the tabs stay properly behind the modality of the Image Manager.  Therefore, this might be are result of some custom CSS implemented in the used page. You can investigate the rule affecting the tabs via the browser's dev toolbar and remove it. 

    If you are unable to resolve the issue, you can try to isolate this into a simple project and provide it, so that I could examine it properly and find the origin of the problem.

    Regards,
    Ianko
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Joel
    Joel avatar
    2 posts
    Member since:
    Apr 2014

    Posted 18 Dec 2014 in reply to Ianko Link to this post

    Hello Ianko,

    Upon further inspection, it seems that this issue occurs when the window is scrolled down, not zoomed in.  In the console, the following error message displays whenever the issue occurs:

    Uncaught Sys.ArgumentOutOfRangeException: Sys.ArgumentOutOfRangeException: Value must be an integer.
    Parameter name: y
    Actual value was 8.272699999999986.

    Using the console to find this parameter, it seems that it occurs in the MicrosoftAjax.debug.js file somewhere in the Bounds or ValidateParams functions.  Here is the information at the top of the code:

    // Name:        MicrosoftAjax.debug.js
    // Assembly:    AjaxControlToolkit
    // Version:     4.5.7.1213
    // FileVersion: 4.5.7.1213
    // (c) 2010 CodePlex Foundation

    This is code from Bounds:

    $type = Sys.UI.Bounds = function Bounds(x, y, width, height) {
        /// <summary locid="M:J#Sys.UI.Bounds.#ctor"></summary>
        /// <param name="x" type="Number" integer="true"></param>
        /// <param name="y" type="Number" integer="true"></param>
        /// <param name="width" type="Number" integer="true"></param>
        /// <param name="height" type="Number" integer="true"></param>
        /// <field name="x" type="Number" integer="true" locid="F:J#Sys.UI.Bounds.x"></field>
        /// <field name="y" type="Number" integer="true" locid="F:J#Sys.UI.Bounds.y"></field>
        /// <field name="width" type="Number" integer="true" locid="F:J#Sys.UI.Bounds.width"></field>
        /// <field name="height" type="Number" integer="true" locid="F:J#Sys.UI.Bounds.height"></field>
        var e = Function._validateParams(arguments, [
            {name: "x", type: Number, integer: true},
            {name: "y", type: Number, integer: true},
            {name: "width", type: Number, integer: true},
            {name: "height", type: Number, integer: true}
        ]);
        if (e) throw e;
        this.x = x;
        this.y = y;
        this.height = height;
        this.width = width;
    }

    And the code from ValidateParams: 

    $type._validateParams = function Function$_validateParams(params, expectedParams, validateParameterCount) {
        var e, expectedLength = expectedParams.length;
        validateParameterCount = validateParameterCount !== false;
        e = Function._validateParameterCount(params, expectedParams, validateParameterCount);
        if (e) {
            e.popStackFrame();
            return e;
        }
        for (var i = 0, l = params.length; i < l; i++) {
            var expectedParam = expectedParams[Math.min(i, expectedLength - 1)],
                paramName = expectedParam.name;
            if (expectedParam.parameterArray) {
                paramName += "[" + (i - expectedLength + 1) + "]";
            }
            else if (!validateParameterCount && (i >= expectedLength)) {
                break;
            }
            e = Function._validateParameter(params[i], expectedParam, paramName);
            if (e) {
                e.popStackFrame();
                return e;
            }
        }
        return null;
    }
















  5. Ianko
    Admin
    Ianko avatar
    1535 posts

    Posted 19 Dec 2014 Link to this post

    Hello Joel,

    Thank you for providing additional information.

    There is a well known issue with Chrome 39 that causes the same JavaScript error as described. There are not strict steps or configuration setting that can enable us to properly isolate this issue and fix it. At this time we only can suggest possible workarounds to fix the issue until a proper resolution is found.

    More details and the possible workarounds are discussed in this forum thread.

    Let me know if I can help any further on the matter.

    Regards,
    Ianko
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
Back to Top