This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10810 - i18n comment 5 : U+2028 and U+2029 in textarea and pre elements
Summary: i18n comment 5 : U+2028 and U+2029 in textarea and pre elements
Status: CLOSED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-29 12:34 UTC by i18n bidi group
Modified: 2011-01-22 20:15 UTC (History)
8 users (show)

See Also:


Attachments

Description i18n bidi group 2010-09-29 12:34:39 UTC
Comment from the i18n review of:
http://dev.w3.org/html5/spec/

Comment 5
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/#newline-as-separator [http://www.w3.org/International/docs/html-bidi-requirements/#newline-as-separator]
. Here is the proposal made there:

In elements where line breaks are not collapsed, e.g. <textarea> and elements with white-space:pre|pre-line|pre-wrap, the LINE SEPARATOR (U+2028) and PARAGRAPH SEPARATOR (U+2029) characters should also break lines. PARAGRAPH SEPARATOR characters in these elements should constitute UBA paragraph breaks, while LINE SEPARATOR characters should constitute UBA whitespace.

When PARAGRAPH SEPARATOR introduces a UBA paragraph break, the base direction of the new UBA paragraph will be determined by the computed direction of the nearest ancestor element whose bidi properties require its contents to be in a separate UBA paragraph (or sequence of paragraphs), e.g. a block element or an element directionally isolated by the ubi attribute (which is being proposed in a separate bug). Furthermore, for every element on the path in between that results in the creation of an embedding or override level, e.g. a <bdo> element or any element with a dir attribute or a value other than "normal" for the unicode-bidi CSS property, the correspondeng embedding or override level is re-introduced at the start of the new UBA paragraph (to be closed at the end of the element or the UBA paragraph, whichever comes first).
Comment 1 Maciej Stachowiak 2010-09-29 16:03:25 UTC
Shouldn't this be defined in CSS instead of HTML, at least the part that ties behavior to specific white-space values?
Comment 2 Ian 'Hixie' Hickson 2010-10-12 06:08:30 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Seems to me that this is either a problem for the presentation layer above HTML (i.e. the CSS specifications) or the character set layer under HTML (i.e. the Unicode specification). What part of HTML would need changing otherwise?

Also, if this _is_ something that should be done at the HTML level, what problem does this solve? Are implementations on board with this?