Chrome 59 stable released

136 点作者 bd82将近 8 年前

24 条评论

foob将近 8 年前

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.[1] - <a href="https://intoli.com/blog/running-selenium-with-headless-chrome/" rel="nofollow">https://intoli.com/blog/running-selenium-with-headless-chrom...</a>

评论 #14497801 未加载

评论 #14498041 未加载

评论 #14497663 未加载

评论 #14496828 未加载

评论 #14498341 未加载

评论 #14497115 未加载

评论 #14497011 未加载

madjam002将近 8 年前

Has there been any research on whether Material Design has superior UX for desktop use?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.

评论 #14496928 未加载

评论 #14496823 未加载

评论 #14496830 未加载

评论 #14499329 未加载

评论 #14498187 未加载

评论 #14496732 未加载

评论 #14496901 未加载

aargh_aargh将近 8 年前

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].[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>[2] <a href="https://textslashplain.com/2017/05/02/inspecting-certificates-in-chrome/" rel="nofollow">https://textslashplain.com/2017/05/02/inspecting-certificate...</a>

评论 #14497012 未加载

评论 #14496826 未加载

评论 #14500327 未加载

评论 #14498688 未加载

Vinnl将近 8 年前

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>

评论 #14498219 未加载

littlestymaar将近 8 年前

With the new optimizing compiler (Turbofan) landing, JavaScript `Exception` are now usable without significant performance penalty: great news !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 !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>

geekamongus将近 8 年前

Can someone explain or point me to a good source of info on why headless Chrome is a big deal? (Not being snarky; I really want to know).

评论 #14496938 未加载

评论 #14497813 未加载

评论 #14497310 未加载

评论 #14496915 未加载

评论 #14497045 未加载

评论 #14496964 未加载

fosco将近 8 年前

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.[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>

评论 #14506306 未加载

评论 #14500903 未加载

solidr53将近 8 年前

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>

评论 #14498098 未加载

gtirloni将近 8 年前

Anyone seeing a failure in <a href="https://websocketstest.com" rel="nofollow">https://websocketstest.com</a> (Chrome 59.0.3071.86) ?<a href="https://websocketstest.com/result/7629067" rel="nofollow">https://websocketstest.com/result/7629067</a>It works fine on Firefox 53.0.3 and 55.0a1 (Nightly).Console says: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.WebSocket connection to 'wss://wss.websocketstest.com/service' failed: Error in connection establishment: net::ERR_INSECURE_RESPONSEEDIT: Disabling "disallow-doc-written-script-loads" has not effect.

wozniacki将近 8 年前

Has reverse image search on right click ( Search Google image / Search Google for this image [1] ) been removed off late, from Chrome?Now all I have on right click is "Copy image address".That's a fairly heavily used feature. Surely, they couldn't have done away with it.Didn't find any posts of substance in the product forums either.[2]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.[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><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><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>[2]<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>

评论 #14497799 未加载

评论 #14497519 未加载

评论 #14497293 未加载

JohnTHaller将近 8 年前

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>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.

wooptoo将近 8 年前

This version of Chrome has support for running headless (without the need for a graphical environment at all). Awesome for automation and testing.

clumsysmurf将近 8 年前

Does Chrome 59 come with Ignition / Turbofan for V8 enabled ?If i read this correctly, it does ...<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>

kondbg将近 8 年前

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<pre><code> --force-device-scale-factor </code></pre> Previously did not have to do this.

mad182将近 8 年前

Nice! APNG is finally supported.

评论 #14496781 未加载

bsandert将近 8 年前

One I've been looking forward to for a while: native notifications on OSX!

samat将近 8 年前

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?

评论 #14499175 未加载

评论 #14498617 未加载

nickster将近 8 年前

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.

arnon将近 8 年前

This finally kills CentOS 6 support...

borplk将近 8 年前

I have been using the headless mode for a while (on unstable). It's been awesome!

taf2将近 8 年前

Headless chrome is very exciting

amelius将近 8 年前

What is the difference between Chrome and Chromium these days?

评论 #14498815 未加载

jordache将近 8 年前

yea headless for CI!

dsincl12将近 8 年前

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 :(