Is it ok to nest section elements inside the aside element? Can't
come up with anything about this scenario on Google...
I'll have a first real attempt at an HTML5 page for critique soon...
--
Tom Livingston | Senior Interactive Developer | Media Logic |
ph: 518.456.3015x231 | fx:
On 1/24/11 2:41 PM, Tom Livingston wrote:
Is it ok to nestsection elements inside theaside element? Can't
come up with anything about this scenario on Google...
I'll have a first real attempt at an HTML5 page for critique soon...
Yes.
http://gsnedders.html5.org/outliner/
On 1/24/11 4:37 PM, David Laakso wrote:
On 1/24/11 2:41 PM, Tom Livingston wrote:
Is it ok to nestsection elements inside theaside element? Can't
come up with anything about this scenario on Google...
I'll have a first real attempt at an HTML5 page for critique soon...
Yes.
Best,
~d
Hello,
Could someone please clarify this for me. I realise that HTML5 has introduced
new semantic elements such as header, aside etc., but does this really
increase the expressive power of the markup? Can't the same thing be achieved
in HTML 4.x using classes (e.g. p class=header)?
I am
I use HTML5 as my doctype, but I don't use the new tags. It's wise to be
very concerned about backwards compatibility.
Are they more semantic - I suppose. If IE doesn't understand the new
tags I'd leave them be until another day.
*Joseph R. B. Taylor*
/Web Designer/Developer/
? Can't the same thing be achieved in HTML 4.x using classes
Not really.
The power of semantics really has to lie in the fact that they are used
consistently across a wide range of disparate systems.
The fact that all the sites you build have a consistent ‘header’ class in them
doesn’t mean that
Is it ok to nest section elements inside the aside element? Can't
come up with anything about this scenario on Google...
Hi.
The section element represents a generic section of a document or application.
A section, in this context, is a thematic grouping of content, typically with a
Could someone please clarify this for me. I realise that HTML5 has introduced
new semantic elements such as header, aside etc., but does this really
increase the expressive power of the markup? Can't the same thing be achieved
in HTML 4.x using classes (e.g. p class=header)?
I am
I use HTML5 as my doctype, but I don't use the new tags. It's wise to be very
concerned about backwards compatibility.
Are they more semantic - I suppose. If IE doesn't understand the new tags I'd
leave them be until another day.
Hi.
Is the backwards compatibility really a problem?
What
So called 'semantic classnames' are not semantic at all except in the
case of microformats. The whole point of semantic markup is that the
author and user agree on the terminology and the meaning, and that is
not the case with semantic classnames no matter how obvious they may
seem to you.
On 25 January 2011 09:44, grant_malcolm_bai...@westnet.com.au wrote:
Hello,
Could someone please clarify this for me. I realise that HTML5 has
introduced new semantic elements such as header, aside etc., but does
this really increase the expressive power of the markup?
In the long run,
One word : semantics.
It all has to do with what the tags mean to the computer. For example, you
can write div class=code to specify that the markup in that div is code
and should be displayed as such. However, to the browser, the means nothing
more than div class=happyfuntime. They're both just
Could someone please clarify this for me. I realise that HTML5 has
introduced new semantic elements such as header, aside etc., but
does this really increase the expressive power of the markup? Can't
the same thing be achieved in HTML 4.x using classes (e.g. p
class=header)?
I am reluctant
On Mon, 24 Jan 2011, Christian Snodgrass wrote:
One word : semantics.
It all has to do with what the tags mean to the computer. For example, you
can write div class=code to specify that the markup in that div is code
and should be displayed as such. However, to the browser, the means nothing
On Mon, Jan 24, 2011 at 8:47 PM, Chris F.A. Johnson
ch...@cfajohnson.com wrote:
On Mon, 24 Jan 2011, Christian Snodgrass wrote:
Now, if you use the new code element instead, that tells the browser it is
code.
There's a new code element? How does it differ from the old one?
Without using
At the moment, HTML5 doesn't really bring a significant benefit, but
that will change (in years rather than months).
I beg to differ. I believe there are a lot of great stuff that we can start
using today (mostly related to form controls).
See http://diveintohtml5.org/forms.html and this one
Hi Grant
As html 5 new tag are not supported to the IE7 and older version as well. For
your query regard the use of p class-“Header” I preferred to use div
instead of the p tag.
p tag has his own value for the margin… and this will difficult to maintain
the same space in IE and
On 25/01/2011 12:34 PM, Christian Snodgrass wrote:
One word : semantics.
Assuming authors use the element in the same way, and assuming the
element has only one semantic meaning possible.
--
Andrew Cunningham
Senior Project Manager, Research and Development
Vicnet
State Library of Victoria
Hi Geroge
Visit this article and read the article 4.4. this will give you all the answer
you have.
http://www.whatwg.org/specs/web-apps/current-work/multipage/
Have a nice day
Birendra
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf
19 matches
Mail list logo
