c5284f9b8e20280e559dcb4c85630af67e1ae898: Bug 1312886: [MSE] P4. Only rely on waiting promise to determine buffering state. r?jwwang draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 27 Oct 2016 20:16:30 +1100 - rev 430589
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1312886: [MSE] P4. Only rely on waiting promise to determine buffering state. r?jwwang MozReview-Commit-ID: 3HfK8bwqlYM
0cd9ffb77d871fbcb1727d56de4a6c332f538d7d: Bug 1312886: P3. Always compute start time with ADTS. r?kamidphish draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 27 Oct 2016 20:12:29 +1100 - rev 430588
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1312886: P3. Always compute start time with ADTS. r?kamidphish This was originally copied from the MP3Demuxer and was only required to work around an issue now fixed. Only MSE should set ShoultComputeStartTime to false, even if the ADTS demuxer always returns a first sample with a time of 0. MozReview-Commit-ID: DMRLpxC5mU1
83a2a4070cfcd8c3cb065761e40c9d94eba8e0cf: Bug 1312886: P2. Never move past HAVE_FUTURE_DATA if we're waiting for a key, r?cpearce draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 27 Oct 2016 16:36:37 +1100 - rev 430587
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1312886: P2. Never move past HAVE_FUTURE_DATA if we're waiting for a key, r?cpearce MozReview-Commit-ID: KWERB7zWXPZ
96c84230fc7fbe98ea83b590e79e64fc4b196254: Bug 1312886: P1. Fix comments. r?cpearce draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 27 Oct 2016 10:05:21 +1100 - rev 430586
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1312886: P1. Fix comments. r?cpearce A MediaDataDecoder now always call InputExhausted once decoding is completed. MozReview-Commit-ID: K6SCRYb2ieI
7862f7d272567d284cea8665d12258c758c9f439: Bug 1313284 - Update some EME WPT to match upstream so that they now pass. r=gerald draft
Chris Pearce <cpearce@mozilla.com> - Thu, 27 Oct 2016 19:08:12 +1300 - rev 430585
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1313284 - Update some EME WPT to match upstream so that they now pass. r=gerald We now pass almost all the upstream EME WPT, but out local copy is out of date, so we're failing some. So rather than mark them as expected fail, update the out copy so that the tests pass as expected. MozReview-Commit-ID: 7YnD6Dlc0HC
2f734e16ec1cb497d0251bdd6d8bf53bf62f9e91: Bug 1313284 - Disable EME WPT for features we don't support, or can't support in the test harness. r=gerald draft
Chris Pearce <cpearce@mozilla.com> - Thu, 27 Oct 2016 16:53:07 +1300 - rev 430584
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1313284 - Disable EME WPT for features we don't support, or can't support in the test harness. r=gerald MozReview-Commit-ID: 51T4hBjezyr
c9fb674f3cb8dff4fe8734e0426e67825878015d: Bug 1308821 - Ensure ClearKey doesn't parse a keyids initdata format session type parameter. r=kikuo draft
Chris Pearce <cpearce@mozilla.com> - Sun, 09 Oct 2016 20:42:01 -0700 - rev 430583
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1308821 - Ensure ClearKey doesn't parse a keyids initdata format session type parameter. r=kikuo The specification doesn't require there to be a 'type' member of the keyids init data format. MozReview-Commit-ID: 7mOm7KwyyuC
6d50c9068b52d8846e4d528d150f3f3dbd9a233d: Bug 1313266 - Make gmp-clearkey reject with TypeError instead of InvalidAccessError on invalid input. r=gerald draft
Chris Pearce <cpearce@mozilla.com> - Thu, 27 Oct 2016 14:59:02 +1300 - rev 430582
Push 33854 by cpearce@mozilla.com at Fri, 28 Oct 2016 00:30:37 +0000
Bug 1313266 - Make gmp-clearkey reject with TypeError instead of InvalidAccessError on invalid input. r=gerald The spec expects this, and now we pass more web platform tests. MozReview-Commit-ID: 9HJFp2ebczk
ec09a6772df798982fc2d52153186fd901a3984c: Bug 1308421: Handle MessageChannel responses correctly after docshells have been swapped. r?aswan draft
Kris Maglione <maglione.k@gmail.com> - Tue, 11 Oct 2016 21:08:33 +0100 - rev 430581
Push 33853 by maglione.k@gmail.com at Fri, 28 Oct 2016 00:00:28 +0000
Bug 1308421: Handle MessageChannel responses correctly after docshells have been swapped. r?aswan MozReview-Commit-ID: HDTrBfdclXd
51bfff5945939cca1b236c8d331827928d4258e1: Bug 1299411 - Error messages for native messaging draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:45:02 +0200 - rev 430580
Push 33852 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:49:10 +0000
Bug 1299411 - Error messages for native messaging - 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
850bd07df0b6d5192d67071137288e277dd37665: Bug 1299411 - Move native messaging to child process draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:25:56 +0200 - rev 430579
Push 33852 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:49:10 +0000
Bug 1299411 - Move native messaging to child process 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
c80f42dfd92ba5ebec1c2fc86f3b64c1bb4bc971: Bug 1313527: exit red parser loop if stroul failed. r=mjf draft
Nils Ohlmeier [:drno] <drno@ohlmeier.org> - Thu, 27 Oct 2016 16:48:10 -0700 - rev 430578
Push 33851 by drno@ohlmeier.org at Thu, 27 Oct 2016 23:48:59 +0000
Bug 1313527: exit red parser loop if stroul failed. r=mjf MozReview-Commit-ID: JaRO7F7tz0j
97136e8ef20a61130154af695ec09598e91078c5: Bug 1309641: only store a single pre-answer request per 5 tuple. r=bwc draft
Nils Ohlmeier [:drno] <drno@ohlmeier.org> - Wed, 26 Oct 2016 21:43:27 -0700 - rev 430577
Push 33851 by drno@ohlmeier.org at Thu, 27 Oct 2016 23:48:59 +0000
Bug 1309641: only store a single pre-answer request per 5 tuple. r=bwc MozReview-Commit-ID: KzrGGRRU28J
e92a259df86e0b20fe579647364e4dbb757f4a54: Bug 1299411 - Error messages for native messaging draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:45:02 +0200 - rev 430576
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - Error messages for native messaging - 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
6d321ed855dda97b4ebfff9c558145cbb1419b9b: Bug 1299411 - Move native messaging to child process draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:25:56 +0200 - rev 430575
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - Move native messaging to child process 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
b23f234bc5b04c82cc6946bdfa13791a59262701: Bug 1299411 - s/on/once/ in NativeApp's sendMessage draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:22:31 +0200 - rev 430574
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - s/on/once/ in NativeApp's sendMessage This communicates more clearly that we expect only one message/event. MozReview-Commit-ID: 8jDYBVwqQtz
7f42500ed69866d6514b12e4a5687828c027bf71: Bug 1299411 - Remove extension param from NativeApp draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:18:48 +0200 - rev 430573
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - Remove extension param from NativeApp The extension is always available as `context.extension`, so do not unnecessarily pass the extension as a separate parameter. MozReview-Commit-ID: 9OaestUAGVk
6130a74a09b576560d6f8361ec4c865daf7abe64: Bug 1299411 - Deduplicate context getter logic in ParentAPIManager draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:10:39 +0200 - rev 430572
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - Deduplicate context getter logic in ParentAPIManager MozReview-Commit-ID: E9MpHhal7WF
e6f29fea8ecd0d24e8fcb046a80ae21f256b980a: Bug 1299411 - separate serialization from sending draft
Rob Wu <rob@robwu.nl> - Sat, 24 Sep 2016 13:03:20 +0200 - rev 430571
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - separate serialization from sending 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
8b3b2a7da7d6167a6ba86ecd8f63ef1c0f2a38c9: Bug 1299411 - Propagate errors to port.onDisconnect via port.error draft
Rob Wu <rob@robwu.nl> - Fri, 30 Sep 2016 22:42:28 +0200 - rev 430570
Push 33850 by bmo:rob@robwu.nl at Thu, 27 Oct 2016 23:41:10 +0000
Bug 1299411 - Propagate errors to port.onDisconnect via port.error 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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip