Fwd: I18N-ISSUE-156: Web Notifications: Directionality of a Notification


Please follow the threads indicated below and let us know if you have 
any comments on Aharon's proposal for resolution.


Richard Ishida
Internationalization Activity Lead
W3C (World Wide Web Consortium)


-------- Original Message --------
Subject: I18N-ISSUE-156: Web Notifications: Directionality of a 
Notification [.Adhoc-WebApps]
Resent-Date: Thu, 12 Apr 2012 11:46:02 +0000
Resent-From: public-i18n-core@w3.org
Date: Thu, 12 Apr 2012 11:45:57 +0000
From: Internationalization Core Working Group Issue Tracker 
Reply-To: Internationalization Core Working Group <public-i18n-core@w3.org>
To: public-i18n-core@w3.org

I18N-ISSUE-156: Web Notifications: Directionality of a Notification 


Raised by: Richard Ishida
On product: .Adhoc-WebApps


>From Kang-Hao (Kenny) Lu:

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.

Received on Thursday, 12 April 2012 11:56:12 UTC