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 ..
CSS is text files and there are no line endings.
[deleted]
Incomplete List of Mistakes in the Design of CSS
41–50 of 111 posts
Re: Incomplete List of Mistakes in the Design of CSS
#42Earlier quoted context omitted.
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…
As a web dev of 11 years, I don't find writing cross browser code a nightmare. And any web site that doesn't work cross browser is by amateurs at best. 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.
As someone that had to support IE6 and Chrome at same time, I can't agree with this statement.
Re: Incomplete List of Mistakes in the Design of CSS
#43Earlier quoted context omitted.
As a web dev of 11 years, I don't find writing cross browser code a nightmare. And any web site that doesn't work cross browser is by amateurs at best. 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.
As someone that had to support IE6 and Chrome at same time, I can't agree with this statement.
Are you seriously trying to throw IE6 into this to attempt to prove your point? We aren't talking about antiquated browsers no one should be using today.
Re: Incomplete List of Mistakes in the Design of CSS
#44When do we get to throw the whole thing out and start again?
When we implement Display PostScript in js, so we can use it for the web?
HTML+CSS for publishing static, stand-alone documents isn't all that bad. It's terrible for making "applications", and it's terrible for composing more than one thing into a page (such as a header, footer, table of contents/menu).
I still think Adobe's idea[1] of flowing content through boxes (aka the "desktop publishing way") makes more sense than many of the other "augmentations" for CSS in terms of allowing complex layout. But it is an idea that makes sense for basically composing pages - not really for "applications".
I'm not convinced there's much of a meaningful overlap between layout for hypermedia meant to be read/watched/consumed - and "smart object graphs"/"applications" that are meant to be interacted with. Other than that the latter can be used to build the former -- but that's a terrible way to approach standardization -- just for the problems related to accessibility and machine readability alone.
If we could agree to keep the two things separate, make some real effort into making better readers for better (but probably dumber/less feature-full mark-up) -- we would probably be better off. Even such things as readability[2] shows the merit of this: it shows, by existing, the virtue of a browser that is better at being a hypertext browser is useful (and that a browser that's better at being an application run-time can be used to build and host a browser that's better at being a hypertext browser...).
But I don't think we should need for users to relate to that many layers: an OS and standard library that acts as platform for applications, an application that acts as a platform for applications and an application in the form of html+js+css+possibly some server side magic that acts as an application for browsing hypertext. I'd very much like an application (a browser) that's actually good at just browsing hypertext too.
[1] https://www.adobe.com/inspire/2014/01/complex-layouts-reflow... (Now dead AFAIK, even though there's a js polyfill)
Re: Incomplete List of Mistakes in the Design of CSS
#45Earlier quoted context omitted.
As someone that had to support IE6 and Chrome at same time, I can't agree with this statement.
Are you seriously trying to throw IE6 into this to attempt to prove your point? We aren't talking about antiquated browsers no one should be using today.
Are you seriously trying to deny IE6 isn't there in the wild? It was a job I had to do. I was paid to do it. It was awful. This happened circa 2013.
For contrast I now support IE8 and IE9. Without jQuery. It's bad. Really, really bad. Like, there isn't indexOf on Array and asking for polyfill is forbidden.
Re: Incomplete List of Mistakes in the Design of CSS
#46Earlier quoted context omitted.
As someone that had to support IE6 and Chrome at same time, I can't agree with this statement.
Are you seriously trying to throw IE6 into this to attempt to prove your point? We aren't talking about antiquated browsers no one should be using today.
[deleted]
Re: Incomplete List of Mistakes in the Design of CSS
#47Earlier quoted context omitted.
As someone that had to support IE6 and Chrome at same time, I can't agree with this statement.
Are you seriously trying to throw IE6 into this to attempt to prove your point? We aren't talking about antiquated browsers no one should be using today.
[deleted]
Re: Incomplete List of Mistakes in the Design of CSS
#48I can't help but wonder if the vertical margin collapsing (in general) would have seemed worth it if we weren't borrowing concepts from print media.
Re: Incomplete List of Mistakes in the Design of CSS
#49Earlier quoted context omitted.
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…
As a web dev of 11 years, I don't find writing cross browser code a nightmare. And any web site that doesn't work cross browser is by amateurs at best. 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.
As of today, you are right. However, we should be aiming towards a future where amateurs don't have to worry about browser incompatibilities. Coding time to be focused on building the product and its features, not juggling css rules to make it look the same across browsers.
Re: Incomplete List of Mistakes in the Design of CSS
#50Earlier quoted context omitted.
The whole idea of using (at least) three separate languages (HTML, JavaScript, CSS) would seem weird if it were proposed de novo . Consider that LaTeX manages to carry out all of those functions (layout, styling, and computation) using only one language.
React and jsx constructed dom using inline-styles brings the disparate technologies together in a composable way.
But without cascading, the whole point of css.