damn remi really starting the site off strong with you just being angry :^^)))))))))))
hi! it’s remi here. by the time this website is up on the internet, it should be 2022 or so. internet explorer 6 is old enough to drink by now! and today, browsers are mostly compatible with each other, unlike the ~ good ol days ~, where all the browsers had diffrent capabilities for no reason. probably even worse before ie6, but like i was alive by then :^)
….. so… all the browsers are mostly compatible, right.
chrome, firefox, safari, and the 500 chrome reskins (kinza my beloved), more or less do the same things. Right ??????????
W r o n g
over the years of making my stupid websites, i’ve encountered Way Too Many silly things browsers do diffrently. the good news, is that they’re not too much of a bother, unless you’re the type like me, that cares wayyyyy toooo muchhhh about how things look.
for example, let’s name some weird things firefox does. (dont worry chrome and safari users, you’re not safe either)
- customizing scrollbars here is a mess. firefox supports the (incredibly new) css scrollbars properties, that notably… no other browser supports. all other browsers (.. the webkit based ones) have been supporting the aptly named ::-webkit-scrollbar properties, which it’d make sense firefox wouldent have… but you’d think they’d atleast hack it in temporarily to make any website with a custom scrollbar not look UGGO
- backdrop-filter … is that supported yet? i remember finding this property like.. two years ago, being overjoyed, and then swiftly realizing the only browser that supported it was safari. a year passed, and chrome started supporting it, so i put it in several of my projects. but…. to this day, firefox doesnt support it. Why ?????? It’s Been Around For Years Now Get With The Times
- image-rendering .. is something im gonna come back to, but very fun: if you want pixellated image rendering (i.e “small 16px images dont become a blurry mess on phones or hidpi screens or when upscaled whatsoever”), you can use the simple property image-rendering: pixellated. Nice Huh??? except, for some unknown reason, on firefox, it’s image-rendering: crisp-edges. and then, even worse, browsers seem to not render all images like this. firefox, for instance, seems to refuse to render border-images and background-images properly. Why ???? ? ?? ??? ? ? ?
…okay, that’s enough bashing firefox for now. mainly because i dont use firefox, and i dont know enough of it’s quirks :^) what about chrome, then?
- MEI is the worst thing ever. like four years ago, chrome just deleted autoplay from their browser. this is kinda fair - nobody wants go to to a news site and get videos and audio blaring at you… but then they never added a way to properly get it in here anyway. there isnt a way to like, remember that users liked your audio playing, other than clicking the lil lock button, and manually enabling autoplay… but uhhh, how are users gonna learn to do that? “hey before you enter my site, please click the lock and enable autoplay! thanks!” No Nobody Will Do That
- image-rendering in chrome…. doesnt support crisp-edges?!??!?!! thankfully, it seems pixellated does the same thing. But What If You Want To Support Multiple Browsers yeah uhhh you gotta figure out how to apply to css to only firefox/chrome Haha Good Luck :))))… atleast this one renders border-images correctly. and backgrounds too. phew.
- border images dont work in chrome for no reason unless you throw in a transparent border which i just learned while writing this!!!!!! WhYY YYYYYY now i have to go update the css on another site THANKS
okay then, what about safari?
- so if you add a border to a border-image, the border-image breaks in safari.. what…….. . .. GOD
- okay this isnt even a rant anymore this is a threat to whoever develops browsers i am going to come down to your house and stab you (just kidding, but mainly for legal reasons)
- does this work in firefox anymore?
- im… not gonna find out…
- oh yeah, image-rendering works properly here. both crisp-edges and pixellated do the same thing! nice, right? (BACKGROUND-IMAGES ARENT AFFECTED BY IMAGE-RENDERING)
- safari supports like no audio formats. LAUGH
- honestly i wanted to write more things here but im just sick and tired of all of this, i just wanna go back to writing css and having fun so im gonna go do that now!!!
…so yeah, browser support is still horrible.
it’s a quadrillion times better than it was in like… 1997, when netscape and internet explorer actively competed and had entirely diffrent featuresets, though…
and atleast we dont have to deal with whatever the heck an active-x is anymore…
(scoffs at chrome native client, which is thankfully dead by now)