Forum Discussion
uwebbrowserparser.cpp, UWebBrowserParser::DocumentComplete
Thank you for your response.
We are using the most recent F5 client. And yes I agree with you regarding the Edge Client using the native embedded browser vs. system default browser. I beleive this is the root cause of the issue. However, I looked at the Okta link you pasted and I'm not seeing where it mentions the setting to use the system default browser on the Edge Clients.
What is your Edge client version as it could be a bug using the embedded browser? Also look at this link and supplement articles as a browser plug-in should be installed with the edge client installation https://support.f5.com/csp/article/K99054837
- pashaJun 01, 2022Altostratus
Edge Client is 7221,2022,412,1126 (I think that is the latest available?)
And yes, I agree it could be a bug (or some kind of incompatibility) with the embedded browser. The embedded browser is running a legacy version of IE10/11 rendering engine. I'm still not clear how to get the client to open the system default browser instead. The link pasted suggests that F5 is telling users to only go through the web browser to connect instead of using the Edge Client. We still want to leverage the Edge Client but have it open the system default browser instead of the embedded browser.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com