This update completely broke my ability to work on developing my Javascript app. Check out at this page: http://www.ccpnc.ac.uk/magresview/magresview/magres_view.html, for example at times the developer console returns a ReferenceError when I ask for variables like "Jmol" which is fundamental to the code and is surely defined if the page works at all. Then it goes back to working regularly. Then it slows down when I use it from a local web server, or it returns "null" when I use jQuery to fetch a reference to an element. Any clue as to WTH is going on?
This update causes real problems when using a proxy inside a network, and your clients are set to "Automatically Detect Settings". Everything worked before!
Google Chrome has already been a great browser but every day that passes the version numbers only increase the browser does not gain any new function or feature designate and still the same thing, but more cumbersome, slow and locked. This final version of Google Chrome 51 is just awful, slow scroll pages locking and high memory consumption'm seriously considering leaving Google Chrome. I use this nevagador since version 0 and I confess that I have seen little change so far.
I like the new look, and everything has been working for me, but there's one thing that irks me: The tabs are too tall. Everything else has gotten smaller, but the tabs have gotten larger. Please make them shorter, they really do feel like wasted space.
In this new version, the link hover status bar now shows all text in grey color, on a light grey background. Impossible to read, please revert this to show black text. As it is right now, the text completely disappears with some screen viewing angles.
This update causes real problems when using a proxy inside a network, and your clients are set to "Automatically Detect Settings". Everything worked before! WE have the same problem, CHROME receive this error message : "The page you requested has been blocked by a firewall policy restriction". I resolved using chrome 50.x instead 51.x. IE11 and Mozilla aren't affect from this error message.
I am having problems with a transition for background-size (from 100% to 110% on hover). In 50 version was working ok, but now it completely ignores the transition and looks/feels plain awful.
Thank you, thank you, THANK YOU! For the first time EVER, my dark GTK+ 2.x theme looks (almost) totally fine with Chromium!!! Enabling overlay scrollbars also helps in this regard.
And the inverted-scroll regression introduced with Chromium 49, which has driven me mad while scrolling the wheel of my left-handed trackball for the past two months, is finally gone! Phew… :-D
There is serious issue in chrome ,when it tries to match the DOM elements .i.e webkitMatchesSelector match selector is not working as expected. Please let us know if any update on this.
I've installed windows 8.1 on my laptop after buying license from ODosta Store, I want to activate it to get free upgrade from windows 7 professional to windows 10 home. I'm now confused, How to activate and upgrade to windows 10. Please mention within details.
In Chrome 50 and 51 we are seeing issues with our application using web workers. We use 2 web workers, one for speech recognition and one for audio encoding, both are emscripten transpilations. The issue is that the web worker processing is significantly slower - at least a factor of 2, although we are still investigating the details. We have already had to push out 2 fixes to compensate for issues caused by the slower processing. I can't find anything in a search, but not sure what to search for. What recent changes could have caused this? Any changes to workers, asm, typed arrays?
Follow
30 comments :
Where is Material Design ? :^(
Give me back me the old tabs! I find the new angular tabs disgusting!
I'd have to agree.
The other changes look quite nice so far, but the tabs feel like some space is wasted, and don't go well with most favicons.
New features are quit nice...:)
Get more extensions - button under extension dont work is empty link page.
This update completely broke my ability to work on developing my Javascript app. Check out at this page: http://www.ccpnc.ac.uk/magresview/magresview/magres_view.html, for example at times the developer console returns a ReferenceError when I ask for variables like "Jmol" which is fundamental to the code and is surely defined if the page works at all. Then it goes back to working regularly. Then it slows down when I use it from a local web server, or it returns "null" when I use jQuery to fetch a reference to an element. Any clue as to WTH is going on?
This update causes real problems when using a proxy inside a network, and your clients are set to "Automatically Detect Settings". Everything worked before!
Google Chrome has already been a great browser but every day that passes the version numbers only increase the browser does not gain any new function or feature designate and still the same thing, but more cumbersome, slow and locked. This final version of Google Chrome 51 is just awful, slow scroll pages locking and high memory consumption'm seriously considering leaving Google Chrome. I use this nevagador since version 0 and I confess that I have seen little change so far.
This release is causing havoc with our production application. Every user that upgrades from 50 to 51 is having serious problems.
It may be related to Simone's issues above. We just realized that our problems are being caused by this release of Chrome.
I'm sure we aren't the only SaaS company having a heck of a morning today.
We are having to tell our user to shift to a different browser until this is resolved.
BTW - Will post more details once we pinpoint what exactly is breaking with this new release. Our development team is working on it right now.
Does anyone know of a reason why Chrome PDF Viewer is set to 'Always allowed to run' and the checkbox is grayed out?
Hmmm, no new material design for me. has it been postponed?
@Simone and Blackat,
Thanks for reporting. I've opened a ticket up on our bug tracker to investigate more.
https://bugs.chromium.org/p/chromium/issues/detail?id=615209
Can you star it so we can keep in touch?
Also I have some questions on the ticket for ya'll. :) Thanks
I saw that that there is material design on Linux, why not in Windows?
I like the new look, and everything has been working for me, but there's one thing that irks me: The tabs are too tall. Everything else has gotten smaller, but the tabs have gotten larger. Please make them shorter, they really do feel like wasted space.
In this new version, the link hover status bar now shows all text in grey color, on a light grey background. Impossible to read, please revert this to show black text. As it is right now, the text completely disappears with some screen viewing angles.
Running Chrome 51.0.2704.63 on Ubuntu 14.04.3.
This update causes real problems when using a proxy inside a network, and your clients are set to "Automatically Detect Settings". Everything worked before!
WE have the same problem, CHROME receive this error message : "The page you requested has been blocked by a firewall policy restriction". I resolved using chrome 50.x instead 51.x. IE11 and Mozilla aren't affect from this error message.
The problem with proxy (PAC file) usage is being tracked with CR 615804
https://bugs.chromium.org/p/chromium/issues/detail?id=615084
Immediate workarounds are described here
https://productforums.google.com/forum/#!topic/chrome/biBhGTDpdxM
The team is working to incorporate the fix for the M51 Stable RC release Tuesday afternoon 5/31 (CR 615804 Cmt#18)
A Material Design discussion is unfolding in this Help Forum post:
https://productforums.google.com/forum/#!topic/chrome/kM87gXdklhI .
It can be, for the moment, disabled with the flag top-chrome-md=non-material.
Caveats apply, see the forum post.
AFAIK Material Design only became the desktop default for Linux.
The windows default is still non-material.
I like the new tabs and design. It looks clean and cool :)
I am having problems with a transition for background-size (from 100% to 110% on hover). In 50 version was working ok, but now it completely ignores the transition and looks/feels plain awful.
Thank you, thank you, THANK YOU! For the first time EVER, my dark GTK+ 2.x theme looks (almost) totally fine with Chromium!!! Enabling overlay scrollbars also helps in this regard.
And the inverted-scroll regression introduced with Chromium 49, which has driven me mad while scrolling the wheel of my left-handed trackball for the past two months, is finally gone! Phew… :-D
Great release, guys.
Click here
Click here
Click here
sexual objects
electronic market
watch movies Sex
Six Children
Free Sex
Gay Sex
Chat Style
live chat
Sex Girls
Click here Sex Arabic Girls
pictures Sex
see a show Sex
rape of Sex
motherland Sex Show
Sex Show
Sex representatives
Celebrities
watch animals Sex
watch Sex humans
Sex in the market
Click here now
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
Click here
its may 30 and my chromebooks (i have three) still have not updated to the new release.... whats the hold up
Looks OK apart from the new tab shape/size, which I'm not sold on ... maybe I will come around to it.
Hi,
There is serious issue in chrome ,when it tries to match the DOM elements .i.e webkitMatchesSelector match selector is not working as expected. Please let us know if any update on this.
For some reason, on my PCs - 2 of them - zoom settings for websites were lost when going from Chrome 50 to 51. Does anyone test these things?
Using Windows 10 Pro 64-bit.
I've installed windows 8.1 on my laptop after buying license from ODosta Store, I want to activate it to get free upgrade from windows 7 professional to windows 10 home.
I'm now confused, How to activate and upgrade to windows 10.
Please mention within details.
@Umerkhan9 - Your question has nothing to do with Chrome, and also it appears to advertise some website. Neither is allowed here.
Please no spam and no non-Google Chrome questions here.
In Chrome 50 and 51 we are seeing issues with our application using web workers. We use 2 web workers, one for speech recognition and one for audio encoding, both are emscripten transpilations. The issue is that the web worker processing is significantly slower - at least a factor of 2, although we are still investigating the details. We have already had to push out 2 fixes to compensate for issues caused by the slower processing. I can't find anything in a search, but not sure what to search for. What recent changes could have caused this? Any changes to workers, asm, typed arrays?
Post a Comment