News for hackers. Stuff that matters.
Re:Google Fonts Redesigned by mrweasel on Tuesday June 14, 2016 @02:23PM (#11904108)
More and more sites are only tested in Chrome. It's not just Edge that no one cares about, Firefox is becoming a second class browser as well.

Often it's pretty obvious that the authors didn't even try Firefox, because the JavaScript isn't even loading properly.

Re:Google Fonts Redesigned by hanley on Tuesday June 14, 2016 @02:34PM (#11904209)
I regularly have to email SaaS companies and tell them the service I just signed up doesn't work correctly in Firefox.
Re:Google Fonts Redesigned by gizzlon on Tuesday June 14, 2016 @05:59PM (#11905671)
I use 85% Firefox and I only see issues on experimental stuff. I'm curious, where do you have these issues?
Re:Google Fonts Redesigned by LoSboccacc on Tuesday June 14, 2016 @08:19PM (#11906413)
Firefox is a pain to support. Its box model is slightly different than other browser, like shadows take up space and an outline is rendered around the shadow instead of aroubd the border. There are other minor things especially on the drag&drop events (in same window, not from outside) but I can't recall the specific.
Re:Google Fonts Redesigned by avikalpa on Tuesday June 14, 2016 @06:57PM (#11906030)
Yes. The latest version of Firefox has cache issues. The same in Chrome was working perfectly after a single refresh. Sad. I love Firefox.
Re:Google Fonts Redesigned by maloney on Tuesday June 14, 2016 @10:23PM (#11906831)
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 by daguava on Tuesday June 14, 2016 @11:08PM (#11906967)
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.