As others have mentioned, the most exciting thing about Chrome 59 is that it is the first release with headless support. I wrote a guide a while back on running headless Chrome with Selenium that someone might find interesting if they're interested in trying out Chrome in headless mode [1]. It's quite a bit easier now that the stable channel is on version 59 and I just updated the guide to specify which steps are no longer necessary.<p>[1] - <a href="https://intoli.com/blog/running-selenium-with-headless-chrome/" rel="nofollow">https://intoli.com/blog/running-selenium-with-headless-chrom...</a>
Has there been any research on whether Material Design has superior UX for desktop use?<p>I've just tried the new settings screen on Chrome 59, and personally I find it far, far worse than what it was previously. I hate this trend of hiding essential top-level navigation behind a hamburger menu, especially on desktop.
I was expecting the easy path to display certificate view (removed in 56) to be returned in 59 [1], but apparently it will be in 60 behind a flag [2].<p>[1] <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=663971" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=663971</a><p>[2] <a href="https://textslashplain.com/2017/05/02/inspecting-certificates-in-chrome/" rel="nofollow">https://textslashplain.com/2017/05/02/inspecting-certificate...</a>
For those interested: headless is coming to Firefox as well.
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1338004" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1338004</a>
With the new optimizing compiler (Turbofan) landing, JavaScript `Exception` are now usable without significant performance penalty: great news !<p>A bit of context: v8 used to have troubles optimizing code which contained `try/catch` sections, which led to massive performance issues on hot parts of the code in Chrome and deterred a lot of people from using Exceptions in JavaScript (including node). Glad to see this bug finally fixed !<p>More infos on the new v8 stack here: <a href="https://v8project.blogspot.fr/2017/05/launching-ignition-and-turbofan.html" rel="nofollow">https://v8project.blogspot.fr/2017/05/launching-ignition-and...</a>
I thought they were dropping some support of SSL certificates in regards to symantec [0] starting in 59 but I see no mention in this post (unless I missed it). does anyone have further information? I am not familiar with blink process however allowing insecure creation of ssl certificates seems like the wrong way forward.<p>[0] <a href="https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/eUAKwjihhBs/rpxMXjZHCQAJ" rel="nofollow">https://groups.google.com/a/chromium.org/forum/#!msg/blink-d...</a>
The real update is in the DevTools: <a href="https://www.youtube.com/watch?v=PjjlwAvV8Jg" rel="nofollow">https://www.youtube.com/watch?v=PjjlwAvV8Jg</a>
Anyone seeing a failure in <a href="https://websocketstest.com" rel="nofollow">https://websocketstest.com</a> (Chrome 59.0.3071.86) ?<p><a href="https://websocketstest.com/result/7629067" rel="nofollow">https://websocketstest.com/result/7629067</a><p>It works fine on Firefox 53.0.3 and 55.0a1 (Nightly).<p>Console says:<p><i>scriptaculous.js:31 A Parser-blocking, cross site (i.e. different eTLD+1) script, <a href="https://ajax.googleapis.com/ajax/libs/scriptaculous/1.8.3/builder.js" rel="nofollow">https://ajax.googleapis.com/ajax/libs/scriptaculous/1.8.3/bu...</a>, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See <a href="https://www.chromestatus.com/feature/5718547946799104" rel="nofollow">https://www.chromestatus.com/feature/5718547946799104</a> for more details.</i><p><i>WebSocket connection to 'wss://wss.websocketstest.com/service' failed: Error in connection establishment: net::ERR_INSECURE_RESPONSE</i><p>EDIT: Disabling "disallow-doc-written-script-loads" has not effect.
Has reverse image search on right click ( Search Google image / Search Google for this image [1] ) been removed off late, from Chrome?<p>Now all I have on right click is "Copy image address".<p>That's a fairly heavily used feature. Surely, they couldn't have done away with it.<p>Didn't find any posts of substance in the product forums either.[2]<p>Some have suggested that removing Google as the default search engine rids the right click of that feature.
However my default search engine has never been not Google.<p>[1] <a href="https://www.andrewhawkes.co.uk/images/articles/search-google-for-image-right-click.jpg" rel="nofollow">https://www.andrewhawkes.co.uk/images/articles/search-google...</a><p><a href="http://1.bp.blogspot.com/-pYcECahKm44/VLAMW-n7hQI/AAAAAAAAAcI/ifBgShdSkgo/s1600/image-search.png" rel="nofollow">http://1.bp.blogspot.com/-pYcECahKm44/VLAMW-n7hQI/AAAAAAAAAc...</a><p><a href="https://2.bp.blogspot.com/-USmwx_yMwIU/Uheyv5gRzBI/AAAAAAABL7w/eXC-gSm0JT8/s640/chrome-search-by-image.png" rel="nofollow">https://2.bp.blogspot.com/-USmwx_yMwIU/Uheyv5gRzBI/AAAAAAABL...</a><p>[2]<p><a href="https://productforums.google.com/forum/#!topic/websearch/Qa_EOcArKvc;context-place=forum/websearch" rel="nofollow">https://productforums.google.com/forum/#!topic/websearch/Qa_...</a>
The portable version was also posted yesterday: <a href="https://portableapps.com/apps/internet/google_chrome_portable" rel="nofollow">https://portableapps.com/apps/internet/google_chrome_portabl...</a><p>It's handy for trying it out without installing the full app and update service on Windows. Or for running Stable, Dev, Beta on the same machine with separate profiles without needing command line switches.
Does Chrome 59 come with Ignition / Turbofan for V8 enabled ?<p>If i read this correctly, it does ...<p><a href="https://v8project.blogspot.com/2017/05/launching-ignition-and-turbofan.html" rel="nofollow">https://v8project.blogspot.com/2017/05/launching-ignition-an...</a>
Running Linux and i3wm. After updating to 59, Chrome didn't seem to automatically detect my DPI settings, so I had to manually specify the scale with<p><pre><code> --force-device-scale-factor
</code></pre>
Previously did not have to do this.
I'd like to make 'screenshots' for different pages on my server. Is there a way to do this with headless chrome without restarting chrome each time? Some sort of easy to use API for this?
I have been using request blocking in developer tools for the last month. It's really made some aspects of development easier for me. I hope Firefox follows suit and adds it.
When will they fix <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=423609?" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=423609...</a>! It's really annoying to find this one when you're getting companies to switch to Chrome from IE and end up with this in your lap instead :(