- From: Daniel Beardsmore <public@telcontar.net>
- Date: Sat, 24 Feb 2007 02:35:59 +0000
- To: www-style@w3.org
Andrew Fedoniouk wrote:
>
> ----- Original Message -----
> From: "Daniel Beardsmore" <public@telcontar.net>
> To: <www-style@w3.org>
> Sent: Thursday, February 22, 2007 8:15 PM
> Subject: Wrapping delimited lists, fluid rows
>
>
> |
> | I won't dump my entire backlog of ideas here in one go, but here's something
> | that's troubled me without solution: imagine a list with a visual delimeter
> set
> | to display horizontally:
> |
> | ul.menu li { display: inline }
> | ul.menu li:after { content: " | " }
> | ul.menu li:last-child:after { content: none }
> |
> | A given list might look like:
> |
> | Foo | Bar | Baz
> |
> | But if this list wraps onto a new line, you'll see a problem:
> |
> | Foo | Bar | Baz | Iddly | Diddly | We've | Run | Out |
> | of | Names | For | This | List
> |
> | The last item on the first row doesn't get its delimited removed.
> |
> | I was thinking, can't we have a way to select :last-on-line and
> :first-on-line?
> |
> | So then we can stipulate:
> |
> | ul.menu li:last-on-line:after { content: none }
> |
>
> ....
>
> Rules like
>
> ul.menu li:after { content: " | " }
> ul.menu li:last-on-line:after { content: none }
>
> effectively create oscillation condition in the layout algorithm.
Right, it's nice to be told why things can't possibly ever conceivably work, but
how CAN it be made to work? How CAN we prevent undesirable glitches like this,
and go on to handle fluid grid rows?
I don't care what the CSS looks like -- you must realise that precise CSS is not
the issue, but achieving the presentation goal is.
Received on Saturday, 24 February 2007 02:36:52 UTC