I upgraded My MacBook Pro to OSX 10.9 hence my safari was upgraded to 7 with good expectation.
First thing I observed that Safari 7 does not take my CustomUserAgent from ~/Library/Preferences/com.apple.Safari.plist.
I stopped safari, made manually CustomUserAgent entry in ~/Library/Preferences/com.apple.Safari.plist and restarted safari again but Safari does not take CustomUserAgent and continued with Default value setting in Developer Menu. Same setting used to work with Safari 6.0.5/6.1.
Could you guys help me to figure out this issue?
Regards,
Anand Choubey
10.9 Preferences are cached. Please check below link for more details.
http://hints.macworld.com/article.php?story=20130908042828630
I suggest, modify Preferences should be done either use defaults command or
CFPreferencesSetValue in programming.
Preferences should not be modified through hand.
Regards,
Anand Choubey
Related
The script is crashing on Chrome version 103 only it's still running on 102. In one instance, it ran but crashed while executing a loop for its fifth time. It is selenium + python. What should I do?
this issue came with chrome 103. Remove the user-data-dir option for solution.
It was fixed for me when I removed the user-data-dir option.
It looks like this problem will go away when chrome 104 is released, we'll be dealing with workarounds until chrome 104 comes out.
https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121
https://github.com/SeleniumHQ/selenium/issues/10799
New Answer
Chrome Version 103.0.5060.134, selenium is now working as normal
Old answer
I actually:
Uninstalled Google Chrome
Restarted the computer
Installed an older version of Chrome(whilst the Internet is OFF)
Run MS config & disable Chrome auto-update
Restart the computer.
Now it runs just FINE.
NB: This can make your computer vulnerable to attacks so don't use your main PC. Use Isolated Environments
.
When I try to debug it shows this dialog:
Error dialog
And when I clock "fix" It shows this:
Web Browsers dialog
I can't solve this problem, any suggestion? Also I am developing a react native app. But i don't think that's the problem...
I am running Intellij Idea in Elementary OS.
This is expected - debugging is only supported in Chrome and browsers of the Chrome family, as it's clearly stated in Help. So, when you start the debugger, the IDE will try to open Chrome regardless of the browser chosen in run configuration. You need to make sure that Chrome is installed and the correct path to it is specified in Settings | Tools | Web Browsers.
We used to support Firefox Remote Debugging (but without source maps) through the FireFox Remote run configuration, but our solution doesn't work in the latest Firefox versions due to changes in the protocol, and there doesn't seem to be an easy way to fix it. We've made some progress recently, but there are still some blocking issues
related ticket: WEB-45986
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!!
So, I'm developing my rails applications on my mac, thro WEBrick at 0.0.0.0:3000 and I need to test how the layout are showing on PC running Windows with Internet Explorer 7 and IE8.
I have tried to test it thro Wine + Wine Bottler, but I can't access that point.
And now I'm thinking to install VirtualBox to give a try, but before doing this, it will be good to know from others if it will or not work for me in this case.
Any advice?
Thanks!
I use VirtualBox for interface testing. I've had no problems with it at all. I have an external drive with various disk images for firing up various versions of Windows and thus various versions of IE as well as Firefox and Chrome. Works a treat and no complaints.
We have used VirtualBox and a program called IETester:
http://www.my-debugbar.com/wiki/IETester/HomePage
It works well, even for IE6 although there are some very minor differences for IE6.
Makes it very quick to test in all versions of IE as you can have a tab for each.
Give it a go.
Anyone that has installed the new IE9 know if I can keep IE8 installed? I do a lot of web testing and don't want to update to IE9 if I loose IE8.
best way is to install a Virtual Machine
Per Microsoft:
If you are running Windows Vista or
Windows 7 on your computer, you can
install the Internet Explorer 9 Beta
to replace your existing version of
Internet Explorer. After you install
Internet Explorer 9, you can uninstall
it to restore the previously installed
version of Internet Explorer.
So no, it will overwrite IE8 (at least the Beta will. I suppose this is not guaranteed to be the same for the release version).
I use Virtual PC with images of the browsers I need to test, but also and more lately, IETester, http://www.my-debugbar.com/wiki/IETester/HomePage. It allows you to run multiple versions of IE side by side.
If you want to be able to play with the new features of IE9 without installing the entire browser (which will replace IE8) you can install the Platform Preview. The PP is stand-alone, includes the latest features and bug fixes and has been getting updated roughly every 8 weeks. You can get the latest Platform Preview at:
www.ietestdrive.com
FYI: the production IE 9 does not accurately reproduce IE 8. I've got a CSS issue I'm chasing down now because IE 9's IE 8 mode isn't the same as real IE 8.
If you are concerned with testing how your site looks in IE8/7, you can use the Developer Tools (press F12) to switch the Browser modes and Document modes so that IE9 interacts with the web server as a different user agent, and renders the HTML document according to the version rules.
http://msdn.microsoft.com/en-sg/ie/ff468705(en-us).aspx#_New_Dev_Tools
IE9 beta is released as a Windows update, so after installing it and playing around, you can remove it from Programs and Features -> Installed Updates, which will recover IE8.
hit f12 on ie9, it will pop up the debug console. In the menu there is a browser mode option where you can set the browser to display as ie8 and a bunch of other versions too.
Also, if you're mouse focus is on the console and you hit ctrl+r, it will clear your browser cache... This is a feature that all the other browser debuggers lack.. ability to quickly clear cache.... I'm rambling now.
The best way to see your site on old versions of IE is that:
If you have IE9+, open your current version of InternetExplorer, press F12, click on "Browser Mode" tab, then choose the version you want.
see screenshot here:
Works better than IE-tester, and easier than using virtual machine.