From f3a8b83ef9c96fe3286f0df50d9b27161cb99d94 Mon Sep 17 00:00:00 2001
From: Alice Boxhall <aboxhall@chromium.org>
Date: Wed, 8 Aug 2018 15:44:27 +1000
Subject: [PATCH] Add advice to use default cursor

---
 source | 21 ++++++++++++++-------
 1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/source b/source
index 86b8f5903bb..9b11d54cc9d 100644
--- a/source
+++ b/source
@@ -72251,13 +72251,20 @@ END:VCARD</pre>
   <p w-nodev>When an element has an <code data-x="attr-inert">inert</code> attribute, the user agent
   must mark that element and all its descendants as <span>inert</span>.</p>
 
-  <p class="note">By default, there is no visual indication of a subtree being inert. Authors are
-  encouraged to clearly mark what parts of their document are active and which are inert, to avoid
-  user confusion. In particular, it is worth remembering that not all users can see all parts of a
-  page at once; for example, users of screen readers, users on small devices or with magnifiers, and
-  even users just using particularly small windows might not be able to see the active part of a
-  page and may get frustrated if inert sections are not obviously inert. For individual controls,
-  the <code data-x="attr-fe-disabled">disabled</code> attribute is probably more appropriate.</p>
+  <p class="note">By default, there is no persistent visual indication of a subtree being inert.
+  Since inert subtrees may not be the target of user interaction events,
+  including text selection,
+  user agents should show the default cursor when an the user indicates an element in an inert subtree
+  using a pointing device.
+  Authors are encouraged to clearly mark what parts of their document are active and which are inert,
+  to avoid user confusion.
+  In particular, it is worth remembering that not all users can see all parts of a page at once;
+  for example, users of screen readers, users on small devices or with magnifiers,
+  and even users just using particularly small windows
+  might not be able to see the active part of a page and may get frustrated
+  if inert sections are not obviously inert.
+  For individual controls, the <code data-x="attr-fe-disabled">disabled</code> attribute
+  is probably more appropriate.</p>
 
   <p>The <dfn data-x="dom-inert"><code>inert</code></dfn> IDL attribute must <span>reflect</span>
   the content attribute of the same name.</p>