51–60 of 65 posts
This looks so good and nice. I would definitely use it with some modifications for a drop in replacement of markdown block inside some blog. But will wrap it in a class ( e.g. .article-content ). What is a beneficial stylesheet system, according to me, is a system that can scale and gives you the opportunity to create a complicated website. This unfortunately doesn't. Sorry.
It however pains me how this is heralded as something new by HN. "Finally, someone figured out how to do CSS correctly!" ... Shows how most people have no idea how to work with CSS yet comment on it. CSS Resets and Normalize stylesheets have been used for decades.
Edit: I feel like I should add this I'm not bashing this project. I recognize the quality of it.
Bootstrap (and various other similar systems) lets you specify this, by adding a class of .initialism to the
Earlier quoted context omitted.
http://www.w3.org/Consortium/join
Or just join www-style[1] or public-webapps[2], or there's the WHATWG mailing list for all of its specs[3]. All of these are totally free to join. [1]: https://lists.w3.org/Archives/Public/www-style/ [2]: https://lists.w3.org/Archives/Public/public-webapps/ [3]: https://whatwg.org/mailing-list#specs
This is true, but misleading.
It's true that it costs nothing to join a W3C mailing list. However, if you join such a list and actually try to participate, you rapidly discover that:
1) Making a meaningful contribution requires being able to commit enough time to shepherd that contribution through the twin gauntlets of W3C process and internal committee politics;
2) The only people who can justify committing that kind of time are people for whom doing so is their full-time job;
3) Almost all of the people whose full-time job is participating in a W3C list are browser implementers;
4) Browser implementers, unsurprisingly, tend to see the problems and concerns of browser implementers as being inherently more important than the problems and concerns of other types of stakeholders in the Web (e.g. Web developers, marketers/adtech people, privacy advocates, accessibility advocates, etc.).
You generally discover this the first time you have the temerity to offer an opinion, at which point you are bombarded with responses about how you don't really understand the issue because you're not a browser implementer and have no idea how hard it is to be a browser implementer because browser implementers have it harder than anybody else in the world including lepers and orphans and seriously you have no freaking idea how anything in the world even works and bro do you even implement we didn't think so thanks for your useless opinion now go away.
(Full disclosure: I may still be a little bitter from my participation in the HTML5 process.)
Not all abbreviations are initialisms, and small caps therefore aren't always appropriate. Bootstrap (and various other similar systems) lets you specify this, by adding a class of .initialism to the http://getbootstrap.com/css/#type-abbreviations
The notion that this feels refreshing enough to be compelling news is a testament to how incredibly convoluted our use of browser technology has become. It's nice to be reminded of CSS's humbler, less-radioactive days...
CSS has always been broken. For example, for many years it was impossible to vertically center an element in its parent (without extensive hacks). And still there are weird things like not being able to select all elements A which have B in them with a single CSS rule. In my opinion, the reason that web technology sucks is that the standards are being created for novices instead of for developers. If the web was a pl…
You mean like this?
:matches(A B) {
color: blue;
}
font-feature-settings: “smcp”;
font-feature-settings: “c2sc”;
More at https://drafts.csswg.org/css-fonts/#font-variant-caps-prop.
Safari’s renderring engine WebKit just got font-feature-settings: support: https://twitter.com/webkit/status/631827777319256064.
Very nice project. This is a quality normalize stylesheet. It however pains me how this is heralded as something new by HN. "Finally, someone figured out how to do CSS correctly!" ... Shows how most people have no idea how to work with CSS yet comment on it. CSS Resets and Normalize stylesheets have been used for decades. Edit: I feel like I should add this I'm not bashing this project. I recognize the quality of it.
Perhaps there are some things that could be incorporated from Normalize, which documents the subtle (and not so subtle) differences in how browsers handle certain elements: https://github.com/necolas/normalize.css