We're having issues with some recent versions/patches of IE11 (esp. 11.0.42)
The Framework function LaunchToPage doesn't load the requested page anymore, but stays on the default homepage.
After some checking on IE developer forums, I came up with the following workaround, but if other users are having similar issues, this should be fixed in the Framework itself [otherwise these changes will be lost during Framework upgrades]. I have this issue in ES versions 12.3.6 and 12.4.5
FIX: change the following lines in the LaunchToPage function:
'Dim oApplication As InternetExplorer
Dim oApplication As InternetExplorerMedium
'Set oApplication = CreateObject("InternetExplorer.Application")
Set oApplication = New InternetExplorerMedium
Solved! Go to Solution.
Thank you very much for sharing the idea of using the InternetExplorerMedium
object in the Framework. The Enterprise Synthetic Monitoring team will seriously consider this idea for the future service
packs and releases.
By the way, looks like (but it has not been tested yet) CreateObject should also work if you
as an argument.
Starting from ESM version 12.5.2 it is possible to use
InternetExplorerMedium object with the Framework. Here are some details:
Here are the details:
Even though VBA does not allow creating subclasses, but it
understands subclasses.InternetExplorerMedium is a subclass of InternetExplorer, so modifying
Dim line as suggested by Jeroen is unnecessary.
The implementation allows to use different methods of
creating an object that allows to reference Internet Explorer in the
script.Predefined methods could be
chosen by setting IEObjectCreateMethod property. Normal_1 and Normal_2 values are
for using InternetExplorer, Medium_1 and Medium_2 values are for using InternetExplorerMedium. Also the user has an option of introducing
their own way of creating the object by modifying UserCreateIEObject function. Such diversity is provided for the case if
there are some more nuances that may affect Internet Explorer behavior.