Chrome 64 is shit
-
@boomzilla said in Borked Chrome 64:
I disabled it, but chrome is still showing errors. Oh, and hangouts doesn't want to make calls any more because it doesn't have access to my microphone. "See the popup to correct." The popup is blank.
Motherfuckers:
Bug report:
Hmm...apparently you can't make a call from gmail. Fucking fuckers.
-
@boomzilla Nope, not from the hangouts page either.
-
Is bugs.chromium.org running on a mic in Chrome 64? It isn't loading for me.
Fake edit: It loaded (without any css or anything from the look of it) while I was writing.
-
All the static resources are throwing up 500's, and are not OK.
-
@hungrier Hilarious. It loads fine in FF.
-
@boomzilla I'm on Version 63.0.3239.132
I installed Version 64.0.3282.119 about an hour ago.
I think I'll wait before I restart it
-
Good. Hangouts always changes the microphone volume at the system level and there's no way to stop that from happening as far as I know, neither in Chrome nor Windows.
-
@lb_ Prior to its current bullshit, on Linux it can't even figure out how to use the microphone. Even though all the settings were correct, it wouldn't use my headset at all. Neither the microphone nor the speakers. I've ranted about this before. I have to use the system mixer to redirect the sound. Every damn time.
What's really infuriating is that it also sets everything from chrome to go to the headset. Unless you have another call. Then hangouts will still use the system speakers (and will have forgotten about the mic, too) even though the rest of chrome is using the headset.
Fuckers.
-
Oh goodie, just as I was about to start the work on making a built-in SIP phone for our webapp, AND recommend Chrome to users because that's the only browser where I'm sure that choosing the audio device works properly (so you can have it ring on your speakers, for example).
Puts in a blocker for the feature:
Chrome is fucked
-
A feature that I wish Chrome would figure out is populating the search box with highlighted text.
-
Every major update of chrome does something different with the way it renders text. The fonts all look slightly different. I don't care enough to check to see what they've changed (like, just picking different defaults or what?) but one thing I noticed this time is the way hyperlinks are rendered:
Glyphs that go below the baseline now break up the link, which tends to make it look like multiple links, especially commas.
-
@boomzilla blame this bit of stupidity:
-
@japonicus Ah, yep, that'd be it.
-
@japonicus In Chrome 63 I see
and looking at that in devtools I can addtext-decoration-skip
(which auto-completes) to the element style, and theink
option does this:
Edit: Oh.
Chrome
57 — 64 Only supports the deprecated ink value.
-
Huzzah! Hangouts released an update yesterday that fixes the latest mic problem.
-
@boomzilla said in Chrome 64 is shit:
Huzzah! Hangouts released an update yesterday that fixes the latest mic problem.
Links are stillfucked tho. Damn I hate the default..
-
@japonicus said in Chrome 64 is shit:
@boomzilla blame this bit of stupidity:
Yeah, I added a user CSS to get rid of that now that the change is spreading throughout Chromium browsers without them adding a setting to turn it off. >:(
-
This looks like ass :|
-
-
@swayde said in Chrome 64 is shit:
@boomzilla said in Chrome 64 is shit:
Huzzah! Hangouts released an update yesterday that fixes the latest mic problem.
Links are stillfucked tho. Damn I hate the default..
Stillfuck - the best kind of fuck.
How can I fuck you, if you won’t hold still?!
Oh, so that’s why @Lorne-Kates uses a shovel.
-
I guess I'm the only person who likes the new look of the underlines.
-
@hungrier It looks pretty but it's also misleading because it makes a single link look like multiple links.
-