PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 05/10/2016 6:29 PM by  Terry P
Design Studio custom screens on Chrome
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Ragu Raghavan
Private
Private
Veteran Member
(878 points)
Veteran Member
Posts:306


Send Message:

--
05/10/2016 5:55 PM

    Has anybody been successful in making the custom screens work on Chrome?

    I have custom screens that make DME calls that work on IE - but fail on Chrome 50.x, Design Studio v10.x.

    As far as I can tell, Chrome does not allow synchronous calls and a DME call makes a synchronous http call.

    This is the message on the developer tools:

    “Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/”

    Any ideas how to overcome this ?

    Thanks.

    Ragu

    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    05/10/2016 6:09 PM
    I had to modify all my DME calls to work with Chrome and Firefox as follows:

    //Construct DME string
    sDME = portalWnd.DMEPath + "?PROD=" + strPDL
    sDME += "&FILE=GLNAMES&INDEX=GLNSET1"
    sDME += "&KEY=" + vCompany + "=" + vNewRetirementAcctUnit
    sDME += "&FIELD=DESCRIPTION"
    sDME += "&OUT=CSV&DELIM=~&NOHEADER=TRUE"

    //Return value from table
    var sReturn = portalWnd.httpRequest(sDME,null,null,"text/csv")

    Ragu Raghavan
    Private
    Private
    Veteran Member
    (878 points)
    Veteran Member
    Posts:306


    Send Message:

    --
    05/10/2016 6:19 PM
    Thanks Terry. What do the two nulls do ?
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    05/10/2016 6:25 PM
    They are required placeholders for the call that are not used. This was the solution given by Support/Development when I opened an incident with them. Made the changes, and it resolved my issues when using other browsers.
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    05/10/2016 6:29 PM

    Here was their initial response:


    "In the custom script, some of the server requests uses ActiveXObject("Msxml2.XMLHTTP") which is not supported on Chrome/Firefox. This is the one that causes the error. We can use portalWnd.httpRequest as a replacement for it and it is already being used on other function in the custom script."
    You are not authorized to post a reply.