From be0a03d1b13ecf96ea87680284a995973195fce4 Mon Sep 17 00:00:00 2001 From: Alice Boxhall Date: Tue, 8 Jan 2019 11:21:26 +1100 Subject: [PATCH] Clarify mouse pointer and event behaviour --- source | 56 +++++++++++++++++++++++++++++++------------------------- 1 file changed, 31 insertions(+), 25 deletions(-) diff --git a/source b/source index 5eb5bba4e28..84781e3ae4d 100644 --- a/source +++ b/source @@ -3199,6 +3199,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • The fire an event algorithm
  • The canceled flag
  • The dispatch algorithm
    • +
  • The concept of invoking an event listener
  • EventInit dictionary type
  • type attribute
  • target attribute
    • @@ -3209,6 +3210,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • isTrusted attribute
  • initEvent() method
  • add an event listener
    • +
  • event listener list
  • addEventListener() method
  • The remove an event listener and remove all event listeners algorithms
    • @@ -72272,26 +72274,36 @@ END:VCARD

    Inert subtrees

    This section does not define or create any content attribute - named "inert". This section merely defines an abstract concept of - inertness.

    + named "inert". This section merely defines an abstract concept of inertness. See inert for an explanation of + the attribute of the same name.

    A node (in particular elements and text nodes) can be marked as inert. When a node - is inert, then the user agent must act as if the node was absent for the purposes of - targeting user interaction events, may ignore the node for the purposes of text search user - interfaces (commonly known as "find in page"), and may prevent the user from selecting text in - that node. User agents should allow the user to override the restrictions on search and text - selection, however.

    + is inert, then:

    + + + +

    User agents should allow the user to override the restrictions on search and text selection, + however.

    For example, consider a page that consists of just a single inert - paragraph positioned in the middle of a body. If a user moves their pointing device - from the body over to the inert paragraph and clicks on the paragraph, - no mouseover event would be fired, and the mousemove and click events would - be fired on the body element rather than the paragraph.

    + button positioned in the middle of a body. If a user clicks on the + button, the click event would cause no event listeners on + button to be run, and the event would bubble up to the body element + regardless of any event listeners on the button.

    When a node is inert, it generally cannot be focused. Inert nodes that are commands will also get disabled.

    +

    User agents should show the default cursor when a user indicates an element in an inert subtree + using a pointing device.

    +

    While a browsing context container is marked as inert, its nested browsing context's active document, and all nodes in that Document, must be marked as inert.

    @@ -72324,19 +72336,13 @@ END:VCARD must mark that element and all its descendants as inert.

    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 disabled attribute - is probably more appropriate.

    + 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 might get frustrated if inert sections are not obviously inert. For + individual controls, the disabled attribute is probably + more appropriate.

    The inert IDL attribute must reflect the content attribute of the same name.