ISSUE-156: Web Notifications: Directionality of a Notification
Web Notifications: Directionality of a Notification
- State:
- CLOSED
- Product:
- notifications
- Raised by:
- Richard Ishida
- Opened on:
- 2012-04-12
- Description:
- 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. - Related Actions Items:
- No related actions
- Related emails:
- Review of tracker issues for best practices (Part V) (from addison@lab126.com on 2015-04-09)
- Fwd: I18N-ISSUE-156: Web Notifications: Directionality of a Notification (from ishida@w3.org on 2012-04-12)
- I18N-ISSUE-156: Web Notifications: Directionality of a Notification [.Adhoc-WebApps] (from sysbot+tracker@w3.org on 2012-04-12)
Related notes:
No additional notes.
Display change log
