The recent discussion of possibly making the href attribute global
brings to mind a broader issue. To what extent should semantics and
behavior belong to specific elements, and to what extent should they
be carried by global attributes that can apply to any element?
XHTML2 moves a lot
- Original Message -
From: Maciej Stachowiak [EMAIL PROTECTED]
To: WHATWG Mailing List [EMAIL PROTECTED]
Sent: Monday, March 12, 2007 10:25 AM
Subject: [whatwg] Attributes vs. Elements
|
|
| The recent discussion of possibly making the href attribute global
| brings to mind
XHTML2 moves a lot of semantics and behavior from elements to global
attributes. For example, href can turn any element into a hyperlink,
and src can turn any element into an image.
I liked the href adding a link to any object, but the src, I don't care
for. I can already set a background
Finally, I'd like to conclude with this reductio ad absurdum of the XHTML2
approach. If assigning behavior and semantics to attributes is so much
better, why not just have a single elt element:
elt role=paragraphMy cat is really cute: elt src=mycat.jpegpicture of
my cat/elt. Check out
On 12 Mar 2007, at 20:19, Andrew Fedoniouk wrote:
Case:
td a href=1.htmxyz/a/td
td a href=2.htmxyz-xyz-xyz/a/td
is perfectly valid from some abstract semantic machine
point of view but for human these two cells are not
equal. At least hit area is different. And visual perception too.
All you
On Mon, 12 Mar 2007, carmen wrote:
Finally, I'd like to conclude with this reductio ad absurdum of the
XHTML2 approach. If assigning behavior and semantics to attributes is
so much better, why not just have a single elt element:
elt role=paragraphMy cat is really cute: elt
On 12 Mar 2007, at 20:19, Andrew Fedoniouk wrote:
Case:
td a href=1.htmxyz/a/td
td a href=2.htmxyz-xyz-xyz/a/td
is perfectly valid from some abstract semantic machine
point of view but for human these two cells are not
equal. At least hit area is different. And visual perception too.
All you
Robert wrote:
As I followed the thread, thinking about styling the element was the
clincher for me. IE 6 doesn't support attribute based selectors. So, I,
for one, couldn't use it until IE 6 (haven't tested attribute selectors in
IE 7, since I stopped using them in light of IE 6) lost most of
- Original Message -
From: Nicholas Shanks [EMAIL PROTECTED]
To: Andrew Fedoniouk [EMAIL PROTECTED]
Cc: WHATWG List [EMAIL PROTECTED]
Sent: Monday, March 12, 2007 12:59 PM
Subject: Re: [whatwg] Attributes vs. Elements
| On 12 Mar 2007, at 20:19, Andrew Fedoniouk wrote:
|
| Case
ddailey wrote:
The ease of using DOM methods to find tags, as opposed to attributes,
tends to suggest that all things having href's should be easily
findable by script. a works nicely for that, but would the
availability of a document.links array then include all things with
href's?
In
On 12/03/2007 21:53, [EMAIL PROTECTED] wrote:
XHTML2 moves a lot of semantics and behavior from elements to global
attributes. For example, href can turn any element into a hyperlink,
and src can turn any element into an image.
I liked the href adding a link to any object, but the src, I
Le 13 mars 2007 à 03:25, Maciej Stachowiak a écrit :
The recent discussion of possibly making the href attribute global
brings to mind a broader issue. To what extent should semantics and
behavior belong to specific elements, and to what extent should
they be carried by global attributes
On 13/03/2007 07:12, Karl Dubost wrote:
more references, food for thoughts.
* Markup design: elements or attributes?
http://annevankesteren.nl/2004/07/markup
* Principles of XML design: When to use elements versus attributes
http://www-128.ibm.com/developerworks/xml/library/x-eleatt.html
On Tue, 13 Mar 2007, Daniel Glazman wrote:
I would add a major principle, rarely explicit : PRAGMATISM. Sometimes
purity calls for an element while browser implems call for an attribute
; or the contrary. And even if implem issues should not apply in theory,
they do apply in real life...
Le 13 mars 2007 à 15:23, Daniel Glazman a écrit :
I would add a major principle, rarely explicit : PRAGMATISM.
Sometimes purity calls for an element while browser implems
call for an attribute ; or the contrary. And even if implem
issues should not apply in theory, they do apply in real life...
On 13/03/2007 07:26, Ian Hickson wrote:
Don't worry, the WHATWG basic principles put pragmatism first. It's the
only way to get a spec implemented, and without implementations, specs are
somewhat academic.
It's also the only way to do something not totally disconnected from
users' needs...
On 13/03/2007 07:29, Karl Dubost wrote:
It comes with test cases and implementations.
I disagree 100%. Pragmatism is a state of mind, not a process.
Tests and implementations can be successful on a spec, and the spec
can remain a failure because it lacks pragmatism.
/Daniel
17 matches
Mail list logo
