W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 Feb 2011 16:54:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PpkeZ-0004n6-Qo@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11829

--- Comment #3 from KangHao Lu <kennyluck@w3.org> 2011-02-16 16:54:59 UTC ---
(In reply to comment #2)
> If a browser _does_ implement CSS and unicode-bidi, then it is
> already required to put in the UA style sheet the rules in the spec, because if
> it doesn't then it will violate the other parts of the spec that says how these
> bidi features work, as far as I can tell.

Let me try to pull the bits here. I am probably missing something so any help
is appreciated.

3.2.3.5 The dir attribute

The effect of this attribute is primarily on the presentation layer. For
example, the rendering section in this specification defines a mapping from
this attribute to the CSS 'direction' and 'unicode-bidi' properties, and CSS
defines rendering in terms of those properties.

3.2.6 doesn't mention anything about CSS and extra characters imposed by having
the dir attribute, etc.

4.6.22 The bdi element

This is the place where the 'unicode-bidi: isolate' algorithm is specified.

== Problem ==

In HTML4, there was a sentence:

[[
When a block element that does not have a dir attribute is transformed to the
style of an inline element by a style sheet, the resulting presentation should
be equivalent, in terms of bidirectional formatting, to the formatting obtained
by explicitly adding a dir attribute (assigned the inherited value) to the
transformed element.
]]

This was not implementable and later on an modified approach was taken (giving
several elements 'unicode-bidi: embed' as default) by Mozilla (see the bug in
comment #1).

They are changed to 'unicode-bidi: isolate' in the current draft. While rules
for the dir attribute and the bdi elements are more or less implied by the
sentences listed above, as far as I can tell, the current spec does not have a
sentence corresponding to 'li { unicode-bidi: isolate; }' and similar rules.

Is it possible to say, *if* the browser supports CSS and 'unicode-bidi', here's
a normative section of CSS rules? Or perhaps you just want to write a sentence
that unambiguously implies these rules.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 16 February 2011 16:55:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 February 2011 16:55:01 GMT