onderhond

11 ms·

61.
Reinstating HTML to its former glory: when mixins become skins(onderhond.com)
2 points by onderhond 14y ago|0 comments
62.
Css animation vs video: should we, not could we(onderhond.com)
3 points by onderhond 14y ago|0 comments
63.
Semicolons save lives (on robust code and killing ambiguity)(onderhond.com)
1 points by onderhond 15y ago|0 comments
64.
Introducing: the 5-year old responsive css grid(onderhond.com)
2 points by onderhond 15y ago|0 comments
65.
OOCSS is crap, long live OOHTML(onderhond.com)
1 points by onderhond 15y ago|0 comments
66.
Partial drop shadows (css3)(onderhond.com)
1 points by onderhond 15y ago|0 comments
67.
Whispers of a reponsive OS (a take on windows 8)(onderhond.com)
2 points by onderhond 15y ago|0 comments
68.
Rethinking content carousels - behavioral patterns vs content patterns(onderhond.com)
1 points by onderhond 15y ago|0 comments
69.
Internet Environmentalism (a tribute to the web)(onderhond.com)
1 points by onderhond 15y ago|0 comments
70.
by onderhond 15y ago
While I don't dispute any of those points, we (as an industry/community) should have matured enough by now to realize the dangers. "Don't develop for a specific browser" should be common knowledge and best practice no 1. Apparently many peo
71.
Webkit is the new ie6 (the trap of vendor prefixes)(onderhond.com)
4 points by onderhond 15y ago|2 comments
72.
Css3 3d-transform image gallery demo(onderhond.com)
2 points by onderhond 15y ago|0 comments
73.
Irresponsibly responsive: a flawed solution for a greater ideal(onderhond.com)
1 points by onderhond 15y ago|0 comments
74.
Content layout issues: on headings and floated images(onderhond.com)
1 points by onderhond 15y ago|0 comments
75.
Google and microdata - stealing your data(onderhond.com)
1 points by onderhond 15y ago|0 comments
76.
Front-end recap 2011(onderhond.com)
1 points by onderhond 15y ago|0 comments
77.
Html5 microdata here and now(onderhond.com)
1 points by onderhond 15y ago|0 comments
78.
Responsive html using back-end filter(onderhond.com)
2 points by onderhond 15y ago|0 comments
79.
The adverse effects of social(onderhond.com)
1 points by onderhond 15y ago|0 comments
80.
Scoped css and how it solves the limitations of the child combinator(onderhond.com)
1 points by onderhond 15y ago|0 comments
81.
Multi-level float trick(onderhond.com)
1 points by onderhond 15y ago|0 comments
82.
by onderhond 15y ago
Actually, the meta data you're talking about is there. You can even test the page to see that it should work (though it never appears like that in Google search results for me): http://www.google.com/webmasters/tools/richsnippets?url=http.
83.
In defense of semantic value (a 2-in-1 rant)(onderhond.com)
16 points by onderhond 15y ago|8 comments
84.
Css3 background transition (workaround)(onderhond.com)
1 points by onderhond 15y ago|0 comments
85.
Full-width row, centered content, 1 structural element: css tricks(onderhond.com)
1 points by onderhond 15y ago|0 comments
86.
Automated Less Parser with the Air Less Parser(onderhond.com)
1 points by onderhond 15y ago|0 comments
87.
Air Less (css) Parser (also for Windows)(proving-ground.be)
1 points by onderhond 15y ago|0 comments
88.
Abstract content categorization - separating fluff from core content(onderhond.com)
1 points by onderhond 15y ago|0 comments
89.
Targeting base variants with attribute selectors(onderhond.com)
1 points by onderhond 15y ago|0 comments
90.
by onderhond 15y ago
>> Generally ordered sequences are designed to be read from the start The spec makes no such claims, it just talks about sequences of documents in a very generic way. If the spec is not clear on this, it should be changed first. And

More ›