@@ -42,7 +42,9 @@ spec:html;
4242 type:dfn; for:/; text:browsing context
4343 type:dfn; for:/; text:joint session history
4444spec:infra; type:dfn; text:user agent
45- spec:selectors-4; type:selector; text::fullscreen
45+ spec:selectors-4; type:selector;
46+ text::fullscreen
47+ text::hover
4648</pre>
4749
4850<pre class=biblio>
@@ -1456,7 +1458,7 @@ Display Modes: the '@media/display-mode' media feature</h3>
14561458 [[FULLSCREEN|Fullscreen API]] .</summary>
14571459
14581460 The ''fullscreen'' value for '@media/display-mode' is not directly related
1459- to the CSS '':fullscreen'' pseudo-class.
1461+ to the CSS '':fullscreen'' [= pseudo-class=] .
14601462 The '':fullscreen'' pseudo-class matches an element
14611463 exclusively when that element is put into the fullscreen element stack.
14621464 However, a side effect of calling the {{requestFullscreen()}} method
@@ -1471,7 +1473,7 @@ Display Modes: the '@media/display-mode' media feature</h3>
14711473 to put a web application into fullscreen
14721474 without invoking the [[FULLSCREEN|Fullscreen API]] .
14731475 When this happens,
1474- the '':fullscreen'' pseudo class will not match,
1476+ the '':fullscreen'' pseudo- class will not match,
14751477 but ''(display-mode: fullscreen)'' will match.
14761478 This is exemplified in CSS code below:
14771479
@@ -2320,7 +2322,7 @@ Hover Capability: the '@media/hover' feature</h3>
23202322 as the primary pointing device (the touch screen) does not allow the user to hover.
23212323
23222324 However, despite this, the optional mouse does allow users to hover.
2323- Authors should therefore be careful not to assume that the ':hover' pseudo class
2325+ Authors should therefore be careful not to assume that the '' :hover'' [= pseudo- class=]
23242326 will never match on a device where 'hover:none' is true,
23252327 but they should design layouts that do not depend on hovering to be fully usable.
23262328 </div>
0 commit comments