Firefox updates just completely broke the CORS, or rather the CORS broke the program. Even though running on the website (not localhost or anything) and even though it should have been sending the proper origin. Because I looked in the headers, and it was sending the origin and sending accept headers, but for some reason the options we received in the response didn't actually work in Firefox. It was sending the... wasn't like HEAD... I forget the term for it, but it was reaching out to the server asking for CORS and then it was saying "nope, can't do this." And it was doing this for every single tile that came from Cesium ion servers. This was on Firefox and I thought that was just broken with Cesium. I was about to submit a bug report, open up an issue, but I checked it out on Chrome and it worked just fine. So I looked into it a little bit more and it was something to do with the strict syntax, I think that Firefox had a little more strictness to it when it was looking for CORS information. And Chrome seemed to be fine, like it didn't really care one way or the other if this was sent first, or if this was in a certain case, as long as it received the information it was fine with that. Whereas Firefox was freaking out about either order or like literally either uppercase or lowercase. I don't know what actually did it, but about a month after that started happening Firefox had resolved the issue, but that's just one example.
Safari
Do any incompatibilities come to mind?
I've noticed that the fonts, for some reason, don't really render correctly. I'll have a font that was stock issue from one of those... it wasn't Typekit and it wasn't Google Fonts, I forget what the CON was. It was a relatively old but stable font, that we could include anywhere. I noticed that even though we had the margin right, the padding right, the kerning right, everything was just spot on, the display of it on Safari didn't look right, it was like the width of the characters, even though it was in the same style, it didn't have the correct width, or thickness rather, for the letter strokes. We kind of had to throw our hands up and say "well, this is just going to look a little bit weird on Safari." So that was an unfortunate thing.
I've noticed some other CSS-related issues. I can't think of one off-hand, but it was either something about vw or vh for the viewport width and
Made with FlippingBook - professional solution for displaying marketing and sales documents online