I had this error with a recent project i had. I don't use Selenium. I didn't even know about it but anyway.
I have no idea why this error happens but my guess, on your case, is that Selenium adds the HTA:application tag combined with a script on your page. can you right click on the selenium output and view the source? If so, please report the generated source.
Sorry for using the direct link scripts. i don't do that on my projects.
Hope that helps you solving this bug (?).
PS: does anyone have to contribute something in my previous post ? i had replied on a closed thread and i'm not actually sure if anyone inspected it... it is HTA related.
Thanks for the reply - unfortunately this doesn't seem related enough:
I can indeed right-click & 'View Source' - there are no HTA tags being injected into the application's HTML when browsed by *iehta
there are no HTA tags being injected into the application's HTML when browsed by *iehta
you mean that you actully did "Point a Selenium test at it", right?
What happens if you copy the source from the "Selenium output" in a new .hta file and run it?? I'm asking this because i have seen some projects that extend the mshta runtime and that could be the case of Selenium. In this case it could internally change the html code in runtime.
have you tried to test my "working" (2nd or 3rd code) example with Selenium?
EDIT: Just ignore this post. I had no clue on how this HTA mode of Selenium is implemented...
Last edited by stashx; 4 Feb 2011 at 7:53 AM.
Reason: Had no idea of how Selenium works
I noticed that this same test passes without the application attribute but there is no alert shown. Isn't this behavior wrong??
Enough said about the Selenium.. Use my patch and you'll be just fine i guess... If not, i suggest you should seek for more help on the Selenium community.
So download ExtJS, extract it in a folder named "extjs" in the same path with your testing html and make your testing html look like this code:
I just tried with the HTA tag &, as you predicted, it doesn't help.
I actually used local resources to start with - this doesn't help.
I will now try to compile a new .jar with the modified TestRunner.hta