3 ms·
Nice idea. However, is doing this client-side with javascript really the best approach? Surely a server-side solution to fix the html before sent to the client
by upthedale 15y ago
Nice idea. However, is doing this client-side with javascript really the best approach? Surely a server-side solution to fix the html before sent to the client would be better.
I get that its very usable from the designer's point of view. They can just drop a little script like this into their document and forget about it, but after the umpteenth little script like this, won't performance become an issue?
My other issue is that until we get decent rendering across the board, anything with @font-face such as this is just infuriating to read. Whilst my browser of choice (Opera) is one of the more niche ones that people might not care about, a recent thread here on HN mentioned that Chrome on Windows also suffers from the chipped away look with @font-face - meaning a lot more people are exposed to this annoyance.
- sp332 15y agoHowever, is doing this client-side with javascript really the best approach? I think it's appropriate, since it's a rendering issue. In the future, the JS can check whether the browser renders things properly, and just skip the whole process.