From 1d6b374fdf97dbb42304085214767560bf0b4e5e Mon Sep 17 00:00:00 2001 From: Dominic Farolino Date: Fri, 20 Dec 2024 13:55:07 -0500 Subject: [PATCH] Some clean-ups, clarification, and wording --- source | 59 ++++++++++++++++++++++++++++++++++++---------------------- 1 file changed, 37 insertions(+), 22 deletions(-) diff --git a/source b/source index 5063398d273..45f4e86d807 100644 --- a/source +++ b/source @@ -80128,32 +80128,35 @@ dictionary ToggleEventInit : EventInit {

  • Let container be the reading flow container associated with owner.

    • -

  • Let items be the rendering-defined sibling reading flow of - container.

    • +

  • Let items be container's rendering-defined sibling reading + flow.

    • + +

  • Assert: items is a list of reading flow items.

  • For each item of items:

      -

    1. Assert: item is a reading flow item.

      2. -

    2. While item is not container:

      +
      1. -

        If item's associated focus navigation owner is owner:

        +

        If scope contains item:

          -

        1. If output does not contain - item, append item to - output.

          2. +
        2. +

          If output does not contain + item, then append item to + output.

          + +

          Different items can share the same ancestor in + scope; only add it to output the first time it is encountered.

          +

        3. Break.

        - -

        Different items can have the same inclusive - ancestor. Only add to output if it is not already in the reading - flow order.

      2. Set item to the parent element of item within the flat @@ -80162,22 +80165,34 @@ dictionary ToggleEventInit : EventInit {

      -

      The rendering-defined sibling reading flow of container - includes descendants of this reading flow container - that might not be in scope. For example, if a direct child of container has - CSS 'display: contents' and its nested children are included in items. Some elements in - items will have the container while others will have 'display: contents' child - as its associated focus navigation owner. This step traverses the ancestors of item within the flat tree to make sure - we only include an element in the reading flow order if it is in scope.

      +
      +

      items can include descendants of + container that are not in scope. For example, when a direct child of + container has display: contents:

      + +
        +

      • The display: contents child will be in scope, but not + in items.

        • + +

      • The display: contents's own children will not be in scope (their + associated focus navigation owner is their parent), but can be in + items.

        • +
      + +

      This step includes in output the first inclusive ancestor of each + item that is also in scope. The result is that output is just + scope, but in reading flow order, as established by items.

      +

    3. For each child of owner element's children, in tree order:

      +
        -

      1. If child's associated focus navigation owner is owner - and output does not contain child, +

      2. If scope contains child and + output does not contain child, then append child to output.