jimmydoreisaleftyHere we go again
whileloopThis is your hourly reminder that Brave is still Chromium and still contributes to Google’s influence over internet standards.
amnesiacrobatIirc Firefox and I think Safari are the only major non-chromium browsers. It makes me so sad because I remember Google’s “don’t be evil” days… man they left that behind
Apathy TreeSafari already has attestation, has for a while, so while its at least a different browser, it’s still part of the problem.
SnowdenHeroOfOurTimeInteresting. I didn’t know that. Safari is a piece of shit for other reasons too
ReygleExample reason why Safari is shit: It’s Safari
Yeah. They selectively adopt web standards years later than the others and the mobile and iPad versions in some ways behave completely differently from desktop (and each other). If safari just acted like the other browsers, frontend web dev would be MUCH easier.
SpeziSuchtelDepends on which standards, for some css functions like backdrop-filters and mix-blend-modes it was years ahead of Firefox, where some of those had to be activated through about:config. I‘m glad Firefox catchend up in the past few years though. Also WebKit accelerated HTML5 adoption a lot.
I feel like you’re referring to Firefox literally 12 years ago or more. I’m talking about today. Literally any brand new standard is not supported for 1-2 years minimum. I run into problems with safari on a near daily basis. I rarely have a weird issue in Firefox. 99% of the time chrome and Firefox behave the same. The vast majority of the time that one browser has an issue others don’t, it’s safari. It’s weird to me to get pushback on this …
Backdrop filters were introduced with Firefox 103, which was released just 12 months ago. And it was a major pain for me that Firefox was the only browser I had to do workarounds for this function when Safari supported it since 2015 and chrome did since 2019.