I still haven't found one good reason to use any of the semantic HTML5 tags instead of just good old divs. This didn't convince me.
… header {…} is slightly shorter than … .header {…}
And what does
The ﹤main﹥ element
31–40 of 93 posts
Re: The ﹤main﹥ element
#32Re: The ﹤main﹥ element
#33Earlier quoted context omitted.
I think that CSS is the biggest failure here. Let's say I have a blog, so for article page markup should be something like this: lorem ipsum search That way screen readers, search engines, etc will get the important stuff first and less important stuff afterwards. But since the common way of presenting blog is more like this: search I either have to do some hacky position:absolute things, crazy floats with negative e…
I think you should try using WAI-ARIA standards[0] instead. That way you can keep your structure the same and give screen readers and such a better description of what's going on in your page. [0]: http://www.w3.org/WAI/intro/aria
WAI-ARIA support is abysmal, not only does it vary between screen readers but also between various browsers using the same screen reader.
Re: The ﹤main﹥ element
#34I still haven't found one good reason to use any of the semantic HTML5 tags instead of just good old divs. This didn't convince me.
The nightmare of divs makes it hard to find the end div unless someone is disciplined enough to indent the code consistently OR if comments are inserted at the end of divs as in
...
Re: The ﹤main﹥ element
#35Sounds convenient for one major use: letting web-scraping and readability-like tools know that everything outside of is alright to throw away.
I consider navigation not alright to throw away, but wouldn't put it in either.
For something like Readability, you don't want to keep the navigation. The whole point is to get just the content, and make it readable.
Re: The ﹤main﹥ element
#36Sounds convenient for one major use: letting web-scraping and readability-like tools know that everything outside of is alright to throw away.
I consider navigation not alright to throw away, but wouldn't put it in either.
But if I'm using a readability tool to access your content, I certainly don't want the navigation to be a part of it.
Re: The ﹤main﹥ element
#37I was honestly a little baffled to come into this thread and discover people were having trouble with semantic HTML. It's not hard to use, you just need to be inventive with your CSS. A page without divs, spans, strongs and bigs should be everyone's goal.
Re: The ﹤main﹥ element
#38I still haven't found one good reason to use any of the semantic HTML5 tags instead of just good old divs. This didn't convince me.
For tools which simplify/standarize webpage presentation (e.g., Pocket, Instapaper, Readability) this makes parsing easier.
I'm leaning strongly toward favoring a browser model which just says buggerall to the site's layout and applies a user-specified preference of styling consistently. I'm already pretty much doing this myself via my own CSS mods using Stylebot, and in most cases it makes sites vastly more readable and less distracting.
In particular crap such as Buzzfeed (I call my styling "unbuzzed"): https://plus.google.com/104092656004159577193/posts/G6pzJBLK...
Re: The ﹤main﹥ element
#39Re: The ﹤main﹥ element
#40I was honestly a little baffled to come into this thread and discover people were having trouble with semantic HTML. It's not hard to use, you just need to be inventive with your CSS. A page without divs, spans, strongs and bigs should be everyone's goal.
Could you show us one of your websites "without divs, spans"?