- Sep 18, 2017
-
-
Axel Hecht authored
MozReview-Commit-ID: 5SmOCzTZiqz --HG-- extra : rebase_source : 3f75fe0d8efc1fd7f4d671128790e2d0a0d43d57
-
- Sep 15, 2017
-
-
Axel Hecht authored
MozReview-Commit-ID: 3qF0i39CYjh --HG-- extra : rebase_source : 71465b8a634e1ddaacfddbf9a79adc925f3930b3
-
- Sep 18, 2017
-
-
Kevin Chen authored
MozReview-Commit-ID: AXY7IjhE1DV --HG-- extra : rebase_source : b3081033087b58bd7aeeba829edfe703d5f14782
-
Sebastian Hengst authored
Backed out changeset d928ad6475d2 (bug 1397229) for failing browser-chrome's browser/base/content/test/performance/browser_windowopen_reflows.js on Windows 7. r=backout
-
Sebastian Hengst authored
-
Sebastian Hengst authored
-
Sebastian Hengst authored
-
- Sep 17, 2017
-
-
Gijs Kruitbosch authored
Rather than using left-hand-side at all times (which can go over the edge of the window in some cases) this uses left or right-hand-side panels, always opening towards the center of the window. MozReview-Commit-ID: EvjDmKR1G5A --HG-- extra : rebase_source : 12046edc24b564e035dff68a5e34bce3ff5fd507
-
Gijs Kruitbosch authored
Note that we will no longer show the panel if you use the context menu to move the item in one window and have customize mode open in the other. I don't think that edgecase matters. MozReview-Commit-ID: 3dzGr3cs2oQ --HG-- extra : rebase_source : cc5f528557e35e48b0bc06e58b92fdcb7ecfa6fe
-
- Sep 15, 2017
-
-
Botond Ballo authored
MozReview-Commit-ID: E7Ukb76vMep --HG-- extra : rebase_source : 5cfeccb1e21959e5614d0da70f60bf9ad548154f
-
Botond Ballo authored
Bug 1400440 - Apply scroll shift for dynamic toolbar to the composited scroll offset right away. r=kats MozReview-Commit-ID: 1I7C0lFx4WP --HG-- extra : rebase_source : 9c6ae39e10a2f9b86d2886140ee2e0d4f5cb4fda
-
- Sep 05, 2017
-
-
Randall Barker authored
Bug 1392705 - part 3: Call nsBaseWidget::DestroyLayerManager() in nsWindow::Destroy to ensure IPC is not shutdown in the destructor for Android r=jchen Due to the indeterminate nature of Gecko shutdown, the ref count of the nsWindow on Android would sometimes go to zero before the XPCOM shutdown observer was called in nsBaseWindow which is where the compositor thread IPC is shutdown. If nsBaseWindow::Shutdown does not get called, then the compositor thread IPC is shutdown in the nsBaseWindow destructor. Unfortunately while the nsWindow is being deleted, it can be accessed in the compositor thread and cause a crash in LayerManagerComposite::RenderToPresentationSurface. Calling nsBaseWidget::DestroyLayerManager() in nsWindow::Destroy() ensures it gets called before the destructor gets invoked typically in the Destroy() call. MozReview-Commit-ID: KCv8SCmEjnb --HG-- extra : rebase_source : f48fe01b15ff7e2e8763628dd22a2c926d051e9d
-
- Sep 01, 2017
-
-
Randall Barker authored
Bug 1392705 - part 2: Ensure LayerManagerComposite::RenderToPresentationSurface checks the compositor widget before using it r=kats MozReview-Commit-ID: 6EP9Pp4h5cP --HG-- extra : rebase_source : 878dac0056cb96a6206d39bd000425578503ec2b
-
- Aug 31, 2017
-
-
Randall Barker authored
Ensure the UiCompositorControllerChild is shutdown in the UI thread before the compositor thread is shutdown by the main thread. MozReview-Commit-ID: 4hXYxSi9tzz --HG-- extra : rebase_source : fd265b39986f453ea9ab59c60bb80319b74e8f9c
-
- Sep 18, 2017
-
-
Mark Banner authored
Bug 1399946 - Bump version number of eslint-plugin-mozilla for releasing the dependency fixes from bug 1395879. r=ahal MozReview-Commit-ID: 79nDcgcvm0c --HG-- extra : rebase_source : 78d2dd8eaec5d36c8611effe96f93949b76929e9
-
Henrik Skupin authored
Currently only the Mochitests on Linux use a startup_timeout of 180s for Marionette. This would also be necessary for the other platforms (MacOS and Windows). MozReview-Commit-ID: TGO7XDLXdI --HG-- extra : rebase_source : 29219cc51404cebf22e894966294eae687bb5d68
-
Henrik Skupin authored
On Windows TaskCluster workers Marionette could be ready within 1s. As such the currently used timeout is too long, and needs to be further reduced. MozReview-Commit-ID: KbLVdpB71cu --HG-- extra : rebase_source : 2b9139e4b7e2c9d5815e7cc481086ca779385538
-
Gijs Kruitbosch authored
Bug 1400810 - fix context menus looking squashed while retaining changes to shortcut and footer alignment, r=johannh MozReview-Commit-ID: GPAEdE7eMxk --HG-- extra : rebase_source : e835f5a12b2f8e0437f97ed304ae6494d33713ee
-
Ryan VanderMeulen authored
-
- Sep 15, 2017
-
-
Brad Werth authored
Bug 1399941 Part 2: Add more aspect-ratios to a test of media queries, testing for overflow. r=emilio MozReview-Commit-ID: 6NLYkLUNP8d --HG-- extra : rebase_source : 3aabc27266c676837aba2275f4837dd07fd5f412
-
- Sep 18, 2017
-
-
Jan Odvarko authored
MozReview-Commit-ID: 4FNK3j3filG --HG-- extra : rebase_source : aec5ac04bbe1358d932af0531de2b90c1cabb83a
-
- Sep 07, 2017
-
-
Andrew Halberstadt authored
MozReview-Commit-ID: FqmgeKc1b9o --HG-- extra : rebase_source : 8402d45d2c9f7afcc1a83366bcdd51def1ca3639
-
- Sep 15, 2017
-
-
Andrew Halberstadt authored
Bug 1397229 - Disable toolkit/browser/components/tooltiptext/browser_input_file_tooltips.js on Win10, r=jmaher This started failing when migrating from Windows 8 -> Windows 10. Fix is tracked in bug 1400368. MozReview-Commit-ID: BIKAQDcJnXR --HG-- extra : rebase_source : 5d99fbd6d548344781c79d8debe918e713b533ee
-
Andrew Halberstadt authored
Bug 1397229 - Disable browser/base/content/test/performance/browser_startup_images.js hidpi on Windows 10, r=jmaher This started failing when migrating from Windows 8 -> Windows 10. Fix is tracked in bug 1400357. MozReview-Commit-ID: HO0AYGjVTGm --HG-- extra : rebase_source : 979f41e192a7e862a446b07c55fdde55e5fbdafd
-
- Sep 07, 2017
-
-
Andrew Halberstadt authored
This test was previously skipped on Windows 8. This bug is migrating the test over to Windows 10 where we discovered the unused reflow. MozReview-Commit-ID: FqmgeKc1b9o --HG-- extra : rebase_source : 4c15104b9d63c44dc5c397cb34cf9320797a48a4
-
- Sep 18, 2017
-
-
Emilio Cobos Álvarez authored
servo: Merge #18543 - script: Fix integer-JSID handling in named getters (from emilio:named-getter-int); r=nox On top of #18539, fixes #10686. Source-Repo: https://github.com/servo/servo Source-Revision: ba90e13863208656b7f2e1f5727bb7bada83a0be --HG-- extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear extra : subtree_revision : f714b47e73db51947cdd5d1eb13d967560415457
-
Simon Fraser authored
MozReview-Commit-ID: G6EFXY0UzSa --HG-- extra : rebase_source : dbea33ec8d96cc9a0e016e4828f9f989fca7131b
-
- Sep 17, 2017
-
-
Greg Mierzwinski authored
This patch disables the test 'devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js' on linux64-jsdcov for perma-failing. MozReview-Commit-ID: 1NTOI01g6AV --HG-- extra : rebase_source : 2bf58b1091424ec64b5a0e8571769d11a3d3bc57
-
Greg Mierzwinski authored
This patch makes it possible to disable mochitest-devtools tests on linux64-jsdcov through the 'coverage' flag. MozReview-Commit-ID: 1gkgbFo19MZ --HG-- extra : rebase_source : 9c6d311cb467e4424d42848e1caf024f9702b8cd
-
- Sep 18, 2017
-
-
Sebastian Hengst authored
Backed out changeset 0d71c0be62de (bug 1342392) for bustage in partial update generator for docker images: recompress.sh not found. r=backout --HG-- rename : taskcluster/docker/partial-update-generator/Dockerfile => taskcluster/docker/funsize-update-generator/Dockerfile rename : taskcluster/docker/partial-update-generator/Makefile => taskcluster/docker/funsize-update-generator/Makefile rename : taskcluster/docker/partial-update-generator/README => taskcluster/docker/funsize-update-generator/README rename : taskcluster/docker/partial-update-generator/dep.pubkey => taskcluster/docker/funsize-update-generator/dep.pubkey rename : taskcluster/docker/partial-update-generator/nightly_sha1.pubkey => taskcluster/docker/funsize-update-generator/nightly_sha1.pubkey rename : taskcluster/docker/partial-update-generator/nightly_sha384.pubkey => taskcluster/docker/funsize-update-generator/nightly_sha384.pubkey rename : taskcluster/docker/partial-update-generator/release_sha1.pubkey => taskcluster/docker/funsize-update-generator/release_sha1.pubkey rename : taskcluster/docker/partial-update-generator/release_sha384.pubkey => taskcluster/docker/funsize-update-generator/release_sha384.pubkey rename : taskcluster/docker/partial-update-generator/requirements.txt => taskcluster/docker/funsize-update-generator/requirements.txt rename : taskcluster/docker/partial-update-generator/runme.sh => taskcluster/docker/funsize-update-generator/runme.sh rename : taskcluster/docker/partial-update-generator/scripts/funsize.py => taskcluster/docker/funsize-update-generator/scripts/funsize.py rename : taskcluster/docker/partial-update-generator/scripts/mbsdiff_hook.sh => taskcluster/docker/funsize-update-generator/scripts/mbsdiff_hook.sh
-
- Sep 15, 2017
-
-
Simon Fraser authored
MozReview-Commit-ID: 84fP48sMYhS --HG-- rename : taskcluster/docker/funsize-update-generator/Dockerfile => taskcluster/docker/partial-update-generator/Dockerfile rename : taskcluster/docker/funsize-update-generator/Makefile => taskcluster/docker/partial-update-generator/Makefile rename : taskcluster/docker/funsize-update-generator/README => taskcluster/docker/partial-update-generator/README rename : taskcluster/docker/funsize-update-generator/dep.pubkey => taskcluster/docker/partial-update-generator/dep.pubkey rename : taskcluster/docker/funsize-update-generator/nightly_sha1.pubkey => taskcluster/docker/partial-update-generator/nightly_sha1.pubkey rename : taskcluster/docker/funsize-update-generator/nightly_sha384.pubkey => taskcluster/docker/partial-update-generator/nightly_sha384.pubkey rename : taskcluster/docker/funsize-update-generator/release_sha1.pubkey => taskcluster/docker/partial-update-generator/release_sha1.pubkey rename : taskcluster/docker/funsize-update-generator/release_sha384.pubkey => taskcluster/docker/partial-update-generator/release_sha384.pubkey rename : taskcluster/docker/funsize-update-generator/requirements.txt => taskcluster/docker/partial-update-generator/requirements.txt rename : taskcluster/docker/funsize-update-generator/runme.sh => taskcluster/docker/partial-update-generator/runme.sh rename : taskcluster/docker/funsize-update-generator/scripts/funsize.py => taskcluster/docker/partial-update-generator/scripts/funsize.py rename : taskcluster/docker/funsize-update-generator/scripts/mbsdiff_hook.sh => taskcluster/docker/partial-update-generator/scripts/mbsdiff_hook.sh extra : rebase_source : e5a6cc3aafccde8c9e8cd175aafc7e641ca17031
-
- Sep 17, 2017
-
-
Kartikaya Gupta authored
MozReview-Commit-ID: Ae80DrMwg1X --HG-- extra : rebase_source : e90ffd1b443de46fa3d1bde9acaa4e97eabdf135
-
Kartikaya Gupta authored
Bug 1400034 - Do a more direct translation of transforms from Gecko to WR in layers-free mode. r=ethlin,pchang In layers-free mode the gecko display list and coordinate system is very similar to what WR is expecting. Instead of having each StackingContextHelper shift the origin of the coordinate system, we can leave it in one spot and just pass everything relative to that. The semantics of the Gecko display list already matches this; the exception is that nsDisplayTransform items are also considered reference frames, and anything inside them is relative to the nsDisplayTransform. On the WR side this is also the case, because stacking contexts with a transform are implicitly turned into reference frames. Additionally, the size of the bounds passed to the WR stacking context is never actually used, except on the root stacking context (which is not created by StackingContextHelper). Since we want a zero origin (as explained above) and the size is never used, we can just pass a zero rect to the WR stacking context from StackingContextHelper. In terms of the actual transform matrix, this patch now passes the full unmodified transform from nsDisplayTransform into WR. This transform gets applied onto the contents of the nsDisplayTransform. The contents' coordinate system is relative to the frame that generated the nsDisplayTransform. Again this maps directly to WR, where the transform on the stacking context gets applied to the contents of the stacking context; the contents' coordinates are relative to the stacking context. MozReview-Commit-ID: 9hdDxdKXPPi --HG-- extra : rebase_source : b201cea867c6c6e26c2b0bcd0e38c8722f09fe77
-
Kartikaya Gupta authored
Bug 1400034 - Back out changes that introduce scaling complexity to StackingContextHelper. r=ethlin,pchang This backs out bug 1399050, bug 1394308 (2 patches), and bug 1391499. I believe these patches sent us down a path that would make the code increasingly more complex, when in fact we can do a more "direct" translation from the gecko display list to the WR display list and make things a lot simpler and more correct. MozReview-Commit-ID: ZXXkI9DXiY --HG-- extra : rebase_source : 47ce1fcb87f0c21d158ee06f38e2b3303f999270
-
- Sep 18, 2017
-
-
Sebastian Hengst authored
--HG-- rename : taskcluster/docker/partial-update-generator/Dockerfile => taskcluster/docker/funsize-update-generator/Dockerfile rename : taskcluster/docker/partial-update-generator/Makefile => taskcluster/docker/funsize-update-generator/Makefile rename : taskcluster/docker/partial-update-generator/README => taskcluster/docker/funsize-update-generator/README rename : taskcluster/docker/partial-update-generator/dep.pubkey => taskcluster/docker/funsize-update-generator/dep.pubkey rename : taskcluster/docker/partial-update-generator/nightly_sha1.pubkey => taskcluster/docker/funsize-update-generator/nightly_sha1.pubkey rename : taskcluster/docker/partial-update-generator/nightly_sha384.pubkey => taskcluster/docker/funsize-update-generator/nightly_sha384.pubkey rename : taskcluster/docker/partial-update-generator/recompress.sh => taskcluster/docker/funsize-update-generator/recompress.sh rename : taskcluster/docker/partial-update-generator/release_sha1.pubkey => taskcluster/docker/funsize-update-generator/release_sha1.pubkey rename : taskcluster/docker/partial-update-generator/release_sha384.pubkey => taskcluster/docker/funsize-update-generator/release_sha384.pubkey rename : taskcluster/docker/partial-update-generator/requirements.txt => taskcluster/docker/funsize-update-generator/requirements.txt rename : taskcluster/docker/partial-update-generator/runme.sh => taskcluster/docker/funsize-update-generator/runme.sh rename : taskcluster/docker/partial-update-generator/scripts/funsize.py => taskcluster/docker/funsize-update-generator/scripts/funsize.py rename : taskcluster/docker/partial-update-generator/scripts/mbsdiff_hook.sh => taskcluster/docker/funsize-update-generator/scripts/mbsdiff_hook.sh rename : taskcluster/docker/partial-update-generator/scripts/recompress.py => taskcluster/docker/funsize-update-generator/scripts/recompress.py
-
- Sep 16, 2017
-
-
Andreas Tolfsen authored
This is a liberal port of the old geckodriver release instructions that are on the GitHub wiki: https://github.com/mozilla/geckodriver/wiki/Releasing Because the project's canonical home has moved to mozilla-central, it is better to keep all documentation in one place. Documentation close to the source code is the best. I have improved the release instructions in a number of ways, in particular by describing how to make a release to GitHub/Travis from mozilla-central. DONTBUILD MozReview-Commit-ID: 6f87DLDM59E --HG-- extra : rebase_source : c144ac8ee2486a38d7eb26c91276e841be50fc81
-
- Sep 15, 2017
-
-
Simon Fraser authored
MozReview-Commit-ID: 84fP48sMYhS --HG-- rename : taskcluster/docker/funsize-update-generator/Dockerfile => taskcluster/docker/partial-update-generator/Dockerfile rename : taskcluster/docker/funsize-update-generator/Makefile => taskcluster/docker/partial-update-generator/Makefile rename : taskcluster/docker/funsize-update-generator/README => taskcluster/docker/partial-update-generator/README rename : taskcluster/docker/funsize-update-generator/dep.pubkey => taskcluster/docker/partial-update-generator/dep.pubkey rename : taskcluster/docker/funsize-update-generator/nightly_sha1.pubkey => taskcluster/docker/partial-update-generator/nightly_sha1.pubkey rename : taskcluster/docker/funsize-update-generator/nightly_sha384.pubkey => taskcluster/docker/partial-update-generator/nightly_sha384.pubkey rename : taskcluster/docker/funsize-update-generator/recompress.sh => taskcluster/docker/partial-update-generator/recompress.sh rename : taskcluster/docker/funsize-update-generator/release_sha1.pubkey => taskcluster/docker/partial-update-generator/release_sha1.pubkey rename : taskcluster/docker/funsize-update-generator/release_sha384.pubkey => taskcluster/docker/partial-update-generator/release_sha384.pubkey rename : taskcluster/docker/funsize-update-generator/requirements.txt => taskcluster/docker/partial-update-generator/requirements.txt rename : taskcluster/docker/funsize-update-generator/runme.sh => taskcluster/docker/partial-update-generator/runme.sh rename : taskcluster/docker/funsize-update-generator/scripts/funsize.py => taskcluster/docker/partial-update-generator/scripts/funsize.py rename : taskcluster/docker/funsize-update-generator/scripts/mbsdiff_hook.sh => taskcluster/docker/partial-update-generator/scripts/mbsdiff_hook.sh rename : taskcluster/docker/funsize-update-generator/scripts/recompress.py => taskcluster/docker/partial-update-generator/scripts/recompress.py extra : rebase_source : 5c6e1e909339f58ada48285294d97f3a4de46c28
-
- Sep 18, 2017
-
-
Boris Chiou authored
servo: Merge #18517 - style: Clamp some filter functions to one if the values over 100% (from BorisChiou:stylo/filter/clamp); r=emilio For grayscale, invert, opacity, and sepia, "values of amount over 100% are allowed but UAs must clamp the values to 1" [1]-[4], so we clamp its value in the parser. [1] https://drafts.fxtf.org/filter-effects/#funcdef-filter-grayscale [2] https://drafts.fxtf.org/filter-effects/#funcdef-filter-invert [3] https://drafts.fxtf.org/filter-effects/#funcdef-filter-opacity [4] https://drafts.fxtf.org/filter-effects/#funcdef-filter-sepia --- - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix [Bug 1399799](https://bugzilla.mozilla.org/show_bug.cgi?id=1399799). - [X] There are tests for these changes Source-Repo: https://github.com/servo/servo Source-Revision: cff9b427fca1ab878fd23929cf7835666aab6d84 --HG-- extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear extra : subtree_revision : da2427034269c1a55c8b0fdfa4d48443e8e7bd1f
-
Mateusz Naściszewski authored
servo: Merge #18506 - Fix issues with the combination of position:sticky and tables (from mrobinson:position-sticky-table); r=emilio <!-- Please describe your changes on the following line: --> --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [ ] These changes fix #18441 (github issue number if applicable). <!-- Either: --> - [x] There are tests for these changes OR - [ ] These changes do not require tests because _____ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: 1da581f49b039d5eda5fa618fc41905d444c4885 --HG-- extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear extra : subtree_revision : 53f485d0076d89d20ea6611a08037285eb0ec62b
-
Alastor Wu authored
MozReview-Commit-ID: 3MGmU34JY3t --HG-- extra : rebase_source : 154697238162ff92f861e7cbaa1a6d22b1ee13f4
-