fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-23 12:52:10 +00:00
Code Issues Projects Releases Wiki Activity

New note: supporting alt browser engines

Browse source
This commit is contained in:
Rohan Kumar 2022-11-06 21:13:57 -07:00
parent 0daf754eaf
commit 442c90bb14
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
content/notes/supporting-alternative-browser-engines.md Normal file
View file

@ -0,0 +1,17 @@
---
title: "Supporting alternative browser engines"
date: 2022-11-06T21:13:47-08:00
replyURI: "https://fosstodon.org/@caughtquick/109300199609421021"
replyTitle: "It’s not my job to make sure my website works on a browser from 2008 that’s missing half of [w3c] standards"
replyType: "SocialMediaPosting"
replyAuthor: "Abhijit Sipahimalani"
replyAuthorURI: "https://fosstodon.org/@caughtquick"
---
Progressive enhancement is a wonderful thing. I try to make sites usable in browsers of that era (with a TLS terminator) despite using several HTML 5 and bleeding-edge CSS features. Every feature possible should be progressive.
[Here's the compatibility statement for seirdy.one]({{<relref "/meta/site-design.md#compatibility-statement">}})
I'm not asking anything too radical: when you want to use a feature, just try to make support optional. If there are two ways to do something, have a bias towards the older way. Without trying, you'll get good support for these browsers and for extensions that modify pages.
As a baseline, I recommend starting with the [subset of the HTML Living Standard that appears in the abandoned HTML 5.1 standard]({{<relref "/posts/website-best-practices.md#how-to-support-old-browsers">}}). CSS should be optional. This tends to progressively degrade fairly well.