W3C home > Mailing lists > Public > public-i18n-bidi@w3.org > October to December 2011

directionality of a notification

From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Date: Fri, 23 Dec 2011 02:21:02 +0800
Message-ID: <4EF3750E.4000802@csail.mit.edu>
To: Web Notification WG <public-web-notification@w3.org>
CC: ML publc-i18n-bidi <public-i18n-bidi@w3.org>
I have three pieces of feedback regarding the Directionality section[1]

1. When the dir attribute of a notification is in "inheriting
state"(i.e. dir="auto" currently) and the notification is called from a
Web Worker, the resulting directionality is now always 'ltr'. Is that
intentional and desirable? If not, I suppose we use the directionality
of the root element (or the body element, whatever is better), if
exists, of the calling script's document (or the script's document's
browsing context's active document, whatever is better) as the inherited

2. The "auto" value conflicts semantically with the @dir content
attribute in HTML, which uses the first strong algorithm. I propose we
use the empty string to identify the "inheriting state", and potentially
a new "auto" value to identify the "first strong state". In this state,
the UA would apply the first strong algorithm to the content of the
notification to determine the directionality used.

3. What should be the default value of Notification's dir value? My
guess is the "inheriting state" instead of the "first strong state" but
the bidi folks would know better.

== editorial comments ==
1. Currently it is not close to straightforward to find this mailing
list from the spec.
2. Some of the links ("5.1", "5.2" and "5.3") in table of contents are
3. The style used in this document makes wonder if I am looking at
something old.



Received on Thursday, 22 December 2011 18:21:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:24:39 UTC