80efe717b563f329a2261a8d23f4ebbc470c432f: Bug 1455422 - Implement the new blob image rasterization hooks. r=kats, gankro
Nicolas Silva <nsilva@mozilla.com> - Thu, 19 Jul 2018 16:33:05 -0400 - rev 821197
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1455422 - Implement the new blob image rasterization hooks. r=kats, gankro
7041b2f0aef8df57cd4b33ee054dd866422ff61d: Bug 1476636. Update Cargo lockfiles, re-vendor rust dependencies
Jeff Muizelaar <jmuizelaar@mozilla.com> - Fri, 20 Jul 2018 17:24:55 -0400 - rev 821196
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1476636. Update Cargo lockfiles, re-vendor rust dependencies
5fdc7f00aba11df0fd5ebefa73050d7659a31abc: Bug 1476636. Update webrender to commit 9f21ee5dba0694818a1e2e46d95734ede281447c
Jeff Muizelaar <jmuizelaar@mozilla.com> - Fri, 20 Jul 2018 17:24:47 -0400 - rev 821195
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1476636. Update webrender to commit 9f21ee5dba0694818a1e2e46d95734ede281447c
8984f6868e572079cc991492124ba99747f0f681: Bug 1451104 - follow-up - quiet clang-tidy content checking; r=me
Nathan Froyd <froydnj@mozilla.com> - Fri, 20 Jul 2018 17:16:25 -0400 - rev 821194
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1451104 - follow-up - quiet clang-tidy content checking; r=me
f4c0996b0c34b6561201eb28f6ffa0742a692ef6: Bug 1477381 - JS::ubi::TracerConcrete<Referent>::edges as a public method. r=erahm
Kristen Wright <kwright@mozilla.com> - Fri, 20 Jul 2018 12:57:44 -0700 - rev 821193
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1477381 - JS::ubi::TracerConcrete<Referent>::edges as a public method. r=erahm
ae7ccb8c938d180f5777d4be8885cd425b711966: Bug 1451104 -part 5 - touch CLOBBER; r=me
Nathan Froyd <froydnj@mozilla.com> - Fri, 20 Jul 2018 16:24:08 -0400 - rev 821192
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1451104 -part 5 - touch CLOBBER; r=me
52d37e70b6f191a00817b4c7c648b8d5a4d68c08: Bug 1451104 - part 4 - move toolchains off GCC 4.9; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Fri, 20 Jul 2018 16:22:26 -0400 - rev 821191
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1451104 - part 4 - move toolchains off GCC 4.9; r=glandium Firefox itself has moved on to GCC 6.x; we can move our toolchains along too.
47405e33747c180dadbe99e4efcd879120c71c20: Bug 1451104 - part 3 - inform stage2/3 clang about gcc binutils; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Fri, 20 Jul 2018 16:22:26 -0400 - rev 821190
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1451104 - part 3 - inform stage2/3 clang about gcc binutils; r=glandium We do this to encourage clang to find an new-enough linker instead of the system one.
b4ebc9a500f40bdac529378e6cc9f9922076e5c4: Bug 1451104 - part 2 - force clang to always pick up its local GCC headers and libraries; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Fri, 20 Jul 2018 16:22:26 -0400 - rev 821189
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1451104 - part 2 - force clang to always pick up its local GCC headers and libraries; r=glandium We want our clang bootstrap to use the GCC headers we're building with, not whatever sysroot it happens to find on the server we're building on. The -gcc-toolchain argument we specify when building clang will also be picked up by llvm-config, so we need to strip it out when building the plugin. Otherwise, we will get peculiar failures about not being able to find C++ header files.
b93c29157feb5f14b7964b7f83ca88560dc508aa: Bug 1451104 - part 1 - be explicit about our GCC/binutils target and build machine; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Fri, 20 Jul 2018 16:22:26 -0400 - rev 821188
Push 117036 by mozilla@noorenberghe.ca at Sun, 22 Jul 2018 05:15:14 +0000
Bug 1451104 - part 1 - be explicit about our GCC/binutils target and build machine; r=glandium Explicit is better than implicit, and helps ensure that GCC is always using the binutils we built it with, rather than the system binutils.
79b279d751601643d7ece79c3e43aba93b29d7f5: Bug 1476844 - Clear selected tabs whenever 'TabSelect' event is fired except when switching tab from 'switchToNextMultiSelectedTab' function in /browser/base/content/tabbrowser.js. r?jaws draft multiselect_tabs_clear_when_tab_switch_ok
Abdoulaye O. Ly <ablayelyfondou@gmail.com> - Sat, 21 Jul 2018 02:32:19 +0000 - rev 821187
Push 117035 by bmo:ablayelyfondou@gmail.com at Sun, 22 Jul 2018 05:12:43 +0000
Bug 1476844 - Clear selected tabs whenever 'TabSelect' event is fired except when switching tab from 'switchToNextMultiSelectedTab' function in /browser/base/content/tabbrowser.js. r?jaws MozReview-Commit-ID: J2DyAbQJITo
c40d3ff5c1a0352651d7d1444e929af6bdac0cd7: Bug 1476844 - Clear selected tabs whenever 'TabSelect' event is fired except when switching tab from 'switchToNextMultiSelectedTab' function in /browser/base/content/tabbrowser.js. r?jaws draft multiselect_tabs_clear_when_tab_switch_ok
Abdoulaye O. Ly <ablayelyfondou@gmail.com> - Sat, 21 Jul 2018 02:32:19 +0000 - rev 821186
Push 117034 by bmo:ablayelyfondou@gmail.com at Sun, 22 Jul 2018 03:57:08 +0000
Bug 1476844 - Clear selected tabs whenever 'TabSelect' event is fired except when switching tab from 'switchToNextMultiSelectedTab' function in /browser/base/content/tabbrowser.js. r?jaws MozReview-Commit-ID: J2DyAbQJITo
439713456d4c3d5cf35048656eaf710a1c9903e5: Bug 1476844 - Clear selected tabs whenever 'TabSelect' event is fired except when switching tab from 'switchToNextMultiSelectedTab' function in /browser/base/content/tabbrowser.js. r?jaws draft multiselect_tabs_clear_when_tab_switch_ok
Abdoulaye O. Ly <ablayelyfondou@gmail.com> - Sat, 21 Jul 2018 02:32:19 +0000 - rev 821185
Push 117033 by bmo:ablayelyfondou@gmail.com at Sun, 22 Jul 2018 03:50:56 +0000
Bug 1476844 - Clear selected tabs whenever 'TabSelect' event is fired except when switching tab from 'switchToNextMultiSelectedTab' function in /browser/base/content/tabbrowser.js. r?jaws MozReview-Commit-ID: J2DyAbQJITo
4e08c3a92dcd99d4c5b527bab0f1f11f21ab8851: Bug 1475342 - Move document.getElementsByAttribute[NS] to ParentNode so it'll work for HTML document and elements;r=bz draft
Brian Grinstead <bgrinstead@mozilla.com> - Sat, 21 Jul 2018 18:11:08 -0700 - rev 821184
Push 117032 by bgrinstead@mozilla.com at Sun, 22 Jul 2018 01:11:32 +0000
Bug 1475342 - Move document.getElementsByAttribute[NS] to ParentNode so it'll work for HTML document and elements;r=bz It's currently only accessible on XULDocument and XULElement, but that makes porting existing JS to run in an HTML document inconvenient. We could alternatively change calling JS, but this can be easily moved and exposed in chrome contexts. MozReview-Commit-ID: 2sUXFj0dg0f
0dfc449ecbbd3ffc4e5f2ecaec730fe85f287ae2: Bug 1465616 - Add async-scroll reftests. r?botond draft
Kashav Madan <kmadan@mozilla.com> - Fri, 20 Jul 2018 17:48:30 -0400 - rev 821183
Push 117031 by bmo:kmadan@mozilla.com at Sat, 21 Jul 2018 23:59:14 +0000
Bug 1465616 - Add async-scroll reftests. r?botond The first set of tests test that fixed/sticky position elements are no longer attached to the visual viewport (i.e., that they go "out of view" when the visual viewport is scrolled) and the second set of tests test that fixed/sticky position elements are attached to the layout viewport (i.e., that they "follow" the layout viewport when it's scrolled). MozReview-Commit-ID: 6H2f0oz9lW7
1fc92e8615999bfea4cabd8bf198086a26efb80c: Bug 1465616 - Use layout viewport transformations to async-adjust fixed position elements. r?botond draft
Kashav Madan <kmadan@mozilla.com> - Fri, 20 Jul 2018 17:45:48 -0400 - rev 821182
Push 117031 by bmo:kmadan@mozilla.com at Sat, 21 Jul 2018 23:59:14 +0000
Bug 1465616 - Use layout viewport transformations to async-adjust fixed position elements. r?botond This results in fixed position elements being attached to the layout viewport when being async-scrolled by APZ. MozReview-Commit-ID: 2YYIDnTWgVn
bb393c02d971d279a10a1c67aba5a6515f71ce77: Bug 1465616 - Apply async scroll & zoom to FrameMetrics in GetCurrentAsyncTransform. r?botond draft
Kashav Madan <kmadan@mozilla.com> - Fri, 20 Jul 2018 17:37:36 -0400 - rev 821181
Push 117031 by bmo:kmadan@mozilla.com at Sat, 21 Jul 2018 23:59:14 +0000
Bug 1465616 - Apply async scroll & zoom to FrameMetrics in GetCurrentAsyncTransform. r?botond Includes a new RAII class, AutoApplyTestAttributes, which, for the duration of its lifetime, applies mTestAsyncScrollOffset and mTestAsyncZoom to the controller's FrameMetrics and calls FrameMetrics::RecalculateViewportOffset to ensure APZC is using a layout viewport offset corresponding to the updated scroll offset and zoom. MozReview-Commit-ID: 9owJcdIegNH
854c63b6a479fa7a9f8c633edec6efede8d62d06: Bug 1477512: Part 5 - Rearrange the fields of nsThread for better packing. r?erahm draft
Kris Maglione <maglione.k@gmail.com> - Sat, 21 Jul 2018 16:00:02 -0700 - rev 821180
Push 117030 by maglione.k@gmail.com at Sat, 21 Jul 2018 23:02:46 +0000
Bug 1477512: Part 5 - Rearrange the fields of nsThread for better packing. r?erahm This takes 16 bytes off of the allocated size of each instance. MozReview-Commit-ID: AhfN6MWvVL1
372e2b9cad4b2061c8fa8992838a808ed5a3f6d0: Bug 1477512: Part 4 - Add memory reporter for thread kernel stack sizes. r?erahm draft
Kris Maglione <maglione.k@gmail.com> - Sat, 21 Jul 2018 15:12:11 -0700 - rev 821179
Push 117030 by maglione.k@gmail.com at Sat, 21 Jul 2018 23:02:46 +0000
Bug 1477512: Part 4 - Add memory reporter for thread kernel stack sizes. r?erahm We don't have a way to determine these at runtime, but for Windows and Linux, the values are known and predictable. MozReview-Commit-ID: 57LMJLzl762
1f902f2d190f9c6bfea0f8b6702b9ae91e4022d8: Bug 1477512: Part 3 - Add memory reporter for thread heap overhead. r?erahm draft
Kris Maglione <maglione.k@gmail.com> - Sat, 21 Jul 2018 14:27:15 -0700 - rev 821178
Push 117030 by maglione.k@gmail.com at Sat, 21 Jul 2018 23:02:46 +0000
Bug 1477512: Part 3 - Add memory reporter for thread heap overhead. r?erahm This adds reporting for heap overhead from nsThread and PRThread wrappers, as well as thread event queues. It does not, currently, include overhead from PlatformThread or js::Thread wrappers. MozReview-Commit-ID: 6DkvbbkjHXm
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip