ea305bed5459d13496dabd8d491a19bf4320cbd1: Bug 1362617 - Generalize MOZ_CHROME_MULTILOCALE to work for browser as well. r?ted draft
Zibi Braniecki <zbraniecki@mozilla.com> - Tue, 30 May 2017 10:30:26 +0200 - rev 605212
Push 67326 by bmo:gandalf@aviary.pl at Fri, 07 Jul 2017 06:54:22 +0000
Bug 1362617 - Generalize MOZ_CHROME_MULTILOCALE to work for browser as well. r?ted In order to get Firefox to work with multiple built-in languages, we want to bundle the same file in desktop as we do in fennec - res/multilocale.json MozReview-Commit-ID: BY1cMYd0q8Q
f89f8b5ae3a92b81ff1f6cb785fa01fad6064b7d: Bug 1274919 - part4 : add test. draft
Alastor Wu <alwu@mozilla.com> - Fri, 07 Jul 2017 14:36:14 +0800 - rev 605211
Push 67325 by alwu@mozilla.com at Fri, 07 Jul 2017 06:37:01 +0000
Bug 1274919 - part4 : add test. MozReview-Commit-ID: 5wKkE5tphLl
ef2aa0456882f9962f8ce849190fcf6178b38bce: Bug 1274919 - part3 : only notify the tab with suspened video to resume video decoding. draft
Alastor Wu <alwu@mozilla.com> - Fri, 07 Jul 2017 14:34:57 +0800 - rev 605210
Push 67325 by alwu@mozilla.com at Fri, 07 Jul 2017 06:37:01 +0000
Bug 1274919 - part3 : only notify the tab with suspened video to resume video decoding. If the tab doesn't contain any suspended video, we don't need to notify it to be resumed. MozReview-Commit-ID: AaBeAIYYwim
dd972b0cf98504c748544e9e5f13d9ff45dc9b8f: Bug 1274919 - part2 : implement resume/suspend mechanism in MediaDecoder. draft
Alastor Wu <alwu@mozilla.com> - Fri, 07 Jul 2017 14:33:55 +0800 - rev 605209
Push 67325 by alwu@mozilla.com at Fri, 07 Jul 2017 06:37:01 +0000
Bug 1274919 - part2 : implement resume/suspend mechanism in MediaDecoder. Create the new class "VideoDecodingRecoveringObserver" to handle the suspended request sent from the front end side. When the video decoding starts being suspended, we would start the observer. When the video decoding starts being resumed and it's not caused by the front end side, we would stop the observer. MozReview-Commit-ID: AjwIQKCNDpy
ca0a1d2fbd4837091d3915fcdb5352a355bf44bb: Bug 1274919 - part1 : resume video decoding when cursor is hovering over the tab, and suspend it again when cursor leaves the tab. draft
Alastor Wu <alwu@mozilla.com> - Fri, 07 Jul 2017 14:20:45 +0800 - rev 605208
Push 67325 by alwu@mozilla.com at Fri, 07 Jul 2017 06:37:01 +0000
Bug 1274919 - part1 : resume video decoding when cursor is hovering over the tab, and suspend it again when cursor leaves the tab. To resume the video decoding in advance can reduce the possibility that users see the incorrect video frame after opening the tab. Therefore, when the cursor is hovering over the tab, we assume user would open that tab soon, so we can start to resume the video decoding. In addition, will suspend the video decoding after the specific time the cursor leaves the tab. MozReview-Commit-ID: 94z4pzbXsth
bca07c9c7c548867ba76e555bea126d16d7cf7c0: Bug 1378691 P4 - delay completing seek if skip-to-next-key-frame is triggered; draft
Kaku Kuo <kaku@mozilla.com> - Wed, 05 Jul 2017 15:54:33 +0800 - rev 605207
Push 67324 by bmo:kaku@mozilla.com at Fri, 07 Jul 2017 06:36:43 +0000
Bug 1378691 P4 - delay completing seek if skip-to-next-key-frame is triggered; MozReview-Commit-ID: 9a8S6iaOlhI
78046f0435c294f96a1b013a6a6a9bbbbe3ef6b9: Bug 1378691 P3 - trigger skip-to-next-key-frame if the video decoding is too slow; draft
Kaku Kuo <kaku@mozilla.com> - Wed, 05 Jul 2017 14:18:40 +0800 - rev 605206
Push 67324 by bmo:kaku@mozilla.com at Fri, 07 Jul 2017 06:36:43 +0000
Bug 1378691 P3 - trigger skip-to-next-key-frame if the video decoding is too slow; MozReview-Commit-ID: H5tL4EseLvz
4ec19bdf005d75361853c405fe93751026e023f7: Bug 1378691 P2 - drop video until catch up playbak position; draft
Kaku Kuo <kaku@mozilla.com> - Wed, 05 Jul 2017 14:20:07 +0800 - rev 605205
Push 67324 by bmo:kaku@mozilla.com at Fri, 07 Jul 2017 06:36:43 +0000
Bug 1378691 P2 - drop video until catch up playbak position; MozReview-Commit-ID: A0GyitUamUT
d6f97bfba8501c9a0d04ed2372dd0250597c4e46: Bug 1378691 P1 - keep decoding audio; draft
Kaku Kuo <kaku@mozilla.com> - Wed, 05 Jul 2017 12:59:14 +0800 - rev 605204
Push 67324 by bmo:kaku@mozilla.com at Fri, 07 Jul 2017 06:36:43 +0000
Bug 1378691 P1 - keep decoding audio; MozReview-Commit-ID: LDyora19iAr
0508c119adc8f3b22bf7bd78b0b32e981e791536: Bug 1378814 - Don't return None in get_pseudo_style if not probing. r?emilio draft
Xidorn Quan <me@upsuper.org> - Fri, 07 Jul 2017 16:02:17 +1000 - rev 605203
Push 67323 by xquan@mozilla.com at Fri, 07 Jul 2017 06:36:10 +0000
Bug 1378814 - Don't return None in get_pseudo_style if not probing. r?emilio MozReview-Commit-ID: 5CziNBwYZSa
e01bb9601a69134ae83381fb2dfff9844636b4aa: Bug 1376760 - Fix race condition for ICustomDestinationList usage. r?jimm draft
Wei-Cheng Pan <wpan@mozilla.com> - Thu, 06 Jul 2017 14:06:09 +0800 - rev 605202
Push 67322 by bmo:wpan@mozilla.com at Fri, 07 Jul 2017 06:35:09 +0000
Bug 1376760 - Fix race condition for ICustomDestinationList usage. r?jimm MozReview-Commit-ID: fgZjrHqiek
80f895a2bf24cbce6f22ed58776be9670132f1a8: Bug 1378631. P3 - remove dead code. draft
JW Wang <jwwang@mozilla.com> - Thu, 06 Jul 2017 11:45:02 +0800 - rev 605201
Push 67321 by jwwang@mozilla.com at Fri, 07 Jul 2017 06:34:20 +0000
Bug 1378631. P3 - remove dead code. MozReview-Commit-ID: 6BO25ykG3ps
4e39231fbed1ea6ea6110b528308b73223878192: Bug 1378631. P2 - remove AbstractMediaDecoder::CanonicalDurationOrNull(). draft
JW Wang <jwwang@mozilla.com> - Thu, 06 Jul 2017 11:38:27 +0800 - rev 605200
Push 67321 by jwwang@mozilla.com at Fri, 07 Jul 2017 06:34:20 +0000
Bug 1378631. P2 - remove AbstractMediaDecoder::CanonicalDurationOrNull(). MozReview-Commit-ID: 9zWPcYZndsQ
4b30670e2d75260b21fa953f9c7219e3e485c396: Bug 1378631. P1 - dispatch duration changes from MDSM to MediaDecoderReader. draft
JW Wang <jwwang@mozilla.com> - Thu, 06 Jul 2017 11:32:28 +0800 - rev 605199
Push 67321 by jwwang@mozilla.com at Fri, 07 Jul 2017 06:34:20 +0000
Bug 1378631. P1 - dispatch duration changes from MDSM to MediaDecoderReader. So we can remove AbstractMediaDecoder::CanonicalDurationOrNull() later. MozReview-Commit-ID: 6zJCFDsCZPC
3da5880a509760e8efcea4c7c4b3192fc97ebc2e: Bug 1378814 - Don't return None in get_pseudo_style if not probing. r?emilio draft
Xidorn Quan <me@upsuper.org> - Fri, 07 Jul 2017 16:02:17 +1000 - rev 605198
Push 67320 by xquan@mozilla.com at Fri, 07 Jul 2017 06:03:04 +0000
Bug 1378814 - Don't return None in get_pseudo_style if not probing. r?emilio MozReview-Commit-ID: 5CziNBwYZSa
b952b913e68b8dcdf7e81be4312c270da056c4c8: mybase-stylo draft
Xidorn Quan <me@upsuper.org> - Mon, 12 Sep 2016 11:21:19 +1000 - rev 605197
Push 67320 by xquan@mozilla.com at Fri, 07 Jul 2017 06:03:04 +0000
mybase-stylo MozReview-Commit-ID: KhkzDKnGGhJ
327ed1047ead86797267a971a9c2758b318f0424: Bug 1377672 - part5: IMEStateManager::OnChangeFocusInternal() should notify IME of blur when focus is moving from a remote process to another process r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 05 Jul 2017 16:26:41 +0900 - rev 605196
Push 67319 by masayuki@d-toybox.com at Fri, 07 Jul 2017 05:35:43 +0000
Bug 1377672 - part5: IMEStateManager::OnChangeFocusInternal() should notify IME of blur when focus is moving from a remote process to another process r?m_kato When focus is moving from a remote process to different process (including to the main process), destroying IMEContentObserver in the focused remote process occurs later. I.e., NOTIFY_IME_OF_BLUR will be notified later. However, it may be too late for new focused process especially when destroying the focused widget. Therefore, this patch makes IMEStateManager notifies IME of blur in such case. MozReview-Commit-ID: GkypubVjn3H
caba59e091625c356bc0098fff2bf942cfc2bbef: Bug 1377672 - part4: ContentCacheInParent::RequestIMEToCommitComposition() should ignore too late requests r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 05 Jul 2017 19:55:18 +0900 - rev 605195
Push 67319 by masayuki@d-toybox.com at Fri, 07 Jul 2017 05:35:43 +0000
Bug 1377672 - part4: ContentCacheInParent::RequestIMEToCommitComposition() should ignore too late requests r?m_kato Requests to commit/cancel composition came from remote process with sync message. So, it may be too late. E.g., * If the process already sent new composition start but is not handled by the remote process yet. * If the process already send commit message but it's not handled by the remote process yet. * If focus was already moved to different process. In the former 2 cases, the remote process should wait eCompositionCommit(AsIs) events for clearing TextComposition. Therefore, the requested should be treated as it's handled asynchronously. In the last case, the remote process should commit composition with latest composition string in the main process because if the remote process commits composition with "current" composition string in it, user may lost some inputted text. MozReview-Commit-ID: 18BUoZZq7HS
faa5e384a7e166d9d7ea46aa0ef89b1e6c8dc652: Bug 1377672 - part3: IMEStateManager::NotifyIME() should ignore notifications and requests which comes from unexpected process r?smaug, m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 06 Jul 2017 00:47:40 +0900 - rev 605194
Push 67319 by masayuki@d-toybox.com at Fri, 07 Jul 2017 05:35:43 +0000
Bug 1377672 - part3: IMEStateManager::NotifyIME() should ignore notifications and requests which comes from unexpected process r?smaug, m_kato IME should receive notifications and requests only from proper process. E.g., IME shouldn't commit composition by a request which came from previous focused process. This patch makes that IMEStateManager::NotifyIME() takes pointer to TabParent optionally. If the request or notification came from remote process, it should be non-nullptr. Then, this makes it ignore notifications and requests from unexpected process. Note that this patch also touches some gfx headers because they use |ipc::| but compiler is confused at the ambiguousness between |mozilla::ipc::| and |mozilla::dom::ipc::|. Finally, this patch changes the NS_ASSERTION in IMEHandler::OnDestroyWindow() to MOZ_ASSERT because the orange caused by the NS_ASSERTION was not realized since there was already an intermittent orange bug caused by different NS_ASSERTION. MozReview-Commit-ID: 9CgKXQRJWmN
2f01e62d6867ae1c79aed7c9fdc9b1087a842092: Bug 1377672 - part2: IMEStateManager::SetIMEState() should set input context with proper origin information r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 03 Jul 2017 12:28:10 +0900 - rev 605193
Push 67319 by masayuki@d-toybox.com at Fri, 07 Jul 2017 05:35:43 +0000
Bug 1377672 - part2: IMEStateManager::SetIMEState() should set input context with proper origin information r?m_kato Currently, IMEStateManager always sets input context as set by current process even when it needs to adjust IME state when a tab parent for current focused IME process is removed. Then, input context for the widget is marked as for main process but the widget still have IME focus of a remote process. For fixing this mismatch, IMEStateManager should set ORIGIN_CONTENT even when the tab parent is being destroyed. MozReview-Commit-ID: C10YOAtkET4
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip