- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Sep 2010 12:43:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10814
Summary: i18n comment 9 : block-display elements should act as
UBA paragraph breaks
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: public-i18n-bidi@w3.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org, public-i18n-bidi@w3.org
Comment from the i18n review of:
http://dev.w3.org/html5/spec/
Comment 9
At http://www.w3.org/International/reviews/html5-bidi/
Editorial/substantive: S
Tracked by: AL
Location in reviewed document:
undefined [http://dev.w3.org/html5/spec/spec.html#contents]
Comment:This is a part of the proposals made by the "Additional Requirements
for Bidi in HTML" W3C First Public Working Draft. For a full description of the
use cases, please see
http://www.w3.org/International/docs/html-bidi-requirements/#blocks-as-separators
[http://www.w3.org/International/docs/html-bidi-requirements/#blocks-as-separators]
. Here is the proposal made there:
An element with display:block, except when it has been taken out of document
flow with CSS such as float or position:absolute, but regardless of whether it
is a block element or inline element, should be specified as introducing a UBA
paragraph break between the content preceding and following it. This does not
present a problem for backward compatibility because there has been no browser
interoperability in this respect.
If the display:block element has display:inline ancestors that have bidi
properties (e.g. the dir attribute or the <bdo> element), these bidi properties
should be applied to the anonymous block boxes created for these ancestors, in
accordince with CSS specs for anonymous block boxes.
--
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, 29 September 2010 12:43:12 UTC