- From: Internationalization Core Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Thu, 12 Apr 2012 11:45:57 +0000
- To: public-i18n-core@w3.org
I18N-ISSUE-156: Web Notifications: Directionality of a Notification [.Adhoc-WebApps] http://www.w3.org/International/track/issues/156 Raised by: Richard Ishida On product: .Adhoc-WebApps Thread: http://lists.w3.org/Archives/Public/public-web-notification/2011Dec/0000.html Thread: http://lists.w3.org/Archives/Public/public-web-notification/2012Feb/0000.html >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 directionality. 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:46:00 UTC