At 2007.03.15-21:42(+0200), Simon Montagu wrote:
(snipping a lot since the
combination of top- and bottom- posting is getting very
Stephen Deach wrote:
I'm responding that I think that
is exactly what the existing CSS properties do (with the possible
exception of explicitly saying that this is an input field, dynamically
re-analyze it if the data changes, though most CSS properties can be
animated so most are dynamically applied).
1.) All paragraphs in CSS should map to display="block",
so each paragraph is
its own block (these may or may not be
nested in a parent block).
2.) For all block-level elements, if no 'unicode-bidi' property is
it defaults to "normal". This
effectively disables the setting of
'direction', since the Unicode bidi rules
are supposed to be applied.
I think you aren't taking into account the following paragraph in CSS2.1,
User agents that support bidirectional text must apply the Unicode
bidirectional algorithm to every sequence of inline boxes uninterrupted
by a forced line break or block boundary. This sequence forms the
"paragraph" unit in the bidirectional algorithm. The paragraph
embedding level is set according to the value of the 'direction' property
of the containing block rather than by the heuristic given in steps P2
and P3 of the Unicode algorithm.
Since the 'direction' property, references the 'unicode-bidi' property;
and 'direction's interpretation is dependent on 'unicode-bidi's; I assume
the above paragraph should be interpreted: "... according to the
values of the 'direction' and 'unidoce-bidi'
properties of the containing block ..."
I really think this is a question of asking CSS whether my reading of the
spec is what they meant and asking them to clarify the spec, rather than
add a new value to 'direction' which will then mess up other dependencies