> 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.
Incomplete List of Mistakes in the Design of CSS
61–70 of 111 posts
Re: Incomplete List of Mistakes in the Design of CSS
#62Earlier quoted context omitted.
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.
You're one-off job is nothing to be holding up as an example of current web development. My company has 23 active clients and I can't tell you the last time, many years ago, we saw IE8 in the visitors logs much less anything less than that.
Re: Incomplete List of Mistakes in the Design of CSS
#63I mean, other than it's there on the browser, is there anything else?
Re: Incomplete List of Mistakes in the Design of CSS
#64Re: Incomplete List of Mistakes in the Design of CSS
#65You only have to look at vertical centering to see the problem. Situations that look almost the same require entirely different solutions, often causing a change to ripple through to parent/child/sibling elements.
Re: Incomplete List of Mistakes in the Design of CSS
#66Earlier 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…
The concept of executing untrusted code is entirely antithetical to security. Javascript, or any Turing complete language, or perhaps that even is too precise a constraint, is a remarkably bad idea for setting the style of anything that is otherwise static. There's no good reason that text and images need be stylized via a proper language rather than static, non-executable statements.
> As a user, I keep finding sites that simply don't work in Chrome or Safari or IE or whatever.
I keep finding sites that simply don't work at all in Firefox with NoScript. Many of those sites are primarily just text and images which don't display otherwise. It's completely insane from a security point of view.
Re: Incomplete List of Mistakes in the Design of CSS
#67another one not on the list is that any padding specified in % is always % of width. though this oddity/hack allows to responsively & proportionally scale images and backgrounds.
Re: Incomplete List of Mistakes in the Design of CSS
#68Earlier 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.
Good luck arguing with customers that will only pay when you achieve pixel perfect layouts across all browsers.
Or are able to replicate certain UI behaviors from native platforms.
Doing native stuff again, and I don't miss this type of arguments.
Re: Incomplete List of Mistakes in the Design of CSS
#69When do we get to throw the whole thing out and start again?
Re: Incomplete List of Mistakes in the Design of CSS
#70All that and nothing about variables?
input[type="submit"]{}
exist (but feel hacky as can be) and that if they did exist I would never, ever want to edit someone else's CSS file. Can you imagine the mess?It would be nice not to have to look for a style:
1. inline html
2. in the CSS file(s)
3. in JavaScript (or js library)
4. in the source code in the backend
to find that one edit you need to make.
I think that limitation is the most frustrating, that because CSS cannot 'see' beyond its own little home it bleeds out into other documents.