7e4a87170569ece8bec68b8163e430ca43937a44: Bug 887889 - Limit scope of executeTransaction closure r=mak
Doug Thayer <dothayer@mozilla.com> - Tue, 27 Mar 2018 10:30:37 -0700 - rev 788877
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 887889 - Limit scope of executeTransaction closure r=mak MozReview-Commit-ID: 9d2xh4Qxs3q
e7f2bc2cb13cbf63ef78ce215d0c393f2bd3ef87: Bug 887889 - Relax Sqlite.jsm restrictions in browser_startup.js r=florian
Doug Thayer <dothayer@mozilla.com> - Mon, 26 Mar 2018 10:08:30 -0700 - rev 788876
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 887889 - Relax Sqlite.jsm restrictions in browser_startup.js r=florian We've improved the startup IO situation in bug 887889 by not synchronously initializing a connection to the contentprefs db. However, this means we are loading Sqlite.jsm earlier than we were, which isn't ideal and can be avoided. However, this isn't completely trivial so I'd like to move this work to a follow-up. MozReview-Commit-ID: 6Em0rN26Qj3
744a7b9fe0abd1095d0f5ba464161d51a97a33b7: Bug 887889 - Asyncify cps2 tests r=mak
Doug Thayer <dothayer@mozilla.com> - Mon, 12 Mar 2018 14:46:24 -0700 - rev 788875
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 887889 - Asyncify cps2 tests r=mak I converted the cps2 tests to use async/await, since it was easier for me to debug the breakages introduced by my changes that way. There are a few differences hidden in there, though - most notable is that I also modified the direct db access in the tests to use the Sqlite.jsm wrapper. This was to avoid reaching into the connections internals in order to get the underlying connection. MozReview-Commit-ID: DwJ5hfyvAOf
29598c587f7fb07c434df30534bdf489f987562d: Bug 887889 - Migrate ContentPrefService2 to Sqlite.jsm r=mak
Doug Thayer <dothayer@mozilla.com> - Mon, 12 Mar 2018 14:41:42 -0700 - rev 788874
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 887889 - Migrate ContentPrefService2 to Sqlite.jsm r=mak - I kept the xpcom-shutdown observer around even though it's not doing much and it could be satisfied by doing a little more work in the Sqlite.shutdown blocker. I wasn't sure which to use since it seems like the Sqlite.shutdown blocker is intended to be used to cleanup connection-related things. Thoughts on this are welcome. MozReview-Commit-ID: CqcGHBFaJsZ
fec4af27b939fe5cf2a5d6ab6290e1feaa302a18: Bug 1457317 - Show a title for the add/edit pages. r=MattN
Jared Wein <jwein@mozilla.com> - Thu, 26 Apr 2018 15:43:31 -0700 - rev 788873
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1457317 - Show a title for the add/edit pages. r=MattN MozReview-Commit-ID: 9B8aA6lPpJX
3f80d2aaef435081f05551eae1a5c9b42302d56b: Bug 1455511: Always prune the accessibility tree for sliders. r=surkov
James Teh <jteh@mozilla.com> - Mon, 23 Apr 2018 17:23:00 +1000 - rev 788872
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1455511: Always prune the accessibility tree for sliders. r=surkov It doesn't make sense for a slider to have descendants and this confuses NVDA. MozReview-Commit-ID: 2A3gqTSu38g
bea414aba9b9e74cd5e1feecf63b1cf0bc240279: Bug 1457071 - allow all extension-storage data to be deleted from the profile. r=glasserc
Mark Hammond <mhammond@skippinet.com.au> - Thu, 26 Apr 2018 17:53:56 +1000 - rev 788871
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1457071 - allow all extension-storage data to be deleted from the profile. r=glasserc MozReview-Commit-ID: Dnb2kdcz1CH
8141b60030b908c1f291979d72e0f21db8206c5c: Bug 1454820 - Add support for system addon signing for web extension bundling. r=johannh,kmag
Jonathan Kingston <jkt@mozilla.com> - Wed, 18 Apr 2018 00:43:39 +0100 - rev 788870
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1454820 - Add support for system addon signing for web extension bundling. r=johannh,kmag MozReview-Commit-ID: 3dpQKGHOgLa
ab26e8e09fe50465702fd4f08fee67edf16a0e6b: Backed out changeset f8ad5962fc89 (bug 1435094) bustage in /builds/worker/workspace/build/src/layout/painting/nsDisplayList.cpp on a CLOSED TREE
Noemi Erli <nerli@mozilla.com> - Fri, 27 Apr 2018 04:14:39 +0300 - rev 788869
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Backed out changeset f8ad5962fc89 (bug 1435094) bustage in /builds/worker/workspace/build/src/layout/painting/nsDisplayList.cpp on a CLOSED TREE
a42293258ab3dffb794f3a1e8fe2c3937dd81bb5: Bug 1425866: Just null-check the CSS Loader for now. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 27 Apr 2018 01:46:50 +0200 - rev 788868
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1425866: Just null-check the CSS Loader for now. r=heycam After discussing with Olli there isn't any kind of severe problem out of this. Shadow subtrees will be disconnected just like the rest, and they shouldn't assume that the document hasn't been disconnected first. MozReview-Commit-ID: CX4fXOqEIFj
7d6abd1366c1060ca6b89e937a6e606c309f7105: Bug 1457316 - Inline the sendMessageToChrome implementation to avoid a dependency on paymentRequest.js in debugging.js. r=MattN
Sam Foster <sfoster@mozilla.com> - Thu, 26 Apr 2018 15:15:54 -0700 - rev 788867
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1457316 - Inline the sendMessageToChrome implementation to avoid a dependency on paymentRequest.js in debugging.js. r=MattN MozReview-Commit-ID: 2GgRQ6NI63d
a8fef63084795665c01e9753fb8647b71e9c0331: Bug 1457287 - Move Payment Request UI code to browser/. r=jaws
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Thu, 26 Apr 2018 16:57:02 -0700 - rev 788866
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1457287 - Move Payment Request UI code to browser/. r=jaws MozReview-Commit-ID: BUDOsda1kSE
ef26c00223691ade20d344707e30220580d664aa: Bug 1456703 - Remove nsIDOMXULTextBoxElement r=enndeakin+6102
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 26 Apr 2018 15:17:00 -0700 - rev 788865
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1456703 - Remove nsIDOMXULTextBoxElement r=enndeakin+6102 MozReview-Commit-ID: 6ZRzVq1bJjz
3e0ca85e69704884e8ff91b0ab4cbfa517d5bbd5: Bug 1456703 - Stop using nsIDOMXULTextBoxElement to detect XUL textboxes r=enndeakin+6102
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 26 Apr 2018 15:15:10 -0700 - rev 788864
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1456703 - Stop using nsIDOMXULTextBoxElement to detect XUL textboxes r=enndeakin+6102 This is used in JS via instanceof checks, and in C++ only to get the `inputField` attribute (the actual HTML input or textarea). We can swap out instanceof by checking the tag name, and we can directly query for the input field from C++. MozReview-Commit-ID: 7xpHQMYzYhD
a13c398c9213cee950cc214becfc4d5ea75e048b: Bug 1456496 - dark theme for onboarding snippets r=k88hudson
Ricky Rosario <rickyrosario@gmail.com> - Thu, 26 Apr 2018 12:51:42 -0400 - rev 788863
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1456496 - dark theme for onboarding snippets r=k88hudson MozReview-Commit-ID: CqprUlxd2IZ
1b3d3412d21063418454b851af3d85943c8f7110: Bug 1455322 - Allow TPS ping validation to be disabled by the `testing.tps.skipPingValidation` preference r=markh
Thom Chiovoloni <tchiovoloni@mozilla.com> - Tue, 24 Apr 2018 11:16:27 -0700 - rev 788862
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1455322 - Allow TPS ping validation to be disabled by the `testing.tps.skipPingValidation` preference r=markh MozReview-Commit-ID: 66KgorRWaC
3ece4329ec731cb6c1d1238007f8206ca0688fa2: Bug 1438375 - Refactor "extensionControlled" Preferences code to use Fluent. r=flod,Gijs
Zibi Braniecki <zbraniecki@mozilla.com> - Tue, 17 Apr 2018 15:31:50 -0700 - rev 788861
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1438375 - Refactor "extensionControlled" Preferences code to use Fluent. r=flod,Gijs MozReview-Commit-ID: 9XJxyuMUCHV
50355ef2f138470db57e71389bf6372c957e02b4: Bug 1457120 - Use mozilla:: namespace at nsLookAndFeel module, r=jhorak
Martin Stransky <stransky@redhat.com> - Thu, 26 Apr 2018 14:59:55 +0200 - rev 788860
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1457120 - Use mozilla:: namespace at nsLookAndFeel module, r=jhorak MozReview-Commit-ID: BXZzDAiY0e4
f8ad5962fc897cbec562226fb23aa361dadcfa0a: Bug 1435094 - wire up GlyphRasterSpace to nsDisplayTransform. r=kats,mstange
Alexis Beingessner <a.beingessner@gmail.com> - Wed, 25 Apr 2018 10:47:34 -0400 - rev 788859
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1435094 - wire up GlyphRasterSpace to nsDisplayTransform. r=kats,mstange When a transform thinks it's animated we should abandon screen rasterization and instead favour local rasterization. This produces a more visually pleasant rendering, as pixel-snapping "wobbles" the text between frames. The float scale of GlyphRasterSpace::Local is currently unused, but this PR tries its best to set it to a reasonable value, based on discussion with glennw about the intended semantics. We agreed it should specify the scale *relative* to the parent stacking context, which means it's just whatever scaling the stacking context's transform applies. It's possible we'll need to clamp this value or make it properly 2-dimensional later on. Some book-keeping is added to StackingContextHelper to ensure that GlyphRasterSpace::Screen is never requested by a descendent of a stacking context using GlyphRasterSpace::Local. nsDisplayMask is changed to use a StackingContextHelper to ensure rasterSpace is properly propagated. In addition, this is the first commit making use of cbindgen's new support for bridging Rust enums natively into C++! This bumps our minimum cbindgen to 6.0.0 (just released). MozReview-Commit-ID: 9AlsB6nUheB
9806b8af0e6fbc1f3ef63da5c55ea68bd5afee2d: Bug 1457102: Ensure a style flush happens after a compat mode change. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 26 Apr 2018 16:11:48 +0200 - rev 788858
Push 108098 by mozilla@noorenberghe.ca at Fri, 27 Apr 2018 03:35:30 +0000
Bug 1457102: Ensure a style flush happens after a compat mode change. r=heycam This is the actual fix. The compat mode changed (well, it didn't), but we were not scheduling a style flush. Then someone called getComputedStyle on an element in this document, and the styles were thought clean, thus we didn't flush style, and we assert when style resolution happened. MozReview-Commit-ID: KkM6NwzD640
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip