1. 05 Dec, 2019 2 commits
  2. 25 Nov, 2019 1 commit
  3. 18 Nov, 2019 1 commit
  4. 29 Oct, 2019 1 commit
  5. 25 Oct, 2019 1 commit
    • Ciure Andrei's avatar
      Backed out 8 changesets (bug 1561227) for causing... · 706c8943
      Ciure Andrei authored
      Backed out 8 changesets (bug 1561227) for causing browser_viewport_resizing_scrollbar.js to permafail CLOSED TREE
      
      Backed out changeset aa00b1b62ea7 (bug 1561227)
      Backed out changeset b22440a67078 (bug 1561227)
      Backed out changeset 4776cec83ae8 (bug 1561227)
      Backed out changeset ac88bbefb95f (bug 1561227)
      Backed out changeset aef3cfa2f539 (bug 1561227)
      Backed out changeset a3759e1a04e2 (bug 1561227)
      Backed out changeset cfcf79794049 (bug 1561227)
      Backed out changeset 97be65338edf (bug 1561227)
      
      --HG--
      rename : devtools/client/responsive/test/browser/browser_viewport_zoom_toggle.js => devtools/client/responsive/test/browser/browser_toggle_zoom.js
      706c8943
  6. 24 Oct, 2019 3 commits
    • Brad Werth's avatar
      Bug 1561227 Part 1: Make nsDocumentViewer send a new event before setting full... · bd10652c
      Brad Werth authored
      Bug 1561227 Part 1: Make nsDocumentViewer send a new event before setting full zoom levels on the pres contexts. r=emilio
      
      The PreFullZoomChange event gives listeners an opportunity to capture
      state before the viewport full zoom changes. Responsive Design Mode uses
      this to save and later restore the resolution of the RDM pane.
      
      Differential Revision: https://phabricator.services.mozilla.com/D48621
      
      --HG--
      extra : moz-landing-system : lando
      bd10652c
    • Csoregi Natalia's avatar
      Backed out 8 changesets (bug 1561227) for failures on... · a377414b
      Csoregi Natalia authored
      Backed out 8 changesets (bug 1561227) for failures on browser_viewport_resizing_scrollbar.js. CLOSED TREE
      
      Backed out changeset 8117cafb3a20 (bug 1561227)
      Backed out changeset 635534927ffc (bug 1561227)
      Backed out changeset 693b0dd88f2b (bug 1561227)
      Backed out changeset 257bc09f49af (bug 1561227)
      Backed out changeset 1b63d555c6c1 (bug 1561227)
      Backed out changeset 677da957ddcb (bug 1561227)
      Backed out changeset f8b8e593316f (bug 1561227)
      Backed out changeset 849e1cf51a8f (bug 1561227)
      
      --HG--
      rename : devtools/client/responsive/test/browser/browser_viewport_zoom_toggle.js => devtools/client/responsive/test/browser/browser_toggle_zoom.js
      a377414b
    • Brad Werth's avatar
      Bug 1561227 Part 1: Make nsDocumentViewer send a new event before setting full... · 5338c8ac
      Brad Werth authored
      Bug 1561227 Part 1: Make nsDocumentViewer send a new event before setting full zoom levels on the pres contexts. r=emilio
      
      The PreFullZoomChange event gives listeners an opportunity to capture
      state before the viewport full zoom changes. Responsive Design Mode uses
      this to save and later restore the resolution of the RDM pane.
      
      Differential Revision: https://phabricator.services.mozilla.com/D48621
      
      --HG--
      extra : moz-landing-system : lando
      5338c8ac
  7. 25 Oct, 2019 1 commit
  8. 12 Oct, 2019 1 commit
  9. 25 Sep, 2019 1 commit
    • Emilio Cobos Álvarez's avatar
      Bug 1583534 - Further simplify PresShell::ResizeReflow. r=botond · 848d89d6
      Emilio Cobos Álvarez authored
      In particular, not let ResizeReflow take the old and new size. Most of the
      callers pass dummy values anyway.
      
      Instead, use the old size of the layout viewport. This ensures we fire resize
      events only if the layout viewport actually changes.
      
      This is important because the first resize of the mobile viewport manager
      after a navigation has an "old size" of 0x0, even though the layout viewport
      is initialized on presshell initialization to the right size.
      
      Thus, we fire resize events unnecessarily in that case, which is the root cause
      for bug 1528052.
      
      To do this, we need to shuffle a bit of code in nsDocumentViewer that deals with
      delayed resizes, to set the visible area _and_ invalidate layout, rather than
      setting the visible area and _then_ relying on doing a resize reflow.
      
      Further cleanup is possible, though not required for my android resizing fix, so
      will do separately.
      
      Differential Revision: https://phabricator.services.mozilla.com/D46944
      
      --HG--
      extra : moz-landing-system : lando
      848d89d6
  10. 26 Aug, 2019 1 commit
  11. 15 Aug, 2019 1 commit
  12. 09 Aug, 2019 1 commit
  13. 08 Aug, 2019 1 commit
  14. 02 Aug, 2019 4 commits
  15. 29 Jul, 2019 1 commit
    • Timothy Nikkel's avatar
      Bug 1565922. When the document viewer loses it prescontext pointer we need to... · 674fb7f2
      Timothy Nikkel authored
      Bug 1565922. When the document viewer loses it prescontext pointer we need to make sure that any potential subdocument display items get rebuilt. r=mattwoodrow
      
      If the subdocument display item gets created when the subdocument doesn't have a root frame it'll be based on the subdocument frame in the parent document. This means that the prescontext pointer on the document viewer of the subdocument can go away without the subdocument display item getting any kind of invalidation. So we make sure the subdocument display item gets rebuilt if that happens. The reason the prescontext pointer is important is that is what nsSubDocumentFrame::GetSubdocumentPresShellForPainting uses (via nsDocShell::GetPresShell) to get the subdocument presshell. So it will fail to get a presshell and RetainedDisplayListBuilder::IncrementSubDocPresShellPaintCount will crash.
      
      Differential Revision: https://phabricator.services.mozilla.com/D39310
      
      --HG--
      extra : moz-landing-system : lando
      674fb7f2
  16. 26 Jul, 2019 1 commit
  17. 23 Jul, 2019 1 commit
    • Ciure Andrei's avatar
      Backed out 10 changesets (bug 1523638) for causing high frequency Android 7.0... · c0756f33
      Ciure Andrei authored
      Backed out 10 changesets (bug 1523638) for causing high frequency Android 7.0 mochitests failures CLOSED TREE
      
      Backed out changeset 644ceb2fe568 (bug 1523638)
      Backed out changeset 27647ee7a927 (bug 1523638)
      Backed out changeset 96f1ccb95570 (bug 1523638)
      Backed out changeset b60a17ea716a (bug 1523638)
      Backed out changeset 507e63186c5f (bug 1523638)
      Backed out changeset 33255408ca61 (bug 1523638)
      Backed out changeset d97b2d223616 (bug 1523638)
      Backed out changeset eba2a0514cde (bug 1523638)
      Backed out changeset d7065174c5c4 (bug 1523638)
      Backed out changeset c21b361e175d (bug 1523638)
      c0756f33
  18. 18 Jul, 2019 1 commit
  19. 06 Jul, 2019 1 commit
  20. 09 Jul, 2019 3 commits
  21. 16 Jul, 2019 1 commit
  22. 09 Jul, 2019 2 commits
  23. 16 Jul, 2019 2 commits
  24. 24 Jun, 2019 1 commit
  25. 11 Jun, 2019 1 commit
  26. 04 Jun, 2019 1 commit
  27. 03 Jun, 2019 2 commits
  28. 30 May, 2019 1 commit
  29. 29 May, 2019 1 commit