17541521c2ece62312b1e907a7675c7c7ba0711c: Bug 1250782 - FxAccountClient: add registerOrUpdateDevice method. r=mcomella
Edouard Oger <eoger@fastmail.com> - Wed, 18 May 2016 12:35:50 -0700 - rev 304071
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1250782 - FxAccountClient: add registerOrUpdateDevice method. r=mcomella MozReview-Commit-ID: 6cGQTZq5G1W
985cadcc9ed5a98f520e6988f556dadbb26266a9: Bug 1250782 - FxAccountClient: add accountStatus method and rename status method to recoveryEmailStatus. r=mcomella
Edouard Oger <eoger@fastmail.com> - Wed, 18 May 2016 12:28:51 -0700 - rev 304070
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1250782 - FxAccountClient: add accountStatus method and rename status method to recoveryEmailStatus. r=mcomella MozReview-Commit-ID: 3fFQaFe14x2
346623206d14008a0877ee57f3a2a4e396386da6: Bug 1250782 - ResourceDelegate#handleSuccess now gives access to a JsonArray body. r=mcomella
Edouard Oger <eoger@fastmail.com> - Wed, 18 May 2016 12:32:55 -0700 - rev 304069
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1250782 - ResourceDelegate#handleSuccess now gives access to a JsonArray body. r=mcomella MozReview-Commit-ID: HbRgCaMPZY7
ec25edc09a602ae0abf6b957d603018598e3ef7b: Bug 1250782 - Allow MozResponse to return a Json array body. r=mcomella
Edouard Oger <eoger@fastmail.com> - Wed, 18 May 2016 12:22:49 -0700 - rev 304068
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1250782 - Allow MozResponse to return a Json array body. r=mcomella MozReview-Commit-ID: B40vvA0E7xJ
9beedb6cbef90bfe3e2b691a17c5c616c7e65b18: Bug 1284829 - Fix the sizes of the VisualElement files for the Win8/10 start menu tile. r=ktbee
Jared Wein <jwein@mozilla.com> - Wed, 06 Jul 2016 10:19:44 -0400 - rev 304067
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1284829 - Fix the sizes of the VisualElement files for the Win8/10 start menu tile. r=ktbee MozReview-Commit-ID: I6FHR1PLPDK
61ee2e040590aab1151d4aca6f03f9ae205a49c4: Bug 1284827 - Fix the path to the VisualElement resources. r=ktbee
Jared Wein <jwein@mozilla.com> - Wed, 06 Jul 2016 08:52:15 -0400 - rev 304066
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1284827 - Fix the path to the VisualElement resources. r=ktbee MozReview-Commit-ID: 6BwMWuES6XS
79d1579dee2efce35b2afed4d13b70855719ec4c: Bug 1283123 - Reps: make it possible to pass in a component to handle object links. r=linclark,honza
Nicolas Chevobbe <chevobbe.nicolas@gmail.com> - Tue, 21 Jun 2016 22:56:10 +0200 - rev 304065
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1283123 - Reps: make it possible to pass in a component to handle object links. r=linclark,honza MozReview-Commit-ID: 20xvwUua4WA
5a6bbd20aa4d45b211d419222ea3f1ae13a470f0: Backed out changeset e178424c2e2a (bug 1261714) for landed already on m-i
Carsten "Tomcat" Book <cbook@mozilla.com> - Thu, 07 Jul 2016 06:22:16 +0200 - rev 304064
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Backed out changeset e178424c2e2a (bug 1261714) for landed already on m-i
e178424c2e2a702ff2c7738e639c59bbed5a17cf: Bug 1261714 - Fix dead CPOW intermittent on browser_toolbox_options_disable_js.js . r=jryans
Nicolas Chevobbe <chevobbe.nicolas@gmail.com> - Tue, 05 Jul 2016 23:24:21 +0200 - rev 304063
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1261714 - Fix dead CPOW intermittent on browser_toolbox_options_disable_js.js . r=jryans MozReview-Commit-ID: G2De93K0Tgv
d8e36b37d5cc4ecccd80b123e47e0623dfebfb88: Bug 1275896 - Replace hard-coded support link for SEC_ERROR_UNKNOWN_ISSUER r=Gijs
Sebastin Santy <sebastinssanty> - Wed, 06 Jul 2016 05:00:00 +0200 - rev 304062
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1275896 - Replace hard-coded support link for SEC_ERROR_UNKNOWN_ISSUER r=Gijs
c8e993f36248d1f0ae66a6fd40af33786723796e: Bug 1269820 - Remove green lock with grey triangle when Mixed Active Content is Blocked r=florian
Sebastin Santy <sebastinssanty> - Wed, 06 Jul 2016 11:32:00 +0200 - rev 304061
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1269820 - Remove green lock with grey triangle when Mixed Active Content is Blocked r=florian
88038ba05ff1a60014bb490ee7849d3b24cbdbfc: Bug 1251071 - "New bookmark" popup disappears if I reopen it after creating bookmark. r=mak
Jared Wein <jwein@mozilla.com> - Wed, 06 Jul 2016 07:27:00 +0200 - rev 304060
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1251071 - "New bookmark" popup disappears if I reopen it after creating bookmark. r=mak MozReview-Commit-ID: DNqcu5vxrBG * * * MozReview-Commit-ID: 3KoNVklCK8d
3468f546b0858d798b57d2bb020fcd309c154c48: Bug 1236283 - Don't mistake <embed> and <object> as having 1 child node when they don't contain anything; r=pbro
Joseph Yeh <jyeh@mozilla.com> - Tue, 05 Jul 2016 00:52:00 +0200 - rev 304059
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1236283 - Don't mistake <embed> and <object> as having 1 child node when they don't contain anything; r=pbro MozReview-Commit-ID: B7bEOP63yxT
0dafaad484d42acb5f411b51c700e47ede4f0321: Bug 1171614 - Add a test for data-URI images to test_inspector_getImageData.html, and check that the server is being truthful about resizing r=jdescottes
Ian Moody <moz-ian@perix.co.uk> - Fri, 01 Jul 2016 18:31:22 +0100 - rev 304058
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1171614 - Add a test for data-URI images to test_inspector_getImageData.html, and check that the server is being truthful about resizing r=jdescottes Also tidy up the HTML a bit by removing errant <img> close tags MozReview-Commit-ID: 4cmtW1S2BI8
52434d177be3fd1dce4509b36d34b3a21c7d9223: Bug 1171614 - Remove the special path for data-URI images from the server inspector actor r=jdescottes
Ian Moody <moz-ian@perix.co.uk> - Fri, 01 Jul 2016 18:28:36 +0100 - rev 304057
Push 30411 by kwierso@gmail.com at Fri, 08 Jul 2016 00:26:45 +0000
Bug 1171614 - Remove the special path for data-URI images from the server inspector actor r=jdescottes MozReview-Commit-ID: 2tWleM1wH1G
4e3c16ea8fced03ab4ef572f16d4aa4464981e2c: Merge mozilla-central into inbound
Gregory Szorc <gps@mozilla.com> - Thu, 07 Jul 2016 11:30:37 -0700 - rev 304056
Push 30410 by kwierso@gmail.com at Fri, 08 Jul 2016 00:15:43 +0000
Merge mozilla-central into inbound
6041ca2176939905e0d55e6dea4f98e2388bfdf3: Bug 1280546 - Disable automatic NSWindow tabbing on 10.12. r=spohl
Markus Stange <mstange@themasta.com> - Thu, 30 Jun 2016 20:24:39 -0400 - rev 304055
Push 30410 by kwierso@gmail.com at Fri, 08 Jul 2016 00:15:43 +0000
Bug 1280546 - Disable automatic NSWindow tabbing on 10.12. r=spohl MozReview-Commit-ID: AnDmvWDMgsg
3bb5c1b4fc5da38dfb5626bb15527119e7858c55: Bug 1283637 - Don't specify the 'state' key in the CoreUI options for overlay scrollbars unless the scrollbar is actually hovered. r=spohl
Markus Stange <mstange@themasta.com> - Thu, 30 Jun 2016 19:44:41 -0400 - rev 304054
Push 30410 by kwierso@gmail.com at Fri, 08 Jul 2016 00:15:43 +0000
Bug 1283637 - Don't specify the 'state' key in the CoreUI options for overlay scrollbars unless the scrollbar is actually hovered. r=spohl MozReview-Commit-ID: 5pak1tqlwM5
39dabd617b129f7c8de7c10bff048406fda44663: Bug 1012752 - Snap scrolled area to layer pixels. r=tnikkel
Markus Stange <mstange@themasta.com> - Thu, 02 Jun 2016 15:41:51 -0400 - rev 304053
Push 30410 by kwierso@gmail.com at Fri, 08 Jul 2016 00:15:43 +0000
Bug 1012752 - Snap scrolled area to layer pixels. r=tnikkel We want the maximum scroll position to be aligned with layer pixels. That way we don't have to re-rasterize the scrolled contents once scrolling hits the edge of the scrollable area. Here's how we determine the maximum scroll position: We get the scroll port rect, snapped to layer pixels. Then we get the scrolled rect and also snap that to layer pixels. The maximum scroll position is set to the difference between right/bottom edges of these rectangles. Now the scrollable area is computed by adding this maximum scroll position to the unsnapped scroll port size. The underlying idea here is: Pretend we have overflow:visible so that the scrolled contents start at (0, 0) relative to the scroll port and spill over the scroll port edges. When these contents are rendered, their rendering is snapped to layer pixels. We want those exact pixels to be accessible by scrolling. This way of computing the snapped scrollable area ensures that, if you scroll to the maximum scroll position, the right/bottom edges of the rendered scrolled contents line up exactly with the right/bottom edges of the scroll port. The scrolled contents are neither cut off nor are they moved too far. (This is something that no other browser engine gets completely right, see the testcase in bug 1012752.) There are also a few disadvantages to this solution. We snap to layer pixels, and the size of a layer pixel can depend on the zoom level, the document resolution, the current screen's scale factor, and CSS transforms. The snap origin is the position of the reference frame. So a change to any of these things can influence the scrollable area and the maximum scroll position. This patch does not make us adjust the current scroll position in the event that the maximum scroll position changes such that the current scroll position would be out of range, unless there's a reflow of the scrolled contents. This means that we can sometimes render a slightly inconsistent state where the current scroll position exceeds the maximum scroll position. We can fix this once it turns out to be a problem; I doubt that it will be a problem because none of the other browsers seems to prevent this problem either. The size of the scrollable area is exposed through the DOM properties scrollWidth and scrollHeight. At the moment, these are integer properties, so their value is rounded to the nearest CSS pixel. Before this patch, the returned value would always be within 0.5 CSS pixels of the value that layout computed for the content's scrollable overflow based on the CSS styles of the contents. Now that scrollWidth and scrollHeight also depend on pixel snapping, their values can deviate by up to one layer pixel from what the page might expect based on the styles of the contents. This change requires a few changes to existing tests. The fact that scrollWidth and scrollHeight can change based on the position of the scrollable element and the zoom level / resolution may surprise some web pages. However, this also seems to happen in Edge. Edge seems to always round scrollWidth and scrollHeight upwards, possibly to their equivalent of layout device pixels. MozReview-Commit-ID: 3LFV7Lio4tG
015a827edf567ce10c866c655aa6d7759d5871f7: Backed out changeset 2620e5ba1067 (bug 1282795) for 'Concrete' redeclaration in HeapSnapshot.h (static failure). r=backout
Sebastian Hengst <archaeopteryx@coole-files.de> - Thu, 07 Jul 2016 19:26:27 +0200 - rev 304052
Push 30410 by kwierso@gmail.com at Fri, 08 Jul 2016 00:15:43 +0000
Backed out changeset 2620e5ba1067 (bug 1282795) for 'Concrete' redeclaration in HeapSnapshot.h (static failure). r=backout
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip