W3C home > Mailing lists > Public > www-style@w3.org > October 2004

Re: Box model: min-margin and max-margin, max-padding and min-padding

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Sat, 2 Oct 2004 19:52:28 -0700
Message-ID: <002a01c4a8f4$054d38d0$0201a8c0@ATHLON>
To: <www-style@w3.org>

| Kiarra:
| Wouldn't it be better if there could be a way to tell text browsers and
screen readers what to display first?

Example as an answer:

<body>
<div id=n1>....</div>
<div id=n2>....</div>
......
<div id=n10000 style="display-order:first">....</div>
</body>

Huh?

Andrew Fedoniouk.
http://terrainformatica.com



----- Original Message -----
From: "Kiarra Parker" <excellencepersonified@hotmail.com>
To: <www-style@w3.org>
Sent: Saturday, October 02, 2004 7:39 PM
Subject: Re: Box model: min-margin and max-margin, max-padding and
min-padding


|
| Andrew Fedoniouk wrote:
|
| >Hi, Brian,
| >
| >| ... Opera is a notable exception.
| >
| >Try to open http://terrainformatica.com/w3/block-inline.htm then.
| >I wouldn't consider still this as a support of inline-block.
| >(no offence to Opera developers, in fact - my deepest and honest respect
to
| >them)
| >
| >BTW: flow: right-to-left/left-to-right
| >solves accessibility problem (what should go first in source: content or
| >sidebar).
| >
| <snip>
|
| Should it really matter what comes first in the source?  Wouldn't it be
better if there could be a way to tell text browsers and screen readers what
to display first? If the standards could exhort these devices to read
stylesheets that had the power to say what comes first, we wouldn't have to
worry about source ordering anymore, would we?  Or is there a greater goal
or purpose in it?
|
| Kiarra
|
|
Received on Sunday, 3 October 2004 02:53:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:34 GMT