I think your misunderstanding lies earlier than my last post.
If someone wishes to use an abbr tag in the way that it was intended
by the spec, then that is perfectly acceptable, obviously. If their
scripting then fails in IE they have three clear choices - write a more
robust script,
Thierry,
I think your misunderstanding lies earlier than my last post.
If someone wishes to use an abbr tag in the way that it was intended
by the spec, then that is perfectly acceptable, obviously. If their
scripting then fails in IE they have three clear choices - write a more
robust script,
Thierry Koblentz wrote:
Does that mean we should drop the ABBR element because IE can't handle it
properly?
Julien wrote:
You have the answer:
http://www.tjkdesign.com/articles/how-to_fix_the_ABBR_element.asp
;)
Touché!
No, its not. In this case, if any single browser breaks a related
script, then the mark-up cannot be used - working on the majority is
not enough to make it viable.
Does that mean we should drop the ABBR element because IE
can't handle it properly?
In what way is that the same as the
No, its not. In this case, if any single browser breaks a related
script, then the mark-up cannot be used - working on the majority is
not enough to make it viable.
Does that mean we should drop the ABBR element because IE
can't handle it properly?
In what way is that the same as
On 22 May 2008, at 05:15, Julián Landerreche wrote:
I wasn't convinced at first because:
- fieldset/legends are used in forms to group controls. This is
common usage/practice, and even more, it's the usage recommended by
the W3C, as some of you already remarked on this thread, .ç
Yes, that
Judging by how quickly you replied, I am doubtful that you managed to
test every browser version known to mankind before you replied - one
or two combinations doesn't really make effective proof!
In any case, is this just a case of the browser inserting what it thinks
should be there, as with
[EMAIL PROTECTED] wrote:
Judging by how quickly you replied, I am doubtful that you managed to
test every browser version known to mankind before you replied - one
or two combinations doesn't really make effective proof!
Au contraire, one is enough to prove the contention wrong, but in
any
On 22 May 2008, at 11:12, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
In any case, is this just a case of the browser inserting what it
thinks
should be there, as with tbody ?
With tbody, the DTD says what must be there (and also that the start
and end tags for tbody are optional).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hassan Schroeder
Sent: Thursday, May 22, 2008 2:27 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Fwd: using fieldsets and legends (outside a
form) for adding structural mark-up
Au contraire, one is
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Thursday, May 22, 2008 8:26 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] Fwd: using fieldsets and legends (outside a form) for
adding structural markup
-Original
Thierry Koblentz wrote:
Does that mean we should drop the ABBR element because IE can't handle it
properly?
Better to just drop IE
;-)
mark
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
Hi Julien
A little history may help.
In the early days of standards-based markup, people were looking for more
structural ways to markup content. It was a bit of a wild west and you saw
various attempts to replace a table with x, y, or z. Unfortunately, the
standards-based developers did not
So, there were a number of sites that began using fieldsets and legends
outside of forms.
You may still find documentation talking about how nice it is to work
with. Unfortunately,
fieldsets and legends are only for forms and you shouldn't use them
otherwise. I've actually
been dealing with
Hi Julian,
One more subtle point here (after taking this discussion into the office
with guys that work with me) a point was made today that within DOM
fieldset is part of the form hence you cannot reference a fieldset
through DOM unless it is inside a form, so it is definitely a wrong
approach
Jason Grant wrote:
One more subtle point here (after taking this discussion into the office
with guys that work with me) a point was made today that within DOM
fieldset is part of the form hence you cannot reference a fieldset
through DOM unless it is inside a form ...
An easy theory to
Although since the beginning I wasn't convinced (that's why I started this
thread) about using fieldset/legend for adding structural labels to
non-form content (particularly, action links or site nav links), I'm
still not convinced by exposed counter arguments against using it.
I wasn't convinced
Hello Julian,
If you are unsure about what an HTML tag is there for, look up in the W3C
specs. http://www.w3.org/TR/html401/interact/forms.html#edef-FIELDSET
It is pretty clear to me there that fieldset element exists for the
purpose of grouping form elements together, and not for other
What if your fieldset is intended for an AJAX application? And thus
will not require a form (as your data is not sent through the form,
but is picked up by javascript)? Indeed, my opinion is that a
fieldset should only contain form elements, but not necessarily be
inside a form tag.
I do
Needless to say that your application should progressively
enhancehttp://en.wikipedia.org/wiki/Progressive_Enhancementthrough
the presentation layers.
So, irrespective of what technology (or mix of technologies) you are using,
the basic (X)HTML page should make total sense with everything (images,
Hi Julian,
strong is for emphasis. I am on your side on that one.
divs are for separating components/sections of a page and can be
semantically very strong, especially when given a meaningful class or id
name (e.g. header, footer, contacts, product, etc.)
fieldset however is quite specifically
21 matches
Mail list logo
