Window.Open (IE vs Chrome) Issues

[mrojek]

Hello,

We are currently having an issue with a window.open command we are using, along with the parameters passed to our CL using Profound's parameters on the Atrium. Here is the code below:

var BOMInquiry = pui.get("T1_ViewLink." + row);
window.open(BOMInquiry,"_blank");

When using Internet Explorer, the code works, and generates the following link:
http://mcgas400:8080/profoundui/auth/st ... p1=P00075P 202001Q&l1=256

When using any other browser (Chrome, Firefox, Edge), this is the link that is generated, it's applying %20's for the spaces...
http://mcgas400:8080/profoundui/auth/st ... 01Q&l1=256

The link generated by Chrome, Firefox or Edge crashes the program and we get a point error, see the screen shot attached.

Any ideas why this is happening? Being that Internet Explorer end of life is next year, would like to figure out what we can do for this going forward.

Thanks!
Mike

[Scott Klement]

Converting the spaces to %20 is normal. Internet Explorer is doing it, too... its happening under the covers where you can't see it. It would not work if they weren't being converted, spaces in a URL are not valid or possible in HTTP. That's why they are encoded as %20, and then will be decoded on the server back to spaces.

Its hard to tell what the problem is without being familiar with the code in the program. I would guess its trying to use a parameter that wasn't passed. Atrium passes only one parameter, and it is always 256 characters long. Perhaps the program is trying to treat it as if two were passed? Thats the sort of thing that would only work sporadically.