2 ms·
The "default UA stylesheet" has always been a weird compromise: slightly different in every browser, yet generally all trying to render pages from 1994 mostly t
by derefr 11y ago
The "default UA stylesheet" has always been a weird compromise: slightly different in every browser, yet generally all trying to render pages from 1994 mostly the same way they looked in 1994.
Personally, I think it would make way more sense if you could specify something like a "base style" meta-tag, with values like:
• "browser" (the default): do what we're doing now, where every browser styles things a bit differently, and a default Chrome <button> looks nothing like a default Safari <button>, and so forth.
• "legacy": make the page look exactly like it would when displayed in NCSA Mosaic in 1994. (This style could be inferred from the headers and auto-applied if the server sends a very old modification date or the page uses an older version of HTML.)
• "reset": a WHATWG-standardized set of CSS reset values
• "native": make tags resemble native OS controls—<p> should look like label-control text, <h1> should look like a native header style, <button> like an OS button (instead of a browser button), etc.
The interesting part of this is that this would allow the "browser" style to diverge further from the "legacy" and "native" styles than it already has, since any web designer could just ask the browser to drop all its customizations in a quick-and-convenient way.