- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Sep 2010 16:19:53 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10815
Maciej Stachowiak <mjs@apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjs@apple.com
--- Comment #1 from Maciej Stachowiak <mjs@apple.com> 2010-09-29 16:19:53 UTC ---
It's awkward to implement special cases where a computed CSS property value on
particular elements has other side effects. It's not possible to express this
in a stylesheet for instance, it would require hardcoded special cases.
It would also be particularly strange for the value of a CSS property to
implicitly change the value of a markup attribute, so this surely should not
create a literal "ubi" attribute, just have the same effect.
Since block-level elements with display: block already act as paragraphs, they
already essentially have the effect of bidi-isolate. Perhaps one possible way
to handle this is to give blocks recommended default rendering like this:
div {
display: block;
unicode-bidi: isolate;
}
This would preserve bidi isolation if the element's display type is changed to
inline, unless the author takes further steps to override unicode-bidi. It
would have the additional side effect of leaving isolation enabled for display
types other than "inline" or "block". I am not sure offhand whether or not that
is desirable.
I fear that this may be confusing to authors in any case, though. I think there
is an expectation that <div style="display: inline"></div> renders exactly
equivalent to <span>, under default styling. Perhaps this should be limited to
list items, as that is the primary use case presented.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.
Received on Wednesday, 29 September 2010 16:19:55 UTC