3426377 - Changing browser control doesn't seem to work in SAP GUI for some transactions

There are many behaviors which are dependent on browser control, and many limitations affect one browser control and not the other. Most of them are detailed in 2913405.

Sometimes even when the user changes the browser control via SAP GUI Options, e.g  edge browser control has been set but the transaction still invokes internet explorer (or vice-versa). This makes it seem that changing the browser control is not having effect on the GUI.

Typical behaviors that might stems from this are such:

• A limitation detailed in 2901278 - SAP GUI HTML Control based on Chromium Edge: Legacy HTML does not work (correctly) / present limitations persists regardless of the selected browser control.
• Web-transactions (e.g, SOAMANAGER, SLAW2, SOLMAN, and so on) do not open in Microsoft Edge (based on Chromium) but in Internet Explorer, even though the HTML control settings in SAP GUI options dialog> "Interaction Design">"Control Settings"  is set to "Edge (based on Chromium)".

SAP GUI for Windows 8.00.

ABAP PLATFORM - Application Server ABAP.

SOAMANAGER, SLAW2, Microsoft Edge, Internet Explorer, fallback rule, HTML control, wrong browser, IE, SAPBrowserConfManager, GetAllowedBrowserStr, QS Med, med, QS-MED, Ishmed, ish-med, ish med, regardless of browser, independent browser, limitation, edge, both browsers, both browser control, issue with both controls, egde/ie, limitations, blank, both browser controls, regardless of control, regardless of browser controls, regardless of browser control, error, errors. , KBA , BC-FES-CTL , SAP GUI for Windows Controls , Problem