Geoff Pack wrote:
As for lists, the pipe separated menu list is perfectly clear to most
people. What is missing is a clean way to mark it up with HTML. You
could use an unordered list, styled inline, but that is overkill in many
cases, and not an useable if you want the list to be inline when
On 12/11/05, Geoff Pack [EMAIL PROTECTED] wrote:
Yes, but there are different degrees of ugly. I care because I occasionally
look at my pages on a PDA, and inline list work better for some things (esp.
navs) than bulleted lists. They are more compact and require less scrolling.
But you're
Geoff Pack wrote:
Joshua Street wrote:
Can you possibly ditch the un-semantic pipe separators (|)
Are the pipe separators really un-semantic? They have a long history
of being used in navigation menus, and definitely have meaning. They
may be redundant here given that the grandparent marked
And what does a list really look like?
Which of the following is more correct:
My favourite fruits are watermelon, apples and bananas.
My favourite fruits are:
* watermelon
* apples
* bananas
Answer: neither. They are both lists and both mean the same.
what a list
Geoff Pack wrote:
And what does a list really look like? Which of the following is more
correct:
My favourite fruits are watermelon, apples and bananas.
My favourite fruits are:
* watermelon
* apples
* bananas
Answer: neither. They are both lists and both mean the same.
I think
Geoff Pack wrote:
Are the pipe separators really un-semantic? They have a long history of being
used in navigation menus, and definitely have meaning.
Asterisks have a long history of being used to denote required form
fields...but that doesn't make them semantic either. Just like the pipe
On 12/11/05, Geoff Pack [EMAIL PROTECTED] wrote:
Joshua Street wrote:
Can you possibly ditch the un-semantic pipe separators (|) and just
use border-right:1px solid #000; on the li elements? That would
probably help...
Are the pipe separators really un-semantic? They have a long
Christian Montoya wrote:
If you heard what pipe separators sound like in a screen reader, you
wouldn't think they were semantic. Just because they have a long
history doesn't make them machine-readable.
Well, I have heard what they sound like when Opera reads them out, which is no
biggie.
Why are you using pipes in the first place? Why is a li with
border-right : 1px solid black; styled on it and spaced out with margins
and padding not sufficient? This smacks of using nbsp; for layout.
Samuel
Geoff Pack wrote:
Christian Montoya wrote:
If you heard what pipe separators
On 12/11/05, Geoff Pack [EMAIL PROTECTED] wrote:
As for lists, the pipe separated menu list is perfectly clear to most people.
What is missing is a clean way to mark it up with HTML. You could use an
unordered list, styled inline, but that is overkill in many cases, and not an
useable if
We're arguing about the semantics of the word semantics. New record for WSG. ;-)
On 12/12/05, Geoff Pack [EMAIL PROTECTED] wrote:
Christian Montoya wrote:
If you heard what pipe separators sound like in a screen reader, you
wouldn't think they were semantic. Just because they have a long
Samuel Richardson wrote:
Why are you using pipes in the first place? Why is a li with
border-right : 1px solid black; styled on it and spaced out
with margins
and padding not sufficient? This smacks of using nbsp; for layout.
Why? because it's more concise, uses less bandwidth, and
I thought this was a mailing list about web standards and semantics.
pitem 1 | item 2 | item 3/p
Doesn't mean anything semantically, it's telling me that their is a
paragraph with a bunch items in it and something called a pipe between
them, I don't know what a pipe is because I'm a blind
Christian Montoya wrote:
...
- I don't care how a page looks with CSS off, as long as a list really
looks like a list
And what does a list really look like? Which of the following is more correct:
My favourite fruits are watermelon, apples and bananas.
My favourite fruits are:
*
14 matches
Mail list logo
