1. 30 May, 2020 1 commit
  2. 29 May, 2020 1 commit
  3. 15 May, 2020 3 commits
  4. 08 Apr, 2020 1 commit
  5. 27 Mar, 2020 2 commits
  6. 13 Mar, 2020 3 commits
  7. 22 Jan, 2020 13 commits
  8. 20 Jan, 2020 2 commits
    • Emilio Cobos Álvarez's avatar
      Bug 1609996 - Reorder some includes affected by the previous patches. r=froydnj · 256c124f
      Emilio Cobos Álvarez authored
      This was done by:
      
      This was done by applying:
      
      ```
      diff --git a/python/mozbuild/mozbuild/code-analysis/mach_commands.py b/python/mozbuild/mozbuild/code-analysis/mach_commands.py
      index 789affde7bbf..fe33c4c7d4d1 100644
      --- a/python/mozbuild/mozbuild/code-analysis/mach_commands.py
      +++ b/python/mozbuild/mozbuild/code-analysis/mach_commands.py
      @@ -2007,7 +2007,7 @@ class StaticAnalysis(MachCommandBase):
               from subprocess import Popen, PIPE, check_output, CalledProcessError
      
               diff_process = Popen(self._get_clang_format_diff_command(commit), stdout=PIPE)
      -        args = [sys.executable, clang_format_diff, "-p1", "-binary=%s" % clang_format]
      +        args = [sys.executable, clang_format_diff, "-p1", "-binary=%s" % clang_format, '-sort-includes']
      
               if not output_file:
                   args.append("-i")
      ```
      
      Then running `./mach clang-format -c <commit-hash>`
      
      Then undoing that patch.
      
      Then running check_spidermonkey...
      256c124f
    • Emilio Cobos Álvarez's avatar
      Bug 1609996 - Remove mozilla/Move.h. r=froydnj · aa3a6957
      Emilio Cobos Álvarez authored
      rg -l 'mozilla/Move.h' | xargs sed -i 's/#include "mozilla\/Move.h"/#include <utility>/g'
      
      Further manual fixups and cleanups to the include order incoming.
      
      Differential Revision: https://phabricator.services.mozilla.com/D60323
      
      --HG--
      extra : moz-landing-system : lando
      aa3a6957
  9. 21 Nov, 2019 1 commit
    • Hiroyuki Ikezoe's avatar
      Bug 1586986 - Introduce 'fixed margins' on the main-thread to omit the gap... · 1737c375
      Hiroyuki Ikezoe authored
      Bug 1586986 - Introduce 'fixed margins' on the main-thread to omit the gap between 'fixed margins' on the compositor and the last dynamic toolbar position on the main-thread. r=botond
      
      The gap is caused by the difference between 'fixed margin' on the compositor
      based on the state where the dynamic toolbar is completely visible and
      position:fixed elements positioned by the time where is partially visible or
      completely hidden.  That's because the 'fixed margin' is computed based on the
      bottom of the ICB whereas position:fixed elements are slightly shifted from the
      ICB edge during the toolbar transition.
      
      Differential Revision: https://phabricator.services.mozilla.com/D52337
      
      --HG--
      extra : moz-landing-system : lando
      1737c375
  10. 31 Oct, 2019 2 commits
  11. 08 Oct, 2019 1 commit
    • sotaro's avatar
      Bug 1570879 - Fix high contrast theme handling with DirectComposition and WebRender r=nical · fb4696fe
      sotaro authored
      When high contrast mode is enabled, title bar is drawn as transparent and on-client area rendering by DWM is shown. But when compositor window in GPU process is used, the on-client area rendering was not shown. To address the proboem, window needs to be cleard as transparent and SwapChain of compositor window needs to be DXGI_ALPHA_MODE_PREMULTIPLIED.
      
      WinCompositorWidget::mTransparencyMode is changed to atomic, since it is accessed from compositor thread and render thread.
      
      Differential Revision: https://phabricator.services.mozilla.com/D48302
      
      --HG--
      extra : moz-landing-system : lando
      fb4696fe
  12. 15 Oct, 2019 3 commits
  13. 19 Sep, 2019 2 commits
  14. 15 Sep, 2019 1 commit
  15. 06 Jul, 2019 1 commit
  16. 20 Jun, 2019 1 commit
  17. 26 May, 2019 1 commit
  18. 24 May, 2019 1 commit