c5621cb6f9075d731ccb28dcf20dd29deae2bddd: Bug 1333303 - Remove the google4 dir from the test and relax the list comparison. r=whimboo
Francois Marier <francois@mozilla.com> - Wed, 25 Jan 2017 15:45:12 -0800 - rev 340878
Push 36941 by hskupin@mozilla.com at Mon, 06 Feb 2017 08:01:44 +0000
Bug 1333303 - Remove the google4 dir from the test and relax the list comparison. r=whimboo MozReview-Commit-ID: 2KY6CEQZYOk
0cdf5249e6d06897c0ffec56a6675dc971a16847: Bug 1321502 - part 2: Use preferred layout for initializing cubeb when audio queue is empty; r=jya
Chun-Min Chang <chun.m.chang@gmail.com> - Sat, 04 Feb 2017 08:22:15 +0800 - rev 340877
Push 36940 by ihsiao@mozilla.com at Mon, 06 Feb 2017 07:55:46 +0000
Bug 1321502 - part 2: Use preferred layout for initializing cubeb when audio queue is empty; r=jya MozReview-Commit-ID: BDEb8IxuJRn
401683745308733d1ec980b6ba4cab53c7f38bd5: Bug 1321502 - part 1: Enable multi-channel support in Gecko on Windows; r=jya
Chun-Min Chang <chun.m.chang@gmail.com> - Thu, 26 Jan 2017 17:35:31 +0800 - rev 340876
Push 36940 by ihsiao@mozilla.com at Mon, 06 Feb 2017 07:55:46 +0000
Bug 1321502 - part 1: Enable multi-channel support in Gecko on Windows; r=jya MozReview-Commit-ID: KURUk3EffOu
3504f8cdd850178af9a2f2a5a1361a8e347a87e6: Bug 1336331 NativeKey::GetFollowingCharMessage() should try to use GetMessage() when PeekMessage() failed to remove a char message from the queue and there is still existing a char message r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 03 Feb 2017 18:01:33 +0900 - rev 340875
Push 36939 by masayuki@d-toybox.com at Mon, 06 Feb 2017 07:38:01 +0000
Bug 1336331 NativeKey::GetFollowingCharMessage() should try to use GetMessage() when PeekMessage() failed to remove a char message from the queue and there is still existing a char message r=m_kato I think that when PeekMessage(PM_REMOVE) failed to remove a char message but next key message is still a char message, it may be possible that the odd keyboard layout or utility hook only PeekMessage(PM_NOREMOVE) and GetMessage(). If so, we can explain what occurs in this case. I'm still not sure this fixes the case of bug 1336322 comment 0, but we should try to do this because I don't have better idea. MozReview-Commit-ID: CxoO24n167t
448a2d9d62c2951f6da51cd9ff5aa96ac88c67e8: Bug 1336349 - Merge GetIsDocumentEditable implementation to EditorBase. r=masayuki
Makoto Kato <m_kato@ga2.so-net.ne.jp> - Fri, 03 Feb 2017 16:22:50 +0900 - rev 340874
Push 36938 by m_kato@ga2.so-net.ne.jp at Mon, 06 Feb 2017 05:00:05 +0000
Bug 1336349 - Merge GetIsDocumentEditable implementation to EditorBase. r=masayuki GetIsDocumentEditable is implemnted in EditorBase, TextEditor, and HTMLEditor. This is virtual method, we won't use EditorBase::GetIsDocumentEditable. Also, TextEditor::GetIsDocumentEditable and HTMLEditor::GetIsDocumentEditable are same implementation. So we should merge this to EditorBase. MozReview-Commit-ID: 62euqUaYAuY
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 340873
Push 36937 by masayuki@d-toybox.com at Mon, 06 Feb 2017 04:54:14 +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 340872
Push 36936 by philringnalda@gmail.com at Mon, 06 Feb 2017 04:40:27 +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 340871
Push 36935 by masayuki@d-toybox.com at Mon, 06 Feb 2017 04:10:26 +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 340870
Push 36934 by jwwang@mozilla.com at Mon, 06 Feb 2017 03:26:18 +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 340869
Push 36934 by jwwang@mozilla.com at Mon, 06 Feb 2017 03:26:18 +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 340868
Push 36933 by alwu@mozilla.com at Mon, 06 Feb 2017 02:23:47 +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 340867
Push 36932 by philringnalda@gmail.com at Mon, 06 Feb 2017 02:19:01 +0000
Merge m-c to autoland
20a8536b0bfac74389d3a57bd8dd957d98779ce1: Backed out changeset c13c36e04303 (bug 1332295) for extremely frequent Linux32 debug failures in test_be_conservative.js
Phil Ringnalda <philringnalda@gmail.com> - Sun, 05 Feb 2017 18:18:09 -0800 - rev 340866
Push 36932 by philringnalda@gmail.com at Mon, 06 Feb 2017 02:19:01 +0000
Backed out changeset c13c36e04303 (bug 1332295) for extremely frequent Linux32 debug failures in test_be_conservative.js
ff9f57defc040b9a41a7b96361b5b286d2acff90: Bug 1319987: P12. Disable RemoteDataDecoder. ?jhlin r=jya
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 03 Feb 2017 09:40:28 +0100 - rev 340865
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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 340864
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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 340863
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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 340862
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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 340861
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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 340860
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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 340859
Push 36931 by jyavenard@mozilla.com at Sun, 05 Feb 2017 22:50:36 +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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip