I'm using Chrome 59.0.3071.115 and Chromium 61.0.3159.0 (snapshot build) on OSX in headless mode, launching them from a terminal with these flags:
chrome --headless --disable-gpu
Everything works as expected, but a Chrome/Chromium dock icon is always displayed during their execution.
Is there a way to execute them in headless mode without having this icon always being displayed?
It looks like this is a bug.
https://bugs.chromium.org/p/chromium/issues/detail?id=750505
I hope the Chromium developers will fix this soon. You can star the issue in the meantime.
Related
For about a week, Chrome dev tools has been completely blank every time I try to use it on my Mac (screenshot). I have reinstalled it but to no avail. Once I open dev tools, the specific tab seems to break - I have to open a new tab to be able to navigate, and none of the dev tools tabs & buttons work, so I cannot use any of the suggestions included here:
Chrome dev tools console completely blank
I am using High Sierra 10.13.2 & chrome Version 63.0.3239.132 (64-bit)
Any tips would be greatly appreciated
Download Chrome Canary and see if the problem is fixed when you run the latest Chrome code. If it's fixed, then there was just some temporary regression that's causing Chrome to break.
If the issue is still there when you run Canary, file a bug!
I've been searching around for a way to run our Behat (PHP dist of Cucumber) tests on Safari, however we encounter the problem of Selenium Safari Driver not being able to use simple click functionality, which is breaking the majority of our browser tests.
As Safari (at time of writing this post) is around 9% of all browser usage, according to browser stats, it is a necessity to test it.
The click functionality works with Chrome, Firefox and Opera.
Does anyone have any solutions?
Mac OSX 10.11
Safari 9.0
Selenium Safari Driver 2.47.1
Latest SafariDriver.safariextz
Behat 2.5.3
It seems as there is still an open issue concerning the Selenium Safari Driver with Safari 9. You could try to apply the suggestion in one of the comments.
Since two days the Chrome Dev Tools stopped working. I opened/closed Chrome. I restarted my MacBook but nothing worked. I tried to open the Chrome Dev Tools and no window is opening. I tried to solve it with the following trick: [1] but I don't have the file chrome-devtools_devtools_0.localstorage-journal there. Maybe this is because my problem is slightly different because on my MacBook the Chrome Dev Tools aren't showing up anymore.
When I execute the following command:
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --user-data-dir=/tmp/whatever
Everything works fine again. So I fear that my Chrome Profile is somehow destroyed. Is there a way to get the Chrome Dev Tools working without deleting my Chrome Profile? Deleting the profile would be the worst case. Hope someone could help me.
My Chrome Version is: 48.0.2564.116 (64-bit)
My Macbook is: OS X El Capitan 10.11.2 (15C50), MacBook Pro (Retina, 15', Mitte 2014)
EDIT:
I started Chrome with:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --log-level=0
Then I got the following error message:
Uncaught TypeError: Object.observe is not a function", source: chrome-devtools://devtools/bundled/inspector.js (10681)
After pasting this error into Google I found the following thread https://bugs.chromium.org/p/chromium/issues/detail?id=549225#.
Is this expected behavior that I can not open the dev tools when javascript-harmony-shipping is turned on? With javascript-harmony-shipping turned off everything works as expected
[1] https://stackoverflow.com/a/28866632/1280401
Actually it seems to be a bug with javascript-harmony-shipping. Further details can be found here: answer from Paul Irish in Google Groups
I would like to know how to uninstall the FireFox simulator from the Mozilla browser.
Because I have this message error on top of the window:
ReferenceError: debuggerSocketConnect is not defined
P.S: The simulator starts perfectly!
Enter about:addons in the URL bar.
Look for the Firefox OS versions you want to get rid of and click the delete button.
When I have the inspector open in chrome it will "break" all over the javascript even if there are no breakpoints. On sites that I need the debugger to debug javascript this makes chrome pretty unusable.
I'm on a mac, and I have tried deleting and reinstalling chrome. Anyone have any suggestions?
Gracias everyone!
You could have had the "Pause on all exceptions" button enabled (it would be blue if enabled).
See screenshot below:
On Chrome 33.* you'll see it when viewing a script:
I eventually resolved this by uninstalling chrome, removing this directory: ~/Library/Application\ Support/Google/Chrome/ (I'm on a mac) and reinstalling. Not sure whether the deleting chrome step is really necessary.