|
Furthermore, the user supplied user-extensions.js will be correctly loaded if the -proxyInjectionMode is added. However, there are other issues with the -proxyInjectionMode flag (IE throws up because it does not recognise the @SESSION_ID@ token - but that looks like a different issue). The root cause of this is that when the iehta custom profile dir is expanded, the file specified on the commandline does not get copied over. Here is a patch for the HTABrowserLauncher which will overwrite the unpackaged one with what was specified on the commandline. -adam Applied adams patch in r2268. Loading of user-extensions for *iehta worked in my test after the patch. |
|||||||||||||||||||||||||||||||||||||||
Same thing observed in Selenium 0.9.2
I put a javqascript alert() in the user-extensions.js within selenium-server.jar, and it poped up.
Maybe the -userExtensions switch is being ignored in *iehta mode?