- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Apr 2016 20:31:33 +0000
- To: public-secondscreen@w3.org
Reviewing this thread in light of our desire to publish a Candidate Recommendation for the Presentation API. Some background: I reached out a while ago to blink-dev@ and got feedback that indeed, the lang= does influence font selection when rendering. [1] It sounds like there are two distinct issues that we may want to address with specification language. 1. When a user requests presentation, the receiving browsing context SHOULD apply the language settings of the controlling browsing context, so that when the receiving user agent fetches resources for the presentation an appropriate HTTP `accept-language` header is set. (This is not a requirement, as the controller could also append a locale (BCP47) tag to the presentation URL passed to the server for language-specific resources.) 2. When a human-presentable string is passed from the controller to the receiver (or vice versa), the application MAY want to include a locale tag describing the preferred display language for the string to assist the browser with font selection. The page would be responsible for taking this locale and setting the lang= tag on the appropriate element rendering the string. In the scope of the current Presentation API, I believe item 1 would be included as guidance for implementors and 2 as guidance for authors. I can craft a PR along these lines. Both 1 and 2 would certainly be features that we could include in a forthcoming presentation control protocol. [1] https://groups.google.com/a/chromium.org/d/msg/blink-dev/7O6NPCuVWlo/1CwqmrQ4AQAJ -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/218#issuecomment-211564494 using your GitHub account
Received on Monday, 18 April 2016 20:31:34 UTC