Comments on: Aside Revisited http://html5doctor.com/aside-revisited/ helping you implement HTML5 today Mon, 06 Feb 2012 20:26:52 +0000 hourly 1 http://wordpress.org/?v= By: anon http://html5doctor.com/aside-revisited/#comment-21188 anon Tue, 03 Jan 2012 19:01:07 +0000 http://html5doctor.com/?p=1015#comment-21188 This is why people are not going to use this spec because it is going to change and change and change. How am I supposed to convince clients to recode their website to change according to this spec above. Personally, I do not think you guys have it together and you cannot predicate the outcome. You are creating a messy spec and should keep it simple. This is why people are not going to use this spec because it is going to change and change and change.
How am I supposed to convince clients to recode their website to change according to this spec above.

Personally, I do not think you guys have it together and you cannot predicate the outcome.

You are creating a messy spec and should keep it simple.

]]> By: Oli Studholme http://html5doctor.com/aside-revisited/#comment-21140 Oli Studholme Tue, 27 Dec 2011 13:03:45 +0000 http://html5doctor.com/?p=1015#comment-21140 @Johan — This way you can also include a navigation title and other content, and lists are already fully supported and understood. @Mike — I don’t think search engines will treat <code><aside></code> differently. I personally find it useful to have an element for this purpose. It’s also possible to <em>do more stuff</em> if your code is more semantic, with styling being only a basic example. Of course there’s nothing to stop you using <code><section></code>, or <code><div></code>. @Leprechaun — While I personally agree, it <em>is</em> somewhat gauche to say so, and adds nothing to the discussion on <code><aside></code>. Also, “I beg you pardon”? “thickness”?? ppl in glasshouses… ;) @Johan — This way you can also include a navigation title and other content, and lists are already fully supported and understood.

@Mike — I don’t think search engines will treat <aside> differently. I personally find it useful to have an element for this purpose. It’s also possible to do more stuff if your code is more semantic, with styling being only a basic example.

Of course there’s nothing to stop you using <section>, or <div>.

@Leprechaun — While I personally agree, it is somewhat gauche to say so, and adds nothing to the discussion on <aside>.

Also, “I beg you pardon”? “thickness”?? ppl in glasshouses… ;)

]]> By: Leprechaun http://html5doctor.com/aside-revisited/#comment-21139 Leprechaun Tue, 27 Dec 2011 11:58:47 +0000 http://html5doctor.com/?p=1015#comment-21139 I beg you pardon, but I must admit I find it astounding to read such refined semantical disquisitions from someone who doesn't know the difference between "it's" and "its". Have you ever thought about going humbly back to basic English grammar? Believe me or not, that would give more "thickness" to your writings, much more than being part of the hippest web communities. I mean this from the heart. I beg you pardon, but I must admit I find it astounding to read such refined semantical disquisitions from someone who doesn’t know the difference between “it’s” and “its”.
Have you ever thought about going humbly back to basic English grammar? Believe me or not, that would give more “thickness” to your writings, much more than being part of the hippest web communities.
I mean this from the heart.

]]> By: Mike http://html5doctor.com/aside-revisited/#comment-20636 Mike Wed, 14 Dec 2011 22:31:19 +0000 http://html5doctor.com/?p=1015#comment-20636 There seems to be lots of discussion on when to use the "aside" tag, but no indication as to "why" to use it. In other words, if I use it to whose advantage is it? 1) To a page coders advantage, so that they can more easily tell which content is only generally related? OR 2) To a search engine so that it can rule out various page content? Since there is no visual difference, I may as well just use "section". Where is the advantage to me as a coder? There seems to be lots of discussion on when to use the “aside” tag, but no indication as to “why” to use it.

In other words, if I use it to whose advantage is it?

1) To a page coders advantage, so that they can more easily tell which content is only generally related?

OR

2) To a search engine so that it can rule out various page content?

Since there is no visual difference, I may as well just use “section”.

Where is the advantage to me as a coder?

]]> By: Johan http://html5doctor.com/aside-revisited/#comment-17423 Johan Tue, 30 Aug 2011 06:00:22 +0000 http://html5doctor.com/?p=1015#comment-17423 well - i guess it will be more semantic... before the nav tag (html5) i never wrapped my main navigation in a div. i added my nav id to the ul tag: <code><ul id="nav"></code>. sometimes it feels as if HTML5 makes things a bit bloated and not as streamline/light as it says it is. i also think that people don't realize that all tags are also containers. for example: why have a wrapper div - just give the body tag a width and margin auto to wrap your site and align it centre. well – i guess it will be more semantic… before the nav tag (html5) i never wrapped my main navigation in a div. i added my nav id to the ul tag: <ul id="nav">. sometimes it feels as if HTML5 makes things a bit bloated and not as streamline/light as it says it is. i also think that people don’t realize that all tags are also containers. for example: why have a wrapper div – just give the body tag a width and margin auto to wrap your site and align it centre.

]]> By: Oli Studholme http://html5doctor.com/aside-revisited/#comment-17422 Oli Studholme Tue, 30 Aug 2011 05:31:01 +0000 http://html5doctor.com/?p=1015#comment-17422 @Johan — how would dropping <code><ul><li></code> and using <code><ni></code> help you? are nav items something other than an unordered list? @Johan — how would dropping <ul><li> and using <ni> help you? are nav items something other than an unordered list?

]]> By: Johan http://html5doctor.com/aside-revisited/#comment-17421 Johan Tue, 30 Aug 2011 05:14:04 +0000 http://html5doctor.com/?p=1015#comment-17421 thanks for the post! i agree with the other guys that said there should be a tag sidebar tag and while we’re at it drop the ul li tags inside the UL and create nav item "ni" tags. thanks for the post! i agree with the other guys that said there should be a tag sidebar tag and while we’re at it drop the ul li tags inside the UL and create nav item “ni” tags.

]]> By: En nybegynners vei fra papirskisser til HTML5 — iAllenkelhet http://html5doctor.com/aside-revisited/#comment-17202 En nybegynners vei fra papirskisser til HTML5 — iAllenkelhet Wed, 17 Aug 2011 07:50:22 +0000 http://html5doctor.com/?p=1015#comment-17202 [...] med en klasse eller id, så har HTML5 tags med semantisk betydning, eksempelvis article, aside og nav. I tillegg har en rekke tags blitt redefinert, for eksempel [...] [...] med en klasse eller id, så har HTML5 tags med semantisk betydning, eksempelvis article, aside og nav. I tillegg har en rekke tags blitt redefinert, for eksempel [...]

]]> By: Alohci http://html5doctor.com/aside-revisited/#comment-17039 Alohci Wed, 03 Aug 2011 20:51:28 +0000 http://html5doctor.com/?p=1015#comment-17039 @Andi - probably not. The spec says: <blockquote>The aside element represents a section of a page that consists of content that is tangentially related to the content around the aside element, and <em>which could be considered separate from that content.</em></blockquote> (my emphasis) It's unlikely that the additional information in that context could be considered separate from the form field. In addition, <aside> is a sectioning element, so it ought to have a natural header for use in the document outline. That too is unlikely to be the case for your situation. The best approach it probably to just add a second <label> element pointing to the same form field. @Andi – probably not. The spec says:

The aside element represents a section of a page that consists of content that is tangentially related to the content around the aside element, and which could be considered separate from that content.

(my emphasis)

It’s unlikely that the additional information in that context could be considered separate from the form field.

In addition, <aside> is a sectioning element, so it ought to have a natural header for use in the document outline. That too is unlikely to be the case for your situation.

The best approach it probably to just add a second <label> element pointing to the same form field.

]]> By: Andi Smith http://html5doctor.com/aside-revisited/#comment-17034 Andi Smith Tue, 02 Aug 2011 21:16:53 +0000 http://html5doctor.com/?p=1015#comment-17034 If I wanted to use <aside> for an aside to my form fields, would that be allowed? E.g. if I had an input, which already has a label as a short definition but I wanted to add additional information. Andi If I wanted to use <aside> for an aside to my form fields, would that be allowed?

E.g. if I had an input, which already has a label as a short definition but I wanted to add additional information.

Andi

]]>