74b3da8c8c6c64fac8719bd54bc2bdaf9f672008: Bug 1534343 - Document should check if its mCookieSettings exists before using it, r=Ehsan
Andrea Marchesini <amarchesini@mozilla.com> - Mon, 18 Mar 2019 17:12:10 +0000 - rev 464852
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1534343 - Document should check if its mCookieSettings exists before using it, r=Ehsan Differential Revision: https://phabricator.services.mozilla.com/D23764
fd9f4d4210078620ecc87c13d0ae5a7f18216c91: Backed out changeset c0996caf797f (bug 1523761) for bc failures in browser/components/customizableui/test/browser_947914_button_history.js CLOSED TREE
shindli <shindli@mozilla.com> - Mon, 18 Mar 2019 19:20:56 +0200 - rev 464851
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Backed out changeset c0996caf797f (bug 1523761) for bc failures in browser/components/customizableui/test/browser_947914_button_history.js CLOSED TREE
4f9968338e4e38e8d1b30214d85b9133ff7e3954: Backed out 4 changesets (bug 1534313) for causing a perfmafailing Gtest in /builds/worker/workspace/build/application/firefox/gmp-clearkey CLOSED TREE
shindli <shindli@mozilla.com> - Mon, 18 Mar 2019 18:53:33 +0200 - rev 464850
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Backed out 4 changesets (bug 1534313) for causing a perfmafailing Gtest in /builds/worker/workspace/build/application/firefox/gmp-clearkey CLOSED TREE Backed out changeset fe17244230e8 (bug 1534313) Backed out changeset fc232edfe6e8 (bug 1534313) Backed out changeset eae4a9ff0b9b (bug 1534313) Backed out changeset f4252f238b68 (bug 1534313)
dde899c9bfb92feb4872f9f23cd9e51bcca5d96d: Backed out 3 changesets (bug 1353013) for a11y failures in accessible/tests/mochitest/relations/test_tabbrowser.xul CLOSED TREE
shindli <shindli@mozilla.com> - Mon, 18 Mar 2019 18:21:16 +0200 - rev 464849
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Backed out 3 changesets (bug 1353013) for a11y failures in accessible/tests/mochitest/relations/test_tabbrowser.xul CLOSED TREE Backed out changeset af8bce2330e9 (bug 1353013) Backed out changeset a3d1302b06c0 (bug 1353013) Backed out changeset 976afd1adf84 (bug 1353013)
572526065fb20152c1a9a01e91a21bc7eb8f63d0: Bug 1501665 Part 13: Add a test of Responsive Design Mode resizing of meta viewports. r=gl
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 15:00:17 +0000 - rev 464848
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 13: Add a test of Responsive Design Mode resizing of meta viewports. r=gl This test uses a Document with a fixed-width meta viewport. This test simulates resizing the RDM pane from a wide landscape size to a small square size, and back again. It does this again with meta viewport support turned on. Differential Revision: https://phabricator.services.mozilla.com/D22438
1468489e29bffac25d9df4080ae75d36ebda1c7b: Bug 1501665 Part 12: Update RDM viewport size reporting to make it consistent with zoomed presshells. r=gl
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 15:00:57 +0000 - rev 464847
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 12: Update RDM viewport size reporting to make it consistent with zoomed presshells. r=gl There are two viewports: the layout (or content) viewport, and the visual viewport. This change ensures that we are both setting and checking the visual viewport size, which is the size shown in the RDM control bar. It is still possible to get the layout viewport with getContentSize(). Differential Revision: https://phabricator.services.mozilla.com/D22437
916cbe96f1d308779b27af7b842d1c2dba8024c1: Bug 1501665 Part 11: Add a new test of meta viewport with zero display width. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 15:00:53 +0000 - rev 464846
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 11: Add a new test of meta viewport with zero display width. r=botond This test ensures that when meta viewport width is fixed, and a viewport is requested with zero width, the viewport is assigned a height equal to the scaled display height. Differential Revision: https://phabricator.services.mozilla.com/D22436
8824d55c1b62ca892bf153a66213ada838c65df9: Bug 1501665 Part 10: Modify viewport resize zoom scaling to account for clamped zoom levels. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:59:12 +0000 - rev 464845
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 10: Modify viewport resize zoom scaling to account for clamped zoom levels. r=botond Differential Revision: https://phabricator.services.mozilla.com/D21291
22aac830b13a8ff5f57f8d7c1db94d9caeb26a03: Bug 1501665 Part 9: Early exit around an unnecessary call to UpdateVisualViewportSize. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:58:49 +0000 - rev 464844
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 9: Early exit around an unnecessary call to UpdateVisualViewportSize. r=botond Differential Revision: https://phabricator.services.mozilla.com/D21287
c8bf0f59a60c8396cbf8c07764fcb82e9f13a67d: Bug 1501665 Part 8: Allow MVM::RequestReflow to adjust resolution, and do so when destroying the MVM. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:58:31 +0000 - rev 464843
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 8: Allow MVM::RequestReflow to adjust resolution, and do so when destroying the MVM. r=botond Currently the MobileViewportManager leaves somethings permanently changed even after it is destroyed: it may have changed the resolution of the Document, and it may have set a fixed size for the visual viewport. Both of these changes need to be un-done to return to normal display of the Document. Differential Revision: https://phabricator.services.mozilla.com/D17999
67b1eb6b5087063a4ea8f62ca901a8bb7297a500: Bug 1501665 Part 7: Add a new function to allow visual viewport size to be un-set. r=smaug
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:58:07 +0000 - rev 464842
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 7: Add a new function to allow visual viewport size to be un-set. r=smaug Once nsIPresShell::SetVisualViewportSize is called, we currently have no way to restore the default viewport sizing behavior. This corrects that. We need the default behavior to get correctly-placed scrollbars when turning off meta viewport handling in Responsive Design Mode panes. Differential Revision: https://phabricator.services.mozilla.com/D20593
7d0c48d43cbd967bd70aa05fb1866571f061324f: Bug 1501665 Part 6: Fix an edge case in Document::GetViewportInfo to return css scaled sizes. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:57:47 +0000 - rev 464841
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 6: Fix an edge case in Document::GetViewportInfo to return css scaled sizes. r=botond This fixes a problem in an edge case that we are evidently not testing. If width is 0 and height is auto, we are currently setting height to the unscaled (not CSS units) display height value. In addition to this fix, this patch does two drive-by cleanups of code that uses "defaultScale": The redundantly-defined defaultPixelScale is removed. The masking block-level definition of defaultScale is renamed to bestFitScale. Differential Revision: https://phabricator.services.mozilla.com/D16774
05efd157254b238c0bcb14807bf8ce2ddec20250: Bug 1501665 Part 5: Change UpdateShouldBuildAsyncZoomContainer to check if document is zoomable. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:57:20 +0000 - rev 464840
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 5: Change UpdateShouldBuildAsyncZoomContainer to check if document is zoomable. r=botond Also update ScrollFrameHelper::LayoutScrollbars() to correctly handle overlay scrollbars when zoomed in in RDM. Differential Revision: https://phabricator.services.mozilla.com/D20591
7a7781e568c2a8509de7a51dbb68878514d99417: Bug 1501665 Part 4: Use the new function as a replacement for APZAllowZooming. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:56:55 +0000 - rev 464839
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 4: Use the new function as a replacement for APZAllowZooming. r=botond Differential Revision: https://phabricator.services.mozilla.com/D19239
c947824bd2d893bb162cb7a5ed92ba64a7996829: Bug 1501665 Part 3: Add a new function to determine if a document can use resolution zooming. r=botond
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:56:32 +0000 - rev 464838
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 3: Add a new function to determine if a document can use resolution zooming. r=botond Differential Revision: https://phabricator.services.mozilla.com/D19238
b159f05c2d8ed493e9d4934c78a2718e7f5ac5fc: Bug 1501665 Part 2: Set the inRDMPane property on Documents as they enter/leave RDM. r=gl
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:56:09 +0000 - rev 464837
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 2: Set the inRDMPane property on Documents as they enter/leave RDM. r=gl Differential Revision: https://phabricator.services.mozilla.com/D19237
c37181ff94ab3422a372378aeb75a9792865d8aa: Bug 1501665 Part 1: Add a webidl property to Document to track if it's in an RDM pane. r=smaug
Brad Werth <bwerth@mozilla.com> - Mon, 18 Mar 2019 14:55:51 +0000 - rev 464836
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1501665 Part 1: Add a webidl property to Document to track if it's in an RDM pane. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D19235
af46b1e88998c876d71d38b76ce4a9f7809d80a7: Backed out 13 changesets (bug 1501665) for failing a11y tests in accessible/tests/mochitest/relations/test_tabbrowser.xul CLOSED TREE
shindli <shindli@mozilla.com> - Mon, 18 Mar 2019 18:08:58 +0200 - rev 464835
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Backed out 13 changesets (bug 1501665) for failing a11y tests in accessible/tests/mochitest/relations/test_tabbrowser.xul CLOSED TREE Backed out changeset 2fa518cb0dfc (bug 1501665) Backed out changeset afaf26d7df42 (bug 1501665) Backed out changeset 5bdf0ad9dc66 (bug 1501665) Backed out changeset 520dd24a73fc (bug 1501665) Backed out changeset 3542bf2b89dd (bug 1501665) Backed out changeset 088dc24eabc7 (bug 1501665) Backed out changeset 178210eb72ba (bug 1501665) Backed out changeset 9eebe767ef20 (bug 1501665) Backed out changeset 6a84e97d0e62 (bug 1501665) Backed out changeset cf42ea4e8443 (bug 1501665) Backed out changeset 731d7ee06d86 (bug 1501665) Backed out changeset 8e0afe4a041a (bug 1501665) Backed out changeset be1026de486b (bug 1501665)
70b9b6dbe5b8e2b55a240aa3b39ff6087de92276: Bug 1521729 - P2: Fix failure tests r=mayhemer
Kershaw Chang <kershaw@mozilla.com> - Mon, 18 Mar 2019 14:50:56 +0000 - rev 464834
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1521729 - P2: Fix failure tests r=mayhemer Due to the p1 patch, the first time we get the result back from NS_ShouldSecureUpgrade is always asynchronously. This means that the first http request could be completed slower than the http requests opened after the first one. There are some tests affected by this change, since these tests assume that http requests should be completed in the same order as these requests were created. This patch fixes the tests by introducing a new method in nsIHttpProtocolHandler. This method returns a promise and makes sure the HSTS data is ready to read synchronously when the promise is resolved. Once the HSTS is ready to read, the order of open/close channels will be the same. Differential Revision: https://phabricator.services.mozilla.com/D21683
917f02e20ab6edac88ba0d41d24a3b65409becdd: Bug 1521729 - P1: Support to get the result from NS_ShouldSecureUpgrade asynchronously r=mayhemer
Kershaw Chang <kershaw@mozilla.com> - Mon, 18 Mar 2019 15:48:21 +0000 - rev 464833
Push 35727 by dvarga@mozilla.com at Tue, 19 Mar 2019 09:48:59 +0000
Bug 1521729 - P1: Support to get the result from NS_ShouldSecureUpgrade asynchronously r=mayhemer 1. Make nsHttpChannel::OnBeforeConnect async. 2. There are two ways to get the result from NS_ShouldSecureUpgrade. One is getting the result synchronously from the input reference and the other is via the provided callback. Note that the callback is only used when the storage is not ready to read at startup. Differential Revision: https://phabricator.services.mozilla.com/D20191
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip