Lazy loading while I scroll makes Chrome cry.
We've discovered quite a bit while building this site, and better scroll performance is in the works. Stay tuned.
Google Fonts Redesigned
191–200 of 268 posts
Re: Google Fonts Redesigned
#192Earlier quoted context omitted.
I regularly have to email SaaS companies and tell them the service I just signed up doesn't work correctly in Firefox.
Yes. The latest version of Firefox has cache issues. The same in Chrome was working perfectly after a single refresh. Sad. I love Firefox.
Chrome does not obey cache headers on refresh, I think they assume something is wrong if you are hitting the refresh button and fetch all files from the server.
I can't really blame firefox for obeying the headers that the server sent them.
Re: Google Fonts Redesigned
#193Earlier quoted context omitted.
works on Firefox and Safari as well as Chrome. There's a difference between the old-school Microsoft efforts to break competitors and current efforts to support a (popular) subset of browsers.
But the point is that with current standards, things that work on Firefox, Safari, and Chrome just work on Edge. It's extra effort on Google's part to throw up "not supported" banners and pretend like Edge is the worst scum and villainy on the planet. It's a terrible marketing effort disguised as "building a better web" and it's doing a disservice to the open web, modern standards, and basic common sense "do the righ…
How is not devoting time to supporting a proprietary browser doing a disservice to the open web?
Re: Google Fonts Redesigned
#194Earlier quoted context omitted.
Yes. The latest version of Firefox has cache issues. The same in Chrome was working perfectly after a single refresh. Sad. I love Firefox.
Chrome does not obey cache headers on refresh, I think they assume something is wrong if you are hitting the refresh button and fetch all files from the server. I can't really blame firefox for obeying the headers that the server sent them.
This problem hit me very hard, chrome ignores most headers if a server sends a 304 response for a resource.
For a site I was working on, we issued a change to our CSP headers only to attempt to fix a CSP issue that made it to production, and chrome would not accept the new CSP changes since the HTML body and scripts were unchanged.
Had to include the hash of our headers as an HTML comment to allow this dynamic change to be picked up by chrome.
Re: Google Fonts Redesigned
#195Re: Google Fonts Redesigned
#196Earlier quoted context omitted.
Chromium of all browsers gets pestered all the time by Google services. It's... odd.
Google doesn't want you to use Chromium. Use Chrome instead, it's exactly like Chromium but with all the Google bloatware installed!
>with all the Google bloatware installed!
Oh yeah? Like what?
Sorry, does anyone downvoting want to actually explain to me what "bloatware" is "bundled into" Chrome? Or just more errant bullshit that's tacitly accepted because it's anti-Google rhetoric fired from the hip without substance?
Those audio/video codecs... so much bloat! https://chromium.googlesource.com/chromium/src/+/master/docs...
Or maybe you're upset about the "colorful logo" bloat?
Re: Google Fonts Redesigned
#197This is nice and all (apart from an astonishing—even for Google—degree of browser compatibility regression), but what I really want is for the actual fonts to be updated. Crimson Text, for example, is an outdated version of the font, which it breaks a little further too. Upstream ( https://github.com/skosch/Crimson ) has seen substantial improvements, but Google has never updated it, ignoring the author’s pleas.
Hear, hear :)
Same for many others, e.g. Montserrat or many of Vernon Adam's designs. That being said, I find the redesign wonderful and long overdue. Maybe now they'll find the time to update their collection.
Re: Google Fonts Redesigned
#198I tried.
Re: Google Fonts Redesigned
#199Earlier quoted context omitted.
But the point is that with current standards, things that work on Firefox, Safari, and Chrome just work on Edge. It's extra effort on Google's part to throw up "not supported" banners and pretend like Edge is the worst scum and villainy on the planet. It's a terrible marketing effort disguised as "building a better web" and it's doing a disservice to the open web, modern standards, and basic common sense "do the righ…
How is not devoting time to supporting a proprietary browser doing a disservice to the open web?
Sounds like parent is saying Google is spending time to deliberately block/not support Edge.