- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 May 2016 18:49:02 +0000
- To: public-secondscreen@w3.org
@sicking Jonas, I wanted to touch on the second resolution, which you suggested in the minutes of the F2F. * Are you suggesting that the Presentation API spec recommend that the receiving user agent append the string "tv" to `navigator.userAgent` if it was rendering on a television? * How would we define "television"? Is the criterion typical viewing distance or pixel density? * If rendering in 1-UA mode, would the user agent provide a different value for `navigator.userAgent` in the receiving browsing context vs the controlling browsing context? In response, were you thinking the Web developer would query for "tv" in `navigator.userAgent` and provide different styling, or would the receiving user agent answer an existing CSS Media Query in a specific way? Perhaps a pull request would clarify what you are thinking of for the Presentation API spec. -- One thought I had was to use the `resolution` media query [1] that selects on pixel density. Here are some resolutions for a range of TV sizes you can buy today. Most other screens (laptops, mobiles) seem to fall into 40-140 ppcm [1] so there's not a great deal of overlap. ``` 102 cm diagonal (40") @ 2160p: 43 pixels per cm 191 cm (75") @ 1080p: 12 ppcm ``` [1] https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#resolution [2] http://dpi.lv/ -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/99#issuecomment-221960252 using your GitHub account
Received on Thursday, 26 May 2016 18:49:04 UTC