Skip to content
Snippets Groups Projects
  1. Jan 15, 2024
  2. Jan 12, 2024
  3. Jan 15, 2024
  4. Jan 05, 2024
  5. Jan 15, 2024
  6. Dec 13, 2023
  7. Jan 11, 2024
  8. Jan 10, 2024
  9. Jan 11, 2024
  10. Jan 10, 2024
  11. Dec 20, 2023
    • James Teh's avatar
      Bug 1834718: Don't process a duplicate DocAccessible::ContentRemoved call for... · 2489f004
      James Teh authored
      Bug 1834718: Don't process a duplicate DocAccessible::ContentRemoved call for a DOM node we've already processed. r=morgan, a=dmeehan
      
      ContentRemoved recursively walks both AllChildrenIterator and direct DOM children.
      In addition, we might get duplicate notifications from DOM and layout, plus PruneOrInsertSubtree might do a recursive walk and it too calls ContentRemoved.
      To avoid this duplicate processing, keep a set of removed DOM nodes on the DocAccessible which we clear after mutation events are processed.
      
      Differential Revision: https://phabricator.services.mozilla.com/D196707
      2489f004
  12. Dec 31, 2023
  13. Jan 10, 2024
  14. Jan 09, 2024
Loading