21f71652e49132a779ceccba50f92765a38154c1: Bug 1336322 NativeKey::GetFollowingCharMessage() should treat the char message has gone if PeekMessage() failed to remove found char message and next key message becomes non-char message or different key's char message r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 03 Feb 2017 14:30:22 +0900 - rev 479297
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1336322 NativeKey::GetFollowingCharMessage() should treat the char message has gone if PeekMessage() failed to remove found char message and next key message becomes non-char message or different key's char message r=m_kato This patch depends on bug 1336080. When PeekMessage() fails to remove found char message, NativeKey::GetFollowingCharMessage() tries to check next key message in the queue again. Then, when next key message becomes non-char message, such as WM_KEYDOWN or WM_KEYUP, the char message must be removed by odd keyboard layout or something. Similarly, when next key message is a char message but it's caused by different key, the found char message must be removed by one of them too. So, in these cases, NativeKey::GetFollowingCharMessage() should treat the key operation is already handled or canceled by the odd keyboard layout or somebody else. Additionally, in the latter case, following char message should be handled as orphan char message(s) as usual. MozReview-Commit-ID: 8ahs8I0HUQ2
6c56e3e2d6675be68f4164feaddbff6694293e97: Backed out 2 changesets (bug 1336345) for gtest timeouts and crashes in test_data_protocol_registration.js
Phil Ringnalda <philringnalda@gmail.com> - Sun, 05 Feb 2017 20:40:19 -0800 - rev 479296
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Backed out 2 changesets (bug 1336345) for gtest timeouts and crashes in test_data_protocol_registration.js CLOSED TREE Backed out changeset c4247e22a8ff (bug 1336345) Backed out changeset 05e8e7d0f430 (bug 1336345)
e37b1547760353cd23ef7467c9e77389307bafa8: Bug 1336080 When NativeKey::GetFollowingCharMessage() founds different message when it fails to remove a found char message, it should retry to remove the newly found message if it's caused by same physical key r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 02 Feb 2017 23:26:45 +0900 - rev 479295
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1336080 When NativeKey::GetFollowingCharMessage() founds different message when it fails to remove a found char message, it should retry to remove the newly found message if it's caused by same physical key r=m_kato When NativeKey::GetFollowingCharMessage() tries to remove a char message from the queue, the message might be changed by odd keyboard layout or something. In such case, if the new char message is also caused by same physical key, the char message must be overwritten. Then, we should take the new char message instead. Note that this patch saves original found char message into kFoundCharMsg and it's logged by each points for indicating if this case has occurred. MozReview-Commit-ID: HAduq8sfwFt
c4247e22a8ffd809c8f8489bfff77f6d2b0213aa: Bug 1336345. Part 2 - some code cleanup. r=gerald
JW Wang <jwwang@mozilla.com> - Fri, 03 Feb 2017 15:16:50 +0800 - rev 479294
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1336345. Part 2 - some code cleanup. r=gerald MozReview-Commit-ID: 1XHkvz4aWxB
05e8e7d0f430d5cd3a277432fabbca259af80248: Bug 1336345. Part 1 - register shutdown blocker on startup. r=gerald
JW Wang <jwwang@mozilla.com> - Fri, 03 Feb 2017 15:12:22 +0800 - rev 479293
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1336345. Part 1 - register shutdown blocker on startup. r=gerald MozReview-Commit-ID: 80DEZEEhm9E
78d1347fb9f6533a4470087a440a3c9ab2dec354: Bug 1336309 - modify the access key for 'play tab' option. r=jaws
Alastor Wu <alwu@mozilla.com> - Mon, 06 Feb 2017 10:21:19 +0800 - rev 479292
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1336309 - modify the access key for 'play tab' option. r=jaws Because the key "P" was already used by "pin tab", we need to change the access key. MozReview-Commit-ID: Igzs6cv1bLj
f826282b1d21e8af778750e8d543897bc9be4aa1: Merge m-c to autoland
Phil Ringnalda <philringnalda@gmail.com> - Sun, 05 Feb 2017 18:18:52 -0800 - rev 479291
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Merge m-c to autoland
ff9f57defc040b9a41a7b96361b5b286d2acff90: Bug 1319987: P12. Disable RemoteDataDecoder. ?jhlin r=jya
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 03 Feb 2017 09:40:28 +0100 - rev 479290
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P12. Disable RemoteDataDecoder. ?jhlin r=jya There appears to be a race occurring where InputExhausted callback isn't always called. The issue could be reproduced prior all those changes, albeit rarely. The tracking of re-enabling this feature will be done in bug 1336358 MozReview-Commit-ID: 5rPpcCcgNIq
8f062bf0099d2809e5f7cf2fcbaed09c01c74112: Bug 1319987: P11. Fix MediaDataDecoder gtest. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 31 Jan 2017 20:43:07 +0100 - rev 479289
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P11. Fix MediaDataDecoder gtest. r=gerald They appear to have been broken for a while. Several months at least. MozReview-Commit-ID: I71xE91UMOZ
d42edade7ed89be77315be5510839d7047ad6b55: Bug 1319987: P10. Update WPT expected results. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Sun, 29 Jan 2017 21:56:29 +0100 - rev 479288
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P10. Update WPT expected results. r=gerald MozReview-Commit-ID: BWEk7Ri0iyc
7ab9b3dd619c4dc06cf03e7e29ed5e5b0cce90a0: Bug 1319987: P9. More coding style fixes. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 27 Jan 2017 13:20:37 +0100 - rev 479287
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P9. More coding style fixes. r=gerald MozReview-Commit-ID: DhFRqkWQZny
b45df222b0ee0f70948497c1f6455c0f1b58ac40: Bug 1319987: P8. Fix comment. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 27 Jan 2017 11:48:43 +0100 - rev 479286
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P8. Fix comment. r=gerald MozReview-Commit-ID: BXZBHdEAY8Z
3f1edb00f34363f5d577477114b5cca4c6b90608: Bug 1319987: P7. Re-implement handling for WaitingForKey in MFR. r=cpearce,gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 27 Jan 2017 11:48:00 +0100 - rev 479285
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P7. Re-implement handling for WaitingForKey in MFR. r=cpearce,gerald MozReview-Commit-ID: FCiAO54oiH3
c523a15a402fc752e4c6f0eb4cc8d9930342f425: Bug 1319987: P6. Shutdown demuxer asynchronously. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 26 Jan 2017 18:17:15 +0100 - rev 479284
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P6. Shutdown demuxer asynchronously. r=gerald This prevents the demuxer attempting to use the parent resources once the parent has been shutdown. MozReview-Commit-ID: LQqPxBkAfAS
b2171e3e8b6971c434a1c1424fac1484fe322351: Bug 1319987: P5. Promisify MediaDataDecoder. r=cpearce,gerald,mattwoodrow,snorp
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 26 Jan 2017 13:56:46 +0100 - rev 479283
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P5. Promisify MediaDataDecoder. r=cpearce,gerald,mattwoodrow,snorp This is a big change, and unfortunately impossible to break down with independently functional commits. There are four main changes being applied here: * Code cleanup, including making all MediaDataDecoder related code mozilla coding style compliant * Make MediaDataDecoder use MozPromise * Making Flush and Shutdown processes fully asynchronous * Fixing few data races encountered across the code, in particular in the Android PDM MozReview-Commit-ID: DpiZucGofJT
66f93142128809dc9c49dcc5a9d54f6dd08b6196: Bug 1319987: P4. Refactor H264 Converter. r=cpearce
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 30 Dec 2016 21:51:42 +1100 - rev 479282
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P4. Refactor H264 Converter. r=cpearce We can make some assumptions now that the Input method is only called once and never again while a decode is pending. MozReview-Commit-ID: EmzKEcwNY2J
1a05ce09ead4d92544fe31cd24639240f60e63f4: Bug 1319987: P3. Remove Gonk PDM. r=cpearce
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 30 Dec 2016 01:26:12 +1100 - rev 479281
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P3. Remove Gonk PDM. r=cpearce The platform is no longer supported, and the promisifying of the MediaDataDecoder makes it not worthwhile to continue maintenance. MozReview-Commit-ID: FjDzRk5YQp3
fd747ba4db0843f9a87d4364f68bb20f73f084ef: Bug 1319987: P2. Remove FuzzingWrapper. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 21 Dec 2016 10:52:01 +1100 - rev 479280
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P2. Remove FuzzingWrapper. r=gerald It is no longer used and in its current state incompatible with promise based decoders. We'll re-add it later. MozReview-Commit-ID: DHsyTsFvTZB
20e6f90089fadb1c946894445a5b663922eb4ca1: Bug 1319987: P1. Remove handling for WaitingForKey in MFR. r=cpearce
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 20 Dec 2016 18:53:39 +1100 - rev 479279
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Bug 1319987: P1. Remove handling for WaitingForKey in MFR. r=cpearce This is not compatible with promise based decoders. We'll re-implement it in a different fashion later on. MozReview-Commit-ID: HYBNKVxEUmB
951bab16551ab166d754f8c8fcea69fda7d98773: Backed out changeset 70253d6678af (bug 1295072) for failures in browser_ext_tabs_create.js
Phil Ringnalda <philringnalda@gmail.com> - Sun, 05 Feb 2017 13:23:21 -0800 - rev 479278
Push 44211 by bmo:hskupin@gmail.com at Mon, 06 Feb 2017 12:18:11 +0000
Backed out changeset 70253d6678af (bug 1295072) for failures in browser_ext_tabs_create.js
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip