cancel
Showing results for 
Search instead for 
Did you mean: 

Enterprise portal problem after chrome 115/116

0 Kudos
5,429

Hi

We are running Enterprise portal 7.5 SP24

After Chrome 115 (and still in 116) we are facing problems with opening OBN navigation from a WDA , sizing of iViews with WDA of KM Navigation, eventing between applications.

Are anyone facing similar issues?

Thanks

/Jakob

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Setting this may provide resolution:

chrome://flags/#origin-agent-cluster-default set to DISABLED

jorjey1
Discoverer

It works.

thanks.

arvindhoshiar
Discoverer
0 Kudos

Thanks Mr Cooper

Resolved at the movement

khigby
Explorer
0 Kudos

Works for me as well.

0 Kudos

Working fine, when manually we do the above settings. Kindly help us for permanent solution on this regard.
[ There will be Multiple End users. we cont. say them to do this settings manually ]

Answers (5)

Answers (5)

EduardoGzz
Explorer

Check if it is related to note 3159245. We implemented the solution proposed and it resolved the issue.

Thank you

0 Kudos

Hello Eduardo,

Can you tell me which solution you implemented? I see two options listed on that note

thanks

Brian

EduardoGzz
Explorer
0 Kudos

In our case it was 1831525 in our Portals, along with ABAP notes 3154411, 3163365, 3161114, 3194092; for ABAP it will depend on your system patch levels so I would start with 1831525.

We looked at changes to the browser but that would require us to do a company wide policy to deploy to all users; also since the problem was Chrome only, it would be just a matter of time before it makes it to Edge, being it is chromium based.

Hope that helps.

Eduardo

nstrik
Discoverer
0 Kudos

Our BASIS team also implemented option 2 in note 1831525 and based on our initial testing, it seems to be working for us as well.

Steve_S
Explorer
0 Kudos

I believe this should be the Best Answer. As this is not just a Chrome issue.
We used 3159245 Option 2, our ABAP Sytems are already at a high enough patch level.
So, we just needed to implement 1831525 in our Portal Systems and that fixed the issue while using Chrome.

MS will disable "document.domain" in Edge 118.
https://learn.microsoft.com/en-us/deployedge/edge-learnmore-origin-keyed-agent-cluster

Link to Edge Release dates (118 released on week of 12-Oct-2023)
https://learn.microsoft.com/en-us/deployedge/microsoft-edge-release-schedule#microsoft-edge-releases

Steve

0 Kudos

Hi

We have tested the group policy in the note mentioned

https://chromeenterprise.google/policies/#OriginAgentClusterDefaultEnabled

And that seems to solve the problem for the users who previously had problems

chrome://flags/#origin-agent-cluster-default

jjee
Member
0 Kudos

hi all,

We are facing exactily same issue with OBN navigation in chrome(115,116)

Edge is fine but users want to use chrome.

If anyone knows how to solve that, please leave here.

thanks.

jorjey1
Discoverer
0 Kudos

Now I switched to Microsoft edge but I prefer to use google chrome.

0 Kudos

Hi

Yeah that works for us as well, but for how long since Chrome/Edge are built on the same engine

/Jakob

0 Kudos

Hi Brian

I'll update here when we find a solution, please do the same

/Jakob