Applying the CSS "@supports (display: grid) { .wrapper > tbody, .wrapper > tbody > tr { display: contents; } }" with wild abandon in GeoCities HTML table-based layout templates optimized for Internet Explorer 3 and/or Netscape Navigator 3 to make them pleasant on sub-VGA pocket screens while still remaining optimized for those early browsers and every desktop browser since: from IE3 to Edge 125, and from NN3 to Firefox 128.
I'm reading that the CSS "display: contents;" on TR and (implicit) TBODY elements wrecks accessibility of tables as tabular data, rendering their TH and TD cells as ordinary content with no tabular relationship instead, but since these are tables "misapplied" for layout only and never meant to be tabular data themselves (one of the only ways to control page layout in pre-CSS and CSS1 days), that seems like a perk in this specific case.
Mozilla Developer Network, "Realizing common layouts using grids": https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Grid_layout/Common_grid_layouts
Reading guides like that while lamenting the shortcomings of vintage Web browsing, even via RetroZilla in a Windows 98SE VM, does strange things to a girl, y'know?
Related: CSS grids are 3 years older than Chromium-based Microsoft Edge and only 2 years younger than EdgeHTML (Trident)-based Microsoft Edge Legacy.
I may be going back *way* too far. My template is looking nice even in IE2, but since IE2 predates HTTP/1.1 by about 5 years, it can't connect to any website but the default on a virtual host Web server.
I am learning so much modern CSS for features that most websites rely on slower JS to achieve, and I'm learning how to shield modern CSS's side effects from older and early popular browsers.
This is so much more labor than I expected, using every age of CSS to make CSS-free HTML layout table pages look better and responsive, but it's a labor of love. And joy. And bliss.
IE4 is my main target and Firefox current is my ultimate target, but Dillo, Links, RetroZilla, and SeaMonkey (last for Win98 and current, both) are proving at least as useful as Firefox's Responsive Design Mode in testing and debugging.
I set out with the goal of making my vintage HTML page template look fantastic in Netscape Navigator and only passable in Internet Explorer. Instead, it's looking only passable in Netscape Navigator and fantastic in Internet Explorer. I don't know how to feel about this.