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
  15. Jan 08, 2024
  16. Dec 12, 2023
  17. Jan 04, 2024
  18. Dec 11, 2023
  19. Sep 13, 2023
    • Andrew Osmond's avatar
      Bug 1852420 - Ensure surface and crop rect used in ImageBitmap are valid.... · 2557ef36
      Andrew Osmond authored
      Bug 1852420 - Ensure surface and crop rect used in ImageBitmap are valid. r=gfx-reviewers,lsalzman, a=dmeehan
      
      When ImageBitmap::PrepareForDrawTarget is called, we must ensure
      that the surface returned is acceptable to the given DrawTarget. If
      it is not, then we need to recreate the surface from mData. We must
      also ensure similar when we are creating a new ImageBitmap from
      another ImageBitmap, as we don't know in what context it may be
      used.
      
      Similarly, we need to ensure we produce DataSourceSurface compatible
      surfaces when we need to both crop and premultiply.
      
      Additionally, we now no longer clear mPictureRect or mAlphaType
      when we set mSurface with the cached, cropped data. Since we may
      need to clear the cached surface, we need to know the original crop
      rect and alpha.
      
      Differential Revision: https://phabricator.services.mozilla.com/D188056
      2557ef36
  20. Jan 05, 2024
  21. Jan 04, 2024
  22. Jan 03, 2024
    • Dana Keeler's avatar
      Bug 1870262 - a subdomain of any HSTS superdomain that asserts... · efc6f61c
      Dana Keeler authored
      Bug 1870262 - a subdomain of any HSTS superdomain that asserts includeSubdomains is HSTS (ESR115) r=jschanck, a=dmeehan
      
      
      Previously, the HSTS implementation would only consider the first superdomain
      that had any HSTS information and use the presence or absence of the
      includeSubdomains directive to determine if the subdomain was HSTS. However,
      the specification actually stipulates that if any superdomain that is HSTS
      asserts includeSubdomains, the subdomain is HSTS.
      
      Differential Revision: https://phabricator.services.mozilla.com/D197550
      efc6f61c
  23. Dec 12, 2023
  24. Nov 29, 2023
  25. Dec 12, 2023
  26. Jan 03, 2024
  27. Jan 02, 2024
  28. Jan 01, 2024
  29. Dec 11, 2023
  30. Dec 29, 2023
    • Mike Hommey's avatar
      Bug 1868998 - Mark custom-car jobs as running nowhere and not being cached.... · 2a137cc2
      Mike Hommey authored
      Bug 1868998 - Mark custom-car jobs as running nowhere and not being cached. r=taskgraph-reviewers,kshampur,jcristau a=release
      
      They are triggered via cron, so an empty run-on-projects should be the
      appropriate config.
      
      As they are not idempotent (they will pick the last from upstream on
      each run), they also shouldn't be cached.
      2a137cc2
Loading