I'm trying to run my code in some browsers. It works fine in Firefox and Opera, but in IE9 and Chrome it only works fine the first time.
After, when I want to run this code or another again it shows me the next warning:
"Resource interpreted as Script but transferred with MIME type text/html:"http://www.superfish.com/ws/sf_main.jsp?dlsource=dropdowndeals&userId=RR8BRgZAQDCRcXxJEAgX1g&CTID=1049999"."
However, if I delete the cache of the browser and run the code again, the code run without problems, but only the first time of course.
This problem is only on Google Chrome and IE9.
Do you have any suggestion, please?
Thanks!!
I ran into this on a users machine. It looks like it's AdWare that tries to parse the script tag, but doesn't like it when the type isn't javascript. If you use AdBlock or similar for the browser it should work, but this is just covering up the problem.
The end game would probably be to remove the adware completely.
Related
I have a MacBook Pro(macOS Big Sur v 11.4). I am unable to run my test suite in different browser languages like (German, Spanish or French).
I use this command testcafe 'firefox --lang=es' and I have tried both firefox and chrome, I tried --lang=fr and --lang=ger but nothing works.
I tried with double quote testcafe "chrome --lang=fr-Fr" as well.
Everytime I run my test, it execute successfully with no error but always run in English browser language.
And one more thing above code works fine on windows machine.
It seems that on macOS, this method doesn't work out of the box whether or not you use TestCafe.
If you launch chrome with the --lang=fr-FR flag from the console directly (without TestCafe), it will not give the desired result.
Please see the following article and let us know if it helps: https://gist.github.com/kentbrew/e9449acd12c1ef2d78b5b473f615d23b.
does anybody have a problem of selenium tests failing on new safari version 13.
Ran the same tests on chrome and firefox and it works fine. Also tested it on older version of safari and it works fine.
I didn't manage to pin point exactly where it fails. One case I did notice is that on safari 13 selenium click on <div role='button' aria-haspopup='true'>....</div> invokes no action(in my case opens a popup menu). And test proceeds to the next line of code. note however at this point I am not claiming that this kind of click always fails, it's just where I noticed it in my tests.
If anyone came across this kind of issue on safari 13 please provide your input.
Thanks
Safaridriver maintainer here.
This is a known issue that we believe has already been fixed in Safari Technology Preview Release 91. Please verify whether the issue reproduces using latest STP's safaridriver, and reach out to me on Twitter, #brrian.
There is an issue with SafarDriver or Safari 13. Please vote the bug in WebKit https://bugs.webkit.org/show_bug.cgi?id=202589
I am also facing the same issue with Safari 13.0 and Safari 13.0.1. Till Safari 12.1.2 everything was working as expected but since my browser updated to v13.0 selenium script is broken.
I observed that Selenium clicks on other locator instead of the target (identified) locator. For ex. if you want to click on a button (//button) it clicks on the //div which is the sibling node of that //button in the DOM.
My workaround solution:
As I didn't update MacOS Catalina yet and only Safari 13 was updated; I was able to download the "MacOS Mojave installer". Then, I installed it as an update; resulting it rolled back my Safari version from 13.0 to Safari 12.1.2. Now my script started working again!!
I have a program that has been working for quite a while. Not sure what happened, but all of the sudden it crashes. It looks like it is trying to access something on the page when this happens. It launches Chrome, gets to a login page, but then it crashes when trying to grab the login. Happens with multiple sites, so it isn't a site change or anything like that.
I tried converting to Firefox and InternetExplorer. However, because Chrome lets you download a file without prompting, that is what I know will work. I tried with FF creating a Profile and with IE creating a registry setting (to allow auto-download). Neither worked :(
I want to go back to Chrome, but not sure what is wrong. I even uninstalled Chrome entirely and re-installed it. Nothing :( I tried setting ChromeDriver.exe to "Run as Administrator" - nothing crashed, but also nothing ran.
I'm at a loss :(
the latest version of chrome has a rendering bug which is causing errors when working with selenium, you can try installing the latest chromedriver but it might be better to try to find a work around with firefox for now
I have a project suite of automation tests that uses Protractor and Jasmine. As of a couple months ago, my tests stopped working in FireFox. Everything works perfectly in Chrome, and almost perfectly in IE.. because why would IE work ya know.
There have been multiple posts about this and I've read through all of them, but I haven't been able to determine if there's a workaround/solution to this. It's not entirely a HUGE deal if my tests run in FireFox, but with a web application it's mighty nice to be able to test all instances.
Basically what happens when I run a test in FireFox:
Command prompt acts like everything is about to run properly (FireFox driver starts up.. server remains running etc etc)
Firefox opens for a split second (icon appears on the task bar, browser flashes on the screen and closes)
After a good minute or so protractor gives me the following message:
[firefox #01-0] WebDriverError: Unable to connect to host XXX on port XXX
after 45000 ms.
With a ton of DEBUG lines referring to JSON files and Firefox addons.
Any thoughts or other sources I could check out would be sweet. Many thanks in advance.
Problem is with latest Firefox support from latest selenium-server. Use geckoDriver and it will work.
Follow this URL
I have a question regarding Selenium and the current Microsoft updates:
I just installed the newest Microsoft patches on a PC and now the Selenium scripts won't work anymore. I'm using the Selenium IE Driver 2.44.0 in the scripts. Maybe something has changed in the Internet Explorer, I'm not sure. Suddenly the scripts can't find any web elements on the page anymore. An InvalidSelectorException is thrown because the findElements methods can't be executed. The IE driver opens up and it navigates to the given URL, but when it tries to find a web element, the script fails. I also tried it out on a PC which hasn't the newest updates installed yet and the scripts are working fine there, there are no problems at all.
Do you have any ideas what to do or what could be the cause?
Thanks a lot!
Yes as I stated here
If you have taken windows update KB3025390 IE will not work as expected. There is currently no resolution to that yet.
Also, Uninstalling the update KB3025390 should make the WebDriver work correctly with Internet Explorer 11. See this answer