Skip to content

Commit eaced67

Browse files
committed
[cssom-view] Editorial: elementsFromPoint and scrollingElement have multiple implementations
1 parent d4c3279 commit eaced67

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

cssom-view/Overview.bs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -906,7 +906,7 @@ The <dfn method for=Document>elementFromPoint(<var>x</var>, <var>y</var>)</dfn>
906906
Note: The {{elementFromPoint()}} method does not necessarily return the top-most painted element. For
907907
instance, an element can be excluded from being a target for hit testing by using the 'pointer-events' CSS property.
908908

909-
<p class=atrisk>
909+
<p>
910910
The <dfn method for=Document>elementsFromPoint(<var>x</var>, <var>y</var>)</dfn> method must follow these steps:
911911

912912
1. Let <var>sequence</var> be a new empty sequence.
@@ -969,7 +969,7 @@ specification and therefore the exact details of
969969
are therefore too. Hit testing will hopefully be defined in a future
970970
revision of CSS or HTML.
971971

972-
<p class=atrisk>The <dfn attribute for=Document>scrollingElement</dfn> attribute, on getting, must run these steps:
972+
<p>The <dfn attribute for=Document>scrollingElement</dfn> attribute, on getting, must run these steps:
973973

974974
1. If the {{Document}} is in <a>quirks mode</a>, follow these substeps:
975975
1. If <a>the HTML <code>body</code> element</a> exists, and it is not <a>potentially scrollable</a>, return <a>the HTML <code>body</code> element</a> and abort these steps.

0 commit comments

Comments
 (0)