ITT we wait for CHROME 102 TO DROP later today!
ITT we wait for CHROME 102 TO DROP later today!
Other urls found in this thread:
chromestatus.com
chromereleases.googleblog.com
twitter.com
What's in 102 this go around?
BOTNET 102
Hope they finally ship the fix for selecting a year using the HTML5 datepicker scroll.
I can't believe they managed to break something so fundamental and not figure out for weeks, even false flagging a report.
Yeah no thanks
It's out now. At least on Windows. Thread is dead now.
Good news, the linux version we're all waiting for in here should show up shortly!
I T ' S U P
Awesome! Sorry ITODDLERS!
IT'S UP ARCHSISTERS
already on it
chromereleases.googleblog.com
UPDATE YOU'RE BOTNET NOW
>32 security fixes
jfc
Is it worth the time getting video encode/decode enabled? Will I notice a difference? Stability issues?
Ignore gpu blocklist wasn't enough on its own. Its amd.
Why are PWAs such a big deal?
think electron apps but you don't have to download the whole browser every time so yes theyre pretty convenient
Oh, that is kinda neat. Electron is a cancer.
>ITT
Why does Chrome look better than Firefox? Something about the font doesn't seem as bold and I like that.
It doesn't take long to fix, but for some reason Google really doesn't want to enable VAAPI by default. Works fine on my AMD machine except for no AV1 decoding, even though my GPU is capable of it.
I'm sure this varies by distro but this is how to enable it on Arch. Put this in /etc/chromium-flags.conf:
--enable-accelerated-video-decode --enable-accelerated-video-encode --enable-features=VaapiVideoDecoder,VaapiVideoEncoder --disable-features=UseChromeOSDirectVideoDecoder
Chrome introduced their own font rendering engine close to 10 years ago while Firefox is dependent on GTK3, the difference is immediately noticable, your websites will always look like trash on Firefox unless you explicitly set the font size for every last element because the default stylesheet is fucking ASS