W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2011

Fwd: Re: HTML5 alert ! Please read.

From: Richard Ishida <ishida@w3.org>
Date: Fri, 22 Jul 2011 17:57:26 +0100
Message-ID: <4E29ABF6.5030606@w3.org>
To: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
[forwarding to public list so that tracker can catch it]

Date: 	Sun, 17 Jul 2011 17:32:46 +0300
From: 	Aharon (Vladimir) Lanin <aharon@google.com>

ISSUE-35(New attribute: ubi)
I had left http://www.w3.org/Bugs/Public/show_bug.cgi?id=10807 open only
because I was not 100% sure that it was a good idea that the <output>
element was also defined to have isolation by default. But I never did
make up my mind that it was a bad idea, so I have no intention to make a
Last Call about it. Just forget about this.

ISSUE-36(New dir attribute value: auto, and a new attribute:
autodirmethod) <http://www.w3.org/International/track/issues/36>
Both http://www.w3.org/Bugs/Public/show_bug.cgi?id=10808 and
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11734 were fixed and are
closed. The issue should be closed.

ISSUE-43 (Block-display elements should act as UBA paragraph breaks)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11829* is important and is
still awaiting action by the editor.*

ISSUE-49(Option element should support text-align CSS property and be
displayed accordingly both in the dropdown and after being chosen)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10820 was a mistake on my
part that should never have been filed (see

why). The current HTML spec says "User agents are expected to render the
labels in a select in such a manner that any alignment remains
consistent whether the label is being displayed as part of the page or
in a menu control", which is fine. So, just forget about this.

ISSUE-52(When an input value is remembered, its direction should be
remembered too) <http://www.w3.org/International/track/issues/52>
In the discussion in
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10823, I agreed that the
requirement can not be normative, given that the spec really does not
spec anything about form control state persistence. However, the editor
agreed to add a note specifically allowing persisting and restoring the
direction: "If the entry is an entry with persisted user state, the user
agent may update aspects of the document and its rendering, for instance
the scroll position or values of form fields, that it had previously
recorded. This can even include updating the dir attribute of textarea
elements or input elements whose type attribute is in either the Text
state or the Search state, if the persisted state includes the
directionality of user input in such controls." I then asked that the
note clarify the motivation for doing so, "Persisting and using in this
manner the directionality of user input values will prevent displaying
the values incorrectly on history traversal when the user had originally
entered the values with an explicit, non-default directionality". *The
editor has yet to address this. *However, this is not very important.

ISSUE-53(List item marker display and position)
The CSS3 Lists Module still appears to be in flux. However, if I
understand correctly, the current thinking there is that
list-style-position:outside (the default) will mean that the marker's
position is determined by the direction of the list element, not the
list item. This is what we wanted (except that we wanted CSS to provide
control over that, and as far as I can see that disappeared over the
last six weeks, but that has nothing to do with HTML5). What we do want
from HTML5 is to make the default stylesheet say li {text-align:
match-parent;}, and I am using
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10824 for that purpose.

Received on Friday, 22 July 2011 16:57:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:01:49 UTC