JavaScript/jQuery Code Run From BIP Portal iFrame Runs in Edge But Not in Chrome For Some Users.

[David Briars]

Our site has a BIP, and related JavaScript/jQuery code, built by a consultant about three years ago.    

The BIP has a container that calls a fex in the repository.  

The fex in the repository creates a tree style menu structure of report fexes that could be run.  The tree is created with JavaScript and jQuery within the -HTMLFORM construct.  

At some point the tree stopped fully rendering, upon clicking on the top level, in Chrome, for some users. 

The tree does render and is clickable in Edge for all users. 

Has anyone seen anything like this and have any ideas?  

F12 Dev Tools isn't showing any errors.   

The BIP would have been built with our current release 8207.  

 

 

 

[Patrick Huebgen]

Which portal are you using? the older BIP or the Designer Portal?

Could be a conflict in JQUERY versions ?

Please make sure to clear browser cache in Chrome completely - Edge is based on Chromium as well - both use are the same rendering engine and should not show very different behavior.

What happens if you use the fex outside of the portal?

 

 

 

[David Briars]

Thank you for your ideas of things to try/think about Patrick.  (The portal in this case is the older BIP.)    

[Clayton Peacock]

The output for the tree is probably an AJAX request returning a JSON/XML file structure or a fex creating the structure for the tree via webservice call or client adapter.

I would limit the tree to specific workspaces to try and figure if there is a specific workspace that's returning content potentially that has special characters or content is truncated possibly field length not long enough and truncating closing tags.

Possibly the tree working for some users is based on their security and access to workspaces which leads me to believe that there is a specific workspace thats recently been added thats giving you the problem and might not be browser related. 

[David Briars]

Exactly correct: the output for the tree is from an AJAX query request returning data from a WebFOCUS RESTful call- 'IBIRS_action=get'.

Excellent ideas to check if it is specific workspaces causing the issue.  I will check.  

Thank you Clayton.  

 

 

[Patrick Huebgen]

@David Briars - sometime the WebFOCUS built in session monitor is quite handy as you can debug everything down to the Fex level as well as the JSON answer sets