71–80 of 191 posts
First of all the post is arguing for more semantic HTML and says nothing about using semantic HTML5 tags over ? AFAIK semantic tags didn’t even exist before HTML5 which is definitely not the 90s.
I also find using the element generally be bad practice. There are much better/easier ways to build responsive tables using grid or flexbox than dealing with // everywhere.
Earlier quoted context omitted.
And for anyone who isn't familiar with (what I would consider) the most important difference in this use-case: borders affect the positioning of other elements, whereas outlines do not. You don't want to be using a temporary border, since it can significantly affect the layout of your site when you remove it.
* { box-sizing: border-box; } I have never wanted anything other than this behaviour, so I pretty much always include it when starting on a fresh project.
Block 1
Block 2
The author is arguing for semantic markup, but prior to HTML5 the concept barely existed. Everything was kludged together. Site layouts were tables. Later divs/spans ruled. Eventually sanity reigned and semantic elements were introduced. So while I don't disagree with what they're saying, the title is a bit of a misnomer. >[Don't] create tables built out of custom div elements Tables aren't responsive. Those fancy di…
Not really. The concept existed and was well known in many developer circles (e.g. List Apart Issue 268 from 2008 http://alistapart.com/issue/268/).
Earlier quoted context omitted.
> I find zero value in using ul/li's for lists that aren't bulleted Browsers don't care. You may not care either. But people with disabilities attempting to make sense of your website do, very much so. There's absolutely no reason __not__ to use semantic HTML, and many reasons to do so.
Maybe I don't care about people with disabilities in the same way that I don't care about people using IE6.
Instead of a border I tend to have a debug helper that adds a 1px outline of cyan or pink. To get the “bones” of a component or page. Good advice. Definitely sounds like captain obvious but it’s also something I think needs to be said.
Handy bookmarklet javascript:(function(){Array.from(document.body.getElementsByTagName('*'), e => e.style.outline = '2px dotted orangered');})();
The author is arguing for semantic markup, but prior to HTML5 the concept barely existed. Everything was kludged together. Site layouts were tables. Later divs/spans ruled. Eventually sanity reigned and semantic elements were introduced. So while I don't disagree with what they're saying, the title is a bit of a misnomer. >[Don't] create tables built out of custom div elements Tables aren't responsive. Those fancy di…
> The author is arguing for semantic markup, but prior to HTML5 the concept barely existed Not really. The concept existed and was well known in many developer circles (e.g. List Apart Issue 268 from 2008 http://alistapart.com/issue/268/ ).
This article is from 2008, but I think it would be quite challenging to find something similar from 1999.
Earlier quoted context omitted.
Maybe I don't care about people with disabilities in the same way that I don't care about people using IE6.
You can upgrade your browser but you can't upgrade to a body that isn't disabled (yet)
Funny enough, only changing the body's background color to "lightgrey" and the font face to "serif" makes it look exactly like that.
My God that page is beautiful. Over half the vertical space is content without me touching anything. No banner bar asking me to install some bullshit mobile app. No 800-pixel panel at the bottom telling me what a cookie is. No incredibly obnoxious warning that I only have one more free article before the wisdom of the ages is lost to me so I'd better cough up five bucks.
Agree. Is it a Jekyll theme or some totally customized template?