33c2241696c07a203f5355771a40a8c28a0767b5: Bug 1311515 - include information on whether system is at risk of bug 1296630 in the update ping. r=felipc
Robert Strong <robert.bugzilla@gmail.com> - Fri, 28 Oct 2016 13:57:17 -0700 - rev 320078
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1311515 - include information on whether system is at risk of bug 1296630 in the update ping. r=felipc
0a1486cf11b228e41d27499b79b1e3ea6be3e28f: Bug 1297790 - Add telemetry probes for GPU process launch/launch-time/abort r=dvander
George Wright <george@mozilla.com> - Thu, 20 Oct 2016 11:33:40 -0400 - rev 320077
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1297790 - Add telemetry probes for GPU process launch/launch-time/abort r=dvander
73aacf4a8f568cfd66a7a306cce0879bbdd5de5b: Bug 1303333 - Implement the probe to count URI loads triggered by search. r=mak, data-review=rweiss
Alessio Placitelli <alessio.placitelli@gmail.com> - Fri, 28 Oct 2016 13:13:00 +0200 - rev 320076
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1303333 - Implement the probe to count URI loads triggered by search. r=mak, data-review=rweiss MozReview-Commit-ID: 3toynbrFeLP
683d731aad23ced97d7ba5f0e16400fc570a4454: Bug 1300550 - IonMonkey - Don't overflow BufferOffsets, r=sstangl
Hannes Verschore <hv1989@gmail.com> - Fri, 28 Oct 2016 21:44:40 +0200 - rev 320075
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1300550 - IonMonkey - Don't overflow BufferOffsets, r=sstangl
d77c9965e9b287150fcc5fc23d386a9ade278bd2: Bug 1281759 - Try to work around mysterious AMD crashes (take 2). r=jandem
Hannes Verschore <hv1989@gmail.com> - Fri, 28 Oct 2016 21:44:39 +0200 - rev 320074
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1281759 - Try to work around mysterious AMD crashes (take 2). r=jandem
3ecd7c2308e72d85b9797458c1d2594ade5458c3: Bug 1310778 - Move TabGroup and GetDocGroup accessors onto nsPIDOMWindow{Inner,Outer}, r=smaug
Michael Layzell <michael@thelayzells.com> - Fri, 28 Oct 2016 14:10:32 -0400 - rev 320073
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1310778 - Move TabGroup and GetDocGroup accessors onto nsPIDOMWindow{Inner,Outer}, r=smaug MozReview-Commit-ID: Hl0QVktr0Lw
288d92c34790593a91aadb83e0e578bdd8ec4b39: Bug 1311921 - Store base and relative URIs explicitly in nsStyleImageRequests for comparison purposes, rather than use css::ImageValues. r=bholley
Cameron McCormack <cam@mcc.id.au> - Fri, 28 Oct 2016 14:34:33 +0800 - rev 320072
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1311921 - Store base and relative URIs explicitly in nsStyleImageRequests for comparison purposes, rather than use css::ImageValues. r=bholley MozReview-Commit-ID: 5aArKCI7Rhx
9f0e99ac3fca2edfe9ba5964b20cabff6a0c3705: Bug 1312416 - use tabbrowser message manager group to listen for decoder doctor messages, r=jaws
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Fri, 28 Oct 2016 18:15:30 +0100 - rev 320071
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1312416 - use tabbrowser message manager group to listen for decoder doctor messages, r=jaws For browsers in e.g. panels, we can't really make decoder doctor work well, so we simply elect to only listen for such messages within tabbrowser browsers. MozReview-Commit-ID: Frrhf6AOgAy
97db1163c72973f0027e25591b09819a903c2b50: Bug 1305534 - Add debug artifact builds on try; r=chmanchester
Maja Frydrychowicz <mjzffr@gmail.com> - Tue, 18 Oct 2016 11:18:58 -0400 - rev 320070
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1305534 - Add debug artifact builds on try; r=chmanchester MozReview-Commit-ID: Gg46RzHarO1
425c0602ccb486822c4974aa5f7d367597d2b259: Bug 1313716 - Don't provide a blank subsuite as a default in the manifestparser. r=ahal
Chris Manchester <cmanchester@mozilla.com> - Fri, 28 Oct 2016 11:07:21 -0700 - rev 320069
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1313716 - Don't provide a blank subsuite as a default in the manifestparser. r=ahal This causes consumers managing defaults themselves to fail to find a default subsuite for tests, because the manifestparser will have provided a blank default value by the time they incorporate defaults into a test definition. This patch removes the provided defaults and updates a number of places assuming the 'subsuite' field is always present. MozReview-Commit-ID: 1jPy52VmEPr
c2b23c06acfe4086c26e844ffb9bd94e01c6a252: Backed out 3 changesets (bug 1252871) for test_ext_all_apis.html bustage a=backout CLOSED TREE
Wes Kocher <wkocher@mozilla.com> - Fri, 28 Oct 2016 14:24:13 -0700 - rev 320068
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Backed out 3 changesets (bug 1252871) for test_ext_all_apis.html bustage a=backout CLOSED TREE Backed out changeset b3a08a040c8a (bug 1252871) Backed out changeset c2a511511a72 (bug 1252871) Backed out changeset 9c2c3780aa4c (bug 1252871)
c456c1797299e5dfc39187992e30c323f7d92ee1: Bug 1299411 - Error messages for native messaging r=aswan
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:45:02 +0200 - rev 320067
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Error messages for native messaging r=aswan - Combine the errors for a non-existing app and lacking permissions to avoid information leakage. - Do not treat normal application exit as an error. - Create errors in the right context. - Add tests that check the error messages. MozReview-Commit-ID: HxBpeCSyyGN
ed1afd2aad61c64bb938cf1647975b4fda846d66: Bug 1299411 - Move native messaging to child process r=kmag
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:25:56 +0200 - rev 320066
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Move native messaging to child process r=kmag Move `runtime.connectNative` and `runtime.sendNativeMessage` to `addon_child`. Note: This does not change the behavior for launching the native app, it is still launched from the main process. Now ExtensionUtils's Port is also used for native messaging ports. Now the behavior of `runtime.connect` and `runtime.connectNative` are identical from the extension's perspective. In particular: - `disconnect()` does not throw when called again (bug 1287229). - `onDisconnect` is called with error messages (tests will be added in the next commit). MozReview-Commit-ID: AyU9amiLeoL
24d81c7b335e8cb1949efb2b27a978cf108de705: Bug 1299411 - s/on/once/ in NativeApp's sendMessage r=aswan
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:22:31 +0200 - rev 320065
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - s/on/once/ in NativeApp's sendMessage r=aswan This communicates more clearly that we expect only one message/event. MozReview-Commit-ID: 8jDYBVwqQtz
2829c46a636d7a2b77a88df0b9fbe36182fa836d: Bug 1299411 - Remove extension param from NativeApp r=aswan
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:18:48 +0200 - rev 320064
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Remove extension param from NativeApp r=aswan The extension is always available as `context.extension`, so do not unnecessarily pass the extension as a separate parameter. MozReview-Commit-ID: 9OaestUAGVk
57f7a5c7044db9fba2cd039773ac058b7269aac5: Bug 1299411 - Deduplicate context getter logic in ParentAPIManager r=aswan
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:10:39 +0200 - rev 320063
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Deduplicate context getter logic in ParentAPIManager r=aswan MozReview-Commit-ID: E9MpHhal7WF
a9c19ee017a44aeb9953858b663a100a85ccffab: Bug 1299411 - separate serialization from sending r=aswan
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:03:20 +0200 - rev 320062
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - separate serialization from sending r=aswan Serialization of the message should happen in the same process as the extension context, whereas sending the message should be in the same process as the owner of the native messaging host. With webext-oop, the former is an addon process and the latter the main process. Therefore it is necessary to separate the two roles. MozReview-Commit-ID: 8BJZmn2QjLJ
0ce4a6653d1966333fa72a29f762fdde5614d02f: Bug 1299411 - Propagate errors to port.onDisconnect via port.error r=kmag
Rob Wu <rob@robwu.nl> - Fri, 30 Sep 2016 22:42:28 +0200 - rev 320061
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Propagate errors to port.onDisconnect via port.error r=kmag In Chrome, runtime.lastError is set when the port is disconnected due to an error. Here in Firefox we choose to set a new property "error" on the port if the port disconnected due to an error. Since onDisconnect fires at most once, port.error is set only once. MozReview-Commit-ID: EPaVtV4WkcQ
e08ee4c2b1e2a0f9020f9a02f5c0ded4b1aa4ab2: Bug 1299411 - Unify fire and fireWithoutClone. r=kmag
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 11:48:43 +0200 - rev 320060
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Unify fire and fireWithoutClone. r=kmag Unify implementation of fire and fireWithoutClone. `fireWithoutClone` was running the callbacks synchronously. After this commit the callback is run asynchronously. This is safe because the only user of this method is `Port`'s `onDisconnect`. MozReview-Commit-ID: 1kiYavsu3e7
502aaf0691ccecb5988d719cf904fb52c992dce3: Bug 1299411 - Pass port parameter to port.onMessage r=kmag
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 11:34:26 +0200 - rev 320059
Push 20749 by ryanvm@gmail.com at Sat, 29 Oct 2016 13:21:21 +0000
Bug 1299411 - Pass port parameter to port.onMessage r=kmag This should have been a part of bug 1298810, but that only set the argument for native messaging ports, which does not use Port from ExtensionUtils. The port parameter must also be included in runtime's Port.onMessage to avoid regressions when the port implementations are unified and native messaging starts using runtime's Port. Note that starting from this commit, multiple onMessage listeners receive the same (cloned) message instead of a new clone per listener. This is a side effect of using `fire.withoutClone` instead of `fire`: `fire` clones all parameters, but ports are not cloneable so we have to use `fire.withoutClone` instead. This change with regards to message cloning is fully compatible with Chrome's messaging API (which also passes the same message object to all `port.onMessage` calls). MozReview-Commit-ID: AUDuUKHkXCM
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 tip