At 11:15 PM 11/5/2005, Christian Montoya wrote:
What I would like to do is have a list header, much like tables have
table headers.
I wrote more about this here:
http://montoya.rdpdesign.com/2005/11/06/list-headers-an-idea/
But what it basically boils down to is having a tag I call list
header
Great idea, Christian, but you've been scooped: LH was part of the
1993 HTML3 specification in the UL, OL, and DL definitions, such as:
http://www.w3.org/MarkUp/html3/deflists.html
LH appears to have disappeared from the specs between HTML 3.0 and
3.2, but I wasn't able to discover when or
Hi,
And what about the definition list? It seems to me that is a plain way
to do that job m8.
dl
dtheader/dt
dditem1/dd
...
/dl
dl is handy because you can use more headers (dt tags) in the same list etc.
Regards,
Janos
2005/11/6, Christian Montoya [EMAIL PROTECTED]:
Great idea, Christian,
Or you could nest it, even, if that's valid. Sounds awful complex though...
dl
dtheader/dt
dd
ul
li/li
/ul
/dd
/dl
Though I remain uncertain as to the semantic value of that, even if it is valid.
Josh
On 11/6/05, Janos Hardi [EMAIL PROTECTED] wrote:
And what about the definition
I think those both do not solve the problem. How do I give a
definition list a header?
h1Dictionary/h1
dl
dtword/dt
dddef/dd
dtword/dt
dddef/dd
/dl
I would like to do:
dl
lhDictionary/lh
dt.../dt
dh.../dh
/dl
Any solution that involves nested lists is really bad IMO. That makes
things too
Christian Montoya wrote:
I think those both do not solve the problem. How do I give a
definition list a header?
I understand your desire to be completely explicit in terms of assigning
a header to a list, I'd say that (X)HTML is just not that explicit a
language in that respect, and that
I understand your desire to be completely explicit in terms of assigning
a header to a list, I'd say that (X)HTML is just not that explicit a
language in that respect, and that *source order* is used to infer a lot
of this type of assignment. Think, for instance, about a normal page
structure
Hi,
I do not know is this a solution for our problem but it seems it does
the semantic and valid job - i made it a bit complex but its now a
closely real-world example :)
h1label for=stuff-lista accesskey=0 href=This is a Header
for my stuff list/a/label/h1
ul id=stuff-list
lia accesskey=1
Janos Hardi wrote:
I do not know is this a solution for our problem but it seems it does
the semantic and valid job - i made it a bit complex but its now a
closely real-world example :)
h1label for=stuff-lista accesskey=0 href=This is a Header
for my stuff list/a/label/h1
ul id=stuff-list
lia
I do not know is this a solution for our problem but it seems it does
the semantic and valid job - i made it a bit complex but its now a
closely real-world example :)
h1label for=stuff-lista accesskey=0 href=This is a Header
for my stuff list/a/label/h1
ul id=stuff-list
lia accesskey=1
Hey Patrick,
Yes I understand your doubts but the starting point was that Chris
wanted a Hx element semantically connected with a list (with valid
xhtml code).
I think my solution is okay but I'd never use it ;)
I use the plain DL that has DT elements useable for pseudo-headings.
Janos
Hey Patrick,
Yes I understand your doubts but the starting point was that Chris
wanted a Hx element semantically connected with a list (with valid
xhtml code).
I think my solution is okay but I'd never use it ;)
I use the plain DL that has DT elements useable for pseudo-headings.
Janos
Yes it seems but:
Navigation lists are intended to be used to define collections of
selectable items for presentation in a navigation menu. Note that a
navigation list always starts with a label element that defines the
label for the list.
The spec tells us that this list is (only?) for
Yes it seems but:
Navigation lists are intended to be used to define collections of
selectable items for presentation in a navigation menu. Note that a
navigation list always starts with a label element that defines the
label for the list.
The spec tells us that this list is (only?) for
Janos Hardi wrote:
but the starting point was that Chris
wanted a Hx element semantically connected with a list (with valid
xhtml code).
I understand, but I'd argue that your solution with LABEL is no more
semantically connected than the original one without, as LABEL is
expected to point
Return Receipt
Your document: RE: [WSG] Page Check:
www.qm-consulting.co.uk/test/indextest
Okay I retreat :)
Perhaps we can use one of the followings:
h1 id=stuff-list-titleHeading for stuff list/h1
ul id=stuff-list
li id=stuff1stuff No.1/li
..
/ul
or:
dl id=stuff-list
dt id=stuff-termStuff category/term/dt
dd id=stuff1Stuff No.1/dd
/dl
I think now the closest solution is using the
Patrick H. Lauke said:
Janos Hardi wrote:
...a Hx element semantically connected with a list
LABEL is expected to point to a form control, not a list. It may
validate in terms of syntax, but in terms of logic it doesn't make
sense...
Unfortunately HTML validators do contain errors. Allowing
Assuming Terrence meant to send the message below to the list, and not
just me. And in response: yes, I've heard something along those lines as
well (JAWS recognising changes to DOM initiated by user interaction).
Damn, I need to get myself another copy of JAWS (used to have 4.01 at
work many
Hi,
I suppose Chris referred to the machine readable code - In this case
I'd use your
= div
- header
* list
etc.
solution.
Cheers,
Janos
2005/11/6, Terrence Wood [EMAIL PROTECTED]:
Patrick H. Lauke said:
Janos Hardi wrote:
...a Hx element semantically connected with a list
LABEL is
Return Receipt
Your RE: [WSG] Page Check: www.qm-consulting.co.uk/test/indextest
document
:
Hi standardistas,
Ive had a problem with onfocus and onblur where
Firefox is calling onblur before onfocus when clicking on an input element.
This is a bug (https://bugzilla.mozilla.org/show_bug.cgi?id=53118
) because it goes against the DOM2 Event handling spec.
The only way around
Focas, Grant wrote:
Anyone with Firefox 1.5 beta know if this issue is
fixed in that version?
Firefox 1.5rc1 still has the same faulty behaviour...how weird.
--
Patrick H. Lauke
__
re·dux (adj.): brought back; returned. used
You must Focas. Sorry, couldn't resist.
:P
Thanks for the heads-up.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Focas,
GrantSent: Monday, 7 November 2005 12:12 PMTo:
wsg@webstandardsgroup.orgSubject: [WSG] Firefox onblur and onfocus
event bubbling bug
Hi
Hi Richard,
Very good work! Very nice web site!
My suggestions:
1. The XHTML 1.0 recommendation states that both lang and xml:lang
attributes should be used when specifying the language of an element.
The value of the xml:lang attribute takes precedence.
2. The style attribute has been
John S. Britsios wrote:
Hi Richard,
Very good work! Very nice web site!
My suggestions:
1. The XHTML 1.0 recommendation states that both lang and xml:lang
attributes should be used when specifying the language of an element.
The value of the xml:lang attribute takes precedence.
assuming
26 matches
Mail list logo
