3 ms·
I've always felt that libraries like Slice excessively couple the application's source code with its design Ideally, the HTML should have nothing to do with th
by weavejester 16y ago
I've always felt that libraries like Slice excessively couple the application's source code with its design
Ideally, the HTML should have nothing to do with the site's design. The HTML should semantically describe the content, not govern how it is displayed.
- regularfry 16y ago> Ideally and therein lies the rub. As long as we have to care about browser bugs and inconsistencies, there are going to be limits to this.
- weavejester 16y agoBut not many limits. Modern browsers are pretty consistent in the way they render HTML/CSS, and their differences tend to be superficial. In the past you might have to deal with half a dozen browser layout bugs; now it's whether the browser supports rounded corners or drop shadows. If you have to support IE6, you'll obviously have much more problems, but if you're supporting IE6, you're probably working on a corporate web app that has a very uniform design. In which case, there's less need for a designer to work on every single page.
- KirinDave 16y agoIt's much the way you say, save for some very peculiar rendering differences between Firefox and Webkit family. Or it was, until Mobile became such a huge priority. As much as we wish it was otherwise, mobile is a tricky problem that often requires clever (and often painfully unobvious) workarounds for a variety of deployed browsers. The worst offender here is legacy android phones (which is to say, nearly all but the ones released last month), but iPhone deploys have problems too.