Commits on Feb 8, 2023

1. Range APIs do not construct / move trees in tree order (observable by… …

   … custom elements)
   
   https://bugs.webkit.org/show_bug.cgi?id=188279
   
   Reviewed by Chris Dumez.
   
   In order to match the spec'ed upgrade order, create a nested custom element reaction stack
   which is used as a holding tank of upgrade reactions during Range::processContents.
   
   At the end, we traverse the document fragment top-down and re-enqueue each element to the real
   custom element reaction stack in the tree order.
   
   * LayoutTests/imported/w3c/web-platform-tests/custom-elements/range-and-constructors-expected.txt:
   * Source/WebCore/dom/CustomElementReactionQueue.cpp:
   (WebCore::CustomElementQueue::takeElements): Added.
   (WebCore::CustomElementReactionQueue::enqueueElementsOnAppropriateElementQueue): Added.
   (WebCore::CustomElementReactionStack::takeElements): Added.
   * Source/WebCore/dom/CustomElementReactionQueue.h:
   * Source/WebCore/dom/Range.cpp:
   (WebCore::Range::processContents):
   
   Canonical link: https://commits.webkit.org/259987@main

   

   rniwa committed Feb 8, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for fa5a06a
   • Browse repository at this point

   Copy the full SHA

   fa5a06a View commit details

   Browse the repository at this point in the history