21–30 of 111 posts
Layout is about the relationship between TWO THINGS. If you have a layout language that deals with only one thing at a time, then you have failed.
> Box-sizing should be border-box by default. Didn't older versions of IE do precisely that, leading to endless frustration? I hate to say it but MS did something right for once.
However, since IE had 95% market share, everyone marked up their site according to Microsoft's model instead of the W3C. It's affectionately called "quirks mode" and really screwed people up, remnants of which I still see today.
Earlier quoted context omitted.
In your latex equation, you are missing where the data goes. The idea for html/css/js is that data goes into the html, layout and styling into CDs and interactivity is defined in JavaScript. That makes sense. The problem is that we never got anything close to that.
The problem is it doesn't really make sense in 2015. Or rather, it only makes sense if you accept the technical debt inherited from HTML, which is itself the simplified stepchild of SGML, which was a 1960s idea and firmly rooted in paper publishing. Separating content and presentation isn't a bad idea. The badness happened because JavaScript - or some other web programming language - didn't appear until HTML was esta…
I don't know what web sites you visit where you have such issues but I haven't seen them in years except for the occasional goofball site.
Why do keywords have to end in a colon. couldn't the parser use space " " to detect the end of a word, like in C ..
When do we get to throw the whole thing out and start again?
I always found it interesting that style tags were designed as , implying that new style standards could be introduced down the road. (for a while I thought might get real… oh sweet naivety)
though this oddity/hack allows to responsively & proportionally scale images and backgrounds.
Earlier quoted context omitted.
I always found it interesting that style tags were designed as , implying that new style standards could be introduced down the road. (for a while I thought might get real… oh sweet naivety)
The script type is a possibility but you have to make it work. I've forgotten the details.
This doesn't even address the fundemantal design flaw with CSS: (paraphrased badly from a quote by Casey Muratori) Layout is about the relationship between TWO THINGS. If you have a layout language that deals with only one thing at a time, then you have failed.
> white-space: nowrap should be white-space: no-wrap and line wrapping behavior should not have been added to white-space > word-wrap/overflow-wrap should not exist. Instead, overflow-wrap should be a keyword on 'white-space', like nowrap (no-wrap) Well, which is the mistake?
Earlier quoted context omitted.
The script type is a possibility but you have to make it work. I've forgotten the details.
Since the browser will not react to these nodes, you can add some JS code that will detect them and hand off content interpretation to other mechanisms.
…