Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Lots of mud at the base of the wall. I think it's a good sign. It'll be a bad sign if this list does't grow.

    I do bemoan the loss of the <?xml-stylesheet?> processing instruction and the JavaScript XSLTProcessor API.

  • Thank you so much for this amazing resource. One of my projects is a hyper-compatible framework that builds websites that span the compatibility spectrum from Netscape 3.x to today's browsers, and this is very helpful.
  • Ohh, conditional comments. We had so many IE holdouts on our site, I think only around 2021 I removed the last IE specific fallbacks, and I think some conditional comments were a thing until 2020.

    I’m not sure when I removed a bunch of `msapplication-` fields, but probably after 2021 ;)

    I guess I can remove `apple-touch-` and `application-name` stuff next…

  • Server side image maps are a fun one also: https://rickcarlino.com/2021/what-were-server-side-image-map...
  • I'd only add the Safari Pinned Tabs `meta` tag (https://developer.apple.com/library/archive/documentation/Ap...), which had you define a simple black and white SVG. This image would get used when a user pinned your tab in Safari, in color when active and black when inactive.
  • Forever burnt into my mind is PNG alpha work-arounds in IE:

        filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='image.png');
  • Reminds me of how awkward HTML doctypes used to be. Nowadays it's very simple, but in the past? You had to refer to the URL of the doctype declaration on every page

    > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    This plus the X-UA-Compatible stuff mentioned in the article meant that for many people, the first few lines of code on a web page were something they probably copied from a tutorial or reference document every time, at least if they didn't have a CMS handy.

    by CM30
  • I was also thinking about charsets, BOM (byte order marks) and other shenanigans that had to be correct in the top of the file for things to display as expected. At least it was a struggle for 13 year old me why sometimes æøå showed up completely broken, and sometimes not. Today it feels like a solved issue, all files are UTF-8 all the way and it just works.

    https://www.w3.org/International/questions/qa-byte-order-mar...

Explore Birbla archives