I am facing an issue in which my script is getting stuck in chrome because of an alert. The script is neither getting passed or failed, it's just stuck there and doesn't go forward at all due to an alert.
I have tried Driver.switch().alert() but no use. It seems nothing works if that alert comes up.
Could any one suggest any way to handle this kind of alert? The alert is nothing but a normal alert having an OK button and a check box which says to prevent any additional dialogues.
Could anyone please help here as this small issue has caused the script to stop at that point itself.
Thanks in advance.
Please note that I am using selenium 3.0 and it was all working fine till yesterday. Since today, I am facing this issue.
Please find the below link it may useful for your problem.
http://seleniumsimplified.com/2013/10/faq-why-does-selenium-not-work-with-this-alert/
Related
I am kind of new here, although I read often the posts, that is why, first of all, a big thank you for all the help we get here. If there is someone using Cypress, I have a problem with accessing a print dialog which is outside the DOM. I want to close the print dialog but I cannot access it using the Cypress commands. I had the same problem with Python and Selenium, but there I managed to install AutoGui and this helped me out.
Anyone had the same problem and found a solution to it? Thank you in advance.
** **
I have installed JComments on my site, installation went fine but can't post any comment. Send button has no respond. I tried some solutions from other forums but no help. If I change template it is working. Also working on my local machine.
Can someone help me with this please?
TNX
enter image description here
Typically, this is caused by a JavaScript conflict somewhere, you should be able to see the error by clicking on F12 and then clicking on "Console" in Google Chrome.
Having said that, it is probably a better idea to use Disqus instead of JComments because many users are already on the platform and because Disqus automatically filters out the spam for you.
I get this error on Firefox 24.0, and I have firebug, fireftp and colorzilla installed. This just started happening recently. I have searched for this problem but all the topics come up as being from 2-4 years back, mostly Firefox versions 3 through 4.
Anyone have an idea how to fix this? They work in IE OK.
This also appears to do this for the main list page:
https://drive.google.com/?pli=1&authuser=0#
that just hangs without showing ANY of my docs.
I struggled with this for weeks.
Finally what resolved it is pretty stupid... Not sure if it will work again.
But maybe it will help someone!
Instead of going to drive.google.com I just opened docs.google.com and after it forwarded me to drive everything started to work... without even a cache clean!
Pretty funny!?
I'm trying to import a script from one DB into another in FMP12 and found no other way then using UI scripting.
Most of the time the script stuck when I need to mark the checkbox, complaining that the UI element cannot be found, but as visible on the picture, it is referenced properly, at least this is how I see it:
Pls visit the link for the picture showing the problem, it is much clearer then if I write it down: https://www.dropbox.com/s/y8c7xuazrb5cvlq/Screenshot_25_4_13_3_08_PM.jpg
The funny think is that sometimes the script works fine and I cannot figure out what is making it working fine sometimes.
Any idea what am I doing wrong, or if there is some other way to refer to that UI element?
Thanks
Zsolt
In a lot of cases when my prototype.js javascript code hits an error, I don't get any error notification, line number, etc. I usually end up tracing through my code with alert statement until I find where it dies. Is there a better way to track down these errors?
Depends on browser, but there are some very good ways of handling errors. If you are using firefox, you can install FireBug and then use:
console.log('like an alert but in the firebug window');
It's alot quicker than pressing ok, then ok, then ok...
http://getfirebug.com/
Firebug also has an amazing JS error debugger, and gives great feedback as to what is wrong with your code. A must have if you ask me!
I already use Firebug ...
Is this case, try Chrome — I find that Firefox fails to notify me of errors in my code that uses Prototype.js, but Chrome is fine. Not that I'm a huge fan of Google over Mozilla.