|
|
|
|
|
by tomjen3
2178 days ago
|
|
There is absolutely no reason great typography should come at the expense of privacy, unless you are unable to upload custom fonts or have something against CSS. You also don't need JS to support it, although you may have to give up on the idea that your site has to look the same in all browsers, because not all browsers can do things like automatic hyphenation. And frankly I am happy that I don't have to read source code in Courier just because it is the only available monospace font. |
|
However CSS is not benign. There are features that bad actors regularly exploit. For example, setting the opacity of an evil button to 0, and positioning it above an innocent button.
Also, CSS, as currently designed, is a barrier to reuse. The model I like is one where users are at liberty to display web content however they (the user, not the website) prefer. Since CSS is basically reusable only in theory, it inhibits that.
It's true that, as a web developer, you can provide Courier. As a user, it's not, by browser default, your choice whether you get Courier. If the server decides a user should see Comic Sans, that's what the client will use, no?