This update gave everything a pink tint. Resolved when turning off hardware acceleration. Hope it is fixed soon, as I would prefer to leave that on. Using GeForce 1080ti with latest drivers.
The same thing happened to me, Jonny. Thanks for the hardware acceleration tip. I'm right there with you about wanting it to be enabled since I also have a GTX 1080 Ti. I have a feeling that Chrome is planning to implement a "f.lux"-like feature and gave it the wrong switch.
The pink hue showed up for me after a reboot today of my laptop (with this latest chrome version). I did not realize Jonny was referring to turning off HW acceleration in Chrome, I was looking at my video drivers, etc. :).
Note: that's in Settings->Advanced->System->"Use hardware acceleration when available" in your chrome browser.
Yup, hardware acceleration messed up and gave chrome a weird colour when moving it to a secondary monitor. Apparently it was an issue a while back but it's back. Nvidia GTX 660 TI
I also just started dealing with this pink Chrome bug. At first it affected both of my monitors. Then I toggled (enabled then disabled) Stereoscopic 3D in the NVIDIA Control Panel (GTX 1060 by the way). Now Chrome looks normal in the primary monitor but is still pink when I move it to the secondary monitor.
Thanks all for the feedback! Regarding screen rendering as pink or yellow, please take a look at the following workaround: https://bugs.chromium.org/p/chromium/issues/detail?id=847024#c59
Please use the workaround in bug above, while we deploy a full proper fix soon. Again, thanks again for raising this!
It looks like this is a problem with default ICC profile, and it will be dealt with in next version. For now, "Force color profile" -> "sRGB" is a recommended workaround.
This decision to widen the space between bookmarks in the bar is bad. Takes a lot of space for the bookmarks, takes height, is interrupting workforce etc etc ... Please reverse this decision. Thank you.
On macOS High Sierra, I've long used an osascript to copy the URL and page title from Chrome (my main browser) and Safari. Starting with Chrome 68, it no longer works (still works fine on Safari). Here's a bit of code intended to grab the title and URL:
if (strBrowser === 'Safari') { var tab = Application(strBrowser).windows[0].currentTab; res.url = tab.url(); res.title = tab.name(); } else if (strBrowser === 'Google Chrome') { res.title = applyJsCode( function () { return document.title; }, strBrowser ); res.url = applyJsCode( function () { return document.URL; }, strBrowser ); }
Is there a change in Chrome 68 preventing this from working?
Google Chrome Stable 68.0.3440.75 removed the flag to disable Material Design in the Bookmark Manager - thus forcing Material Design of the Bookmark Manager.
The initial reason I preferred the prior Bookmark Manager is because I was able to copy bookmarks, and paste them in a different folder - which I am unable to do in the Material Design interface.
Now that the flag to disable Material Design in the Bookmark Manager has been removed, I notice that the Bookmark Manager only displays the first 60 bookmarks in a folder that contains roughly 100 bookmarks. Another folder that contains over 400 bookmarks also displays only the first 60.
Regarding the JXA osascript issue I mentioned above, evidently the JXA code I was using (borrowed from a source I've long forgotten) used a Chrome JXA API that is no longer supported. I was using it in a macOS Alfred workflow. The Alfred workflow forum hosts a Gist that maintains current AppleScript and JavaScript APIs for accessing basic browser tab info. I was able to fix my code using that Gist, which is here: https://gist.github.com/vitorgalvao/5392178#file-get_title_and_url-applescript
Follow
23 comments :
too many errors wow
This update gave everything a pink tint. Resolved when turning off hardware acceleration. Hope it is fixed soon, as I would prefer to leave that on. Using GeForce 1080ti with latest drivers.
The same thing happened to me, Jonny. Thanks for the hardware acceleration tip. I'm right there with you about wanting it to be enabled since I also have a GTX 1080 Ti. I have a feeling that Chrome is planning to implement a "f.lux"-like feature and gave it the wrong switch.
FIX THE BOOKMARK BAR EXTRA SPACING LOST LIKE 10 EXTRA BOOKMARKS
There's some "pink hue" bug which was apparently fixed: https://bugs.chromium.org/p/chromium/issues/detail?id=838126
Maybe the fix wasn't robust enough or something.
The pink hue showed up for me after a reboot today of my laptop (with this latest chrome version). I did not realize Jonny was referring to turning off HW acceleration in Chrome, I was looking at my video drivers, etc. :).
Note: that's in Settings->Advanced->System->"Use hardware acceleration when available" in your chrome browser.
Yup, hardware acceleration messed up and gave chrome a weird colour when moving it to a secondary monitor. Apparently it was an issue a while back but it's back. Nvidia GTX 660 TI
I also just started dealing with this pink Chrome bug. At first it affected both of my monitors. Then I toggled (enabled then disabled) Stereoscopic 3D in the NVIDIA Control Panel (GTX 1060 by the way). Now Chrome looks normal in the primary monitor but is still pink when I move it to the secondary monitor.
This version also give me a pink tint with my on board Intel Graphics.
Spacing between icons on bookmarks bar is way too big. Please change it back
Ok, I got "pink hue" myself and "Force color profile" -> "sRGB" in chrome://flags/ workaround (from a bug discussion above) fixed it for me.
Thanks all for the feedback! Regarding screen rendering as pink or yellow, please take a look at the following workaround: https://bugs.chromium.org/p/chromium/issues/detail?id=847024#c59
Please use the workaround in bug above, while we deploy a full proper fix soon. Again, thanks again for raising this!
Found a more relevant discussion, with feedback from developers:
https://bugs.chromium.org/p/chromium/issues/detail?id=847024
It looks like this is a problem with default ICC profile, and it will be dealt with in next version. For now, "Force color profile" -> "sRGB" is a recommended workaround.
This decision to widen the space between bookmarks in the bar is bad. Takes a lot of space for the bookmarks, takes height, is interrupting workforce etc etc ... Please reverse this decision. Thank you.
Terrible issue with print preview in recent builds (even canary). No support on this whatsoever.
On macOS High Sierra, I've long used an osascript to copy the URL and page title from Chrome (my main browser) and Safari. Starting with Chrome 68, it no longer works (still works fine on Safari). Here's a bit of code intended to grab the title and URL:
if (strBrowser === 'Safari') {
var tab = Application(strBrowser).windows[0].currentTab;
res.url = tab.url();
res.title = tab.name();
}
else if (strBrowser === 'Google Chrome') {
res.title = applyJsCode(
function () {
return document.title;
},
strBrowser
);
res.url = applyJsCode(
function () {
return document.URL;
},
strBrowser
);
}
Is there a change in Chrome 68 preventing this from working?
The space between bookmarks is tooooooooo big!
All colors are messed up. Terrible.
Spacing between icons on bookmarks bar is way too big. Please change it back
Google Chrome Stable 68.0.3440.75 removed the flag to disable Material Design in the Bookmark Manager - thus forcing Material Design of the Bookmark Manager.
The initial reason I preferred the prior Bookmark Manager is because I was able to copy bookmarks, and paste them in a different folder - which I am unable to do in the Material Design interface.
Now that the flag to disable Material Design in the Bookmark Manager has been removed, I notice that the Bookmark Manager only displays the first 60 bookmarks in a folder that contains roughly 100 bookmarks. Another folder that contains over 400 bookmarks also displays only the first 60.
Regarding the JXA osascript issue I mentioned above, evidently the JXA code I was using (borrowed from a source I've long forgotten) used a Chrome JXA API that is no longer supported. I was using it in a macOS Alfred workflow. The Alfred workflow forum hosts a Gist that maintains current AppleScript and JavaScript APIs for accessing basic browser tab info. I was able to fix my code using that Gist, which is here: https://gist.github.com/vitorgalvao/5392178#file-get_title_and_url-applescript
Post a Comment