|
11 | 11 | rel=dcterms.rights>
|
12 | 12 | <meta content="CSS Device Adaptation" name=dcterms.title>
|
13 | 13 | <meta content=text name=dcterms.type>
|
14 |
| - <meta content=2013-05-30 name=dcterms.date> |
| 14 | + <meta content=2013-08-15 name=dcterms.date> |
15 | 15 | <meta content="Rune Lillesveen" name=dcterms.creator>
|
16 | 16 | <meta content="Øyvind Stenhaug" name=dcterms.creator>
|
17 | 17 | <meta content="Florian Rivoal" name=dcterms.creator>
|
|
30 | 30 |
|
31 | 31 | <h1>CSS Device Adaptation</h1>
|
32 | 32 |
|
33 |
| - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 30 May 2013</h2> |
| 33 | + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 15 August 2013</h2> |
34 | 34 |
|
35 | 35 | <dl>
|
36 | 36 | <dt>This version:
|
37 | 37 |
|
38 | 38 | <dd>$Date$ (editor's draft)
|
39 |
| - <!--<dd><a href="http://dev.w3.org/csswg/css-device-adapt/">http://www.w3.org/TR/2013/WD-css-device-adapt-20130530/</a></dd>--> |
| 39 | + <!--<dd><a href="http://dev.w3.org/csswg/css-device-adapt/">http://www.w3.org/TR/2013/WD-css-device-adapt-20130815/</a></dd>--> |
40 | 40 |
|
41 | 41 | <dt>Latest version:
|
42 | 42 |
|
@@ -1819,25 +1819,17 @@ <h4 class="no-num no-toc" id=the-width-and-height-properties>The <code
|
1819 | 1819 | title="device-width!!viewport META">device-width</code> and <code
|
1820 | 1820 | class=index id=device-height0
|
1821 | 1821 | title="device-height!!viewport META">device-height</code> translate to
|
1822 |
| - 100% |
| 1822 | + 100vw and 100vh respectively |
1823 | 1823 |
|
1824 | 1824 | <li>Other keywords and unknown values translate to 1px
|
1825 | 1825 | </ol>
|
1826 | 1826 |
|
1827 | 1827 | <p class=note>Some existing UA implementations use device dimensions in CSS
|
1828 | 1828 | pixels, and some use the window dimensions (CSS pixels) for device-width /
|
1829 |
| - device-height. Above, we translate to 100% which are the window |
| 1829 | + device-height. Above, we translate to 100vw / 100vh which are the window |
1830 | 1830 | dimensions. The rationale is that the device dimensions would not be what
|
1831 | 1831 | the author intended for UAs where the window is resizable or does not fill
|
1832 |
| - the screen of the device. The rationale for using 100% and not ‘<a |
1833 |
| - href="#auto" title="auto!!length">auto</a>’, is that ‘<a href="#auto" |
1834 |
| - title="auto!!length">auto</a>’ will be affected by a length in the other |
1835 |
| - dimension. That is, <code>@viewport { width: 100%; height: 500px }</code> |
1836 |
| - will resolve width to the window width while <code>@viewport { width: |
1837 |
| - auto; height: 500px }</code> will resolve width from height and the |
1838 |
| - aspect-ratio of the window. A consequence of using percentages instead of |
1839 |
| - device dimensions, is that one cannot use device-height for width or |
1840 |
| - device-width for height. |
| 1832 | + the screen of the device. |
1841 | 1833 |
|
1842 | 1834 | <div class=example>
|
1843 | 1835 | <p>This <code class=html>META</code> element:
|
@@ -2095,10 +2087,10 @@ <h3 class=no-num id=normative-references>Normative references</h3>
|
2095 | 2087 | <dt id=CSS3VAL>[CSS3VAL]
|
2096 | 2088 |
|
2097 | 2089 | <dd>Håkon Wium Lie; Tab Atkins; Elika J. Etemad. <a
|
2098 |
| - href="http://www.w3.org/TR/2013/CR-css3-values-20130404/"><cite>CSS |
2099 |
| - Values and Units Module Level 3.</cite></a> 4 April 2013. W3C Candidate |
| 2090 | + href="http://www.w3.org/TR/2013/CR-css3-values-20130730/"><cite>CSS |
| 2091 | + Values and Units Module Level 3.</cite></a> 30 July 2013. W3C Candidate |
2100 | 2092 | Recommendation. (Work in progress.) URL: <a
|
2101 |
| - href="http://www.w3.org/TR/2013/CR-css3-values-20130404/">http://www.w3.org/TR/2013/CR-css3-values-20130404/</a> |
| 2093 | + href="http://www.w3.org/TR/2013/CR-css3-values-20130730/">http://www.w3.org/TR/2013/CR-css3-values-20130730/</a> |
2102 | 2094 | </dd>
|
2103 | 2095 | <!---->
|
2104 | 2096 |
|
|
0 commit comments