694e5733334f4dc5bce21e027de7748600444815: no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Tue, 12 Dec 2017 20:21:11 -0800 - rev 714927
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump ar -> 0fb82cfc885d be -> 22f0d28f9bba bg -> a4a40d2ec032 da -> f99fbe23f04e dsb -> d5e53cadbee9 eo -> efe9c3496881 es-CL -> b3d75f5fbb88 es-MX -> 7829edebb584 fi -> 12fee9bf99c9 hsb -> 76d86cf6e32a hu -> ed97f7fac9fa nb-NO -> 4eae2c8418a8 pl -> 4620129f50bc pt-BR -> dd1a019a83fc pt-PT -> 3f3602b0ee5f ro -> e82f720796ad sk -> 8ce4773c6c9a sq -> ea8a70d3f9c2 sr -> 001c301b5796 tr -> b013a3fe3763 zh-CN -> 4fe076aa5530 zh-TW -> 214fe44bed60
a7f1e480c3202b7afd1dc97cbc5a3a1e0cfa70c4: No bug - Tagging d7ddb4b0dc03cb110b8936c89465ca5e08ea71be with FIREFOX_58_0b11_BUILD1, FIREFOX_58_0b11_RELEASE a=release CLOSED TREE
ffxbld <release@mozilla.com> - Tue, 12 Dec 2017 08:39:43 -0800 - rev 714926
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
No bug - Tagging d7ddb4b0dc03cb110b8936c89465ca5e08ea71be with FIREFOX_58_0b11_BUILD1, FIREFOX_58_0b11_RELEASE a=release CLOSED TREE
903ed5a1a7e75b062f6c9b79b15057fefe89068d: No bug - Tagging d7ddb4b0dc03cb110b8936c89465ca5e08ea71be with FENNEC_58_0b11_BUILD1, FENNEC_58_0b11_RELEASE a=release CLOSED TREE
ffxbld <release@mozilla.com> - Tue, 12 Dec 2017 08:04:01 -0800 - rev 714925
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
No bug - Tagging d7ddb4b0dc03cb110b8936c89465ca5e08ea71be with FENNEC_58_0b11_BUILD1, FENNEC_58_0b11_RELEASE a=release CLOSED TREE
bcf45d5c58a5fdfde60675da9c3e55539d072df7: Automatic version bump. CLOSED TREE NO BUG a=release
ffxbld <release@mozilla.com> - Tue, 12 Dec 2017 08:03:56 -0800 - rev 714924
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Automatic version bump. CLOSED TREE NO BUG a=release
c501bec2b3f27f5a8557e12804b8c8751191b884: Bug 1423122 - Use the correct selection object in the getSelectionInfo when an input element is selected: Add newline to fix eslint failure r=eslint a=Aryx
Sebastian Hengst <archaeopteryx@coole-files.de> - Tue, 12 Dec 2017 17:32:02 +0200 - rev 714923
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1423122 - Use the correct selection object in the getSelectionInfo when an input element is selected: Add newline to fix eslint failure r=eslint a=Aryx
198a20c061dadba7366c0963ec845823c8e9a034: Bug 1408708 - Fetch stylesheet content via stylesheet window instead of top level content window. r=pbro a=lizzard
Alexandre Poirot <poirot.alex@gmail.com> - Thu, 07 Dec 2017 08:22:43 -0500 - rev 714922
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1408708 - Fetch stylesheet content via stylesheet window instead of top level content window. r=pbro a=lizzard MozReview-Commit-ID: AKXQLNAwy8t
96355d26b932219a8081bfe21ee80048e12ce274: Bug 1424343 - Stop migrating the browser.search.selectedEngine preference, r=adw a=gchang
Florian Quèze <florian@queze.net> - Sun, 10 Dec 2017 01:39:17 +0100 - rev 714921
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1424343 - Stop migrating the browser.search.selectedEngine preference, r=adw a=gchang
f8ae2687ccc18da13270339d5a0c19fb41c72cb0: Bug 1424292 - Pocket referrer only sent when story has HTTPS URL r=Mardak a=gchang
Christian Sadilek <csadilek@mozilla.com> - Fri, 08 Dec 2017 12:34:45 -0500 - rev 714920
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1424292 - Pocket referrer only sent when story has HTTPS URL r=Mardak a=gchang MozReview-Commit-ID: 5u18oc0GiNx
23dd8e97b482d748b5c5ebea0a1d9d679bd66866: Bug 1423122 - Use the correct selection object in the getSelectionInfo when an input element is selected r=Felipe a=gchang
Thom Chiovoloni <tchiovoloni@mozilla.com> - Wed, 06 Dec 2017 15:27:46 -0500 - rev 714919
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1423122 - Use the correct selection object in the getSelectionInfo when an input element is selected r=Felipe a=gchang MozReview-Commit-ID: L8nANaiYfyc
df953324066b58824a34bcdedf7704674452b60d: Bug 1423456 - ContentCacheInParent::OnEventNeedingAckHandled() shouldn't decrement mPendingCompositionCount when it receives eCompositionCommit(AsIs) from the remote process but the composition has already been committed by a request to commit composition r=m_kato a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 06 Dec 2017 15:07:41 +0900 - rev 714918
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1423456 - ContentCacheInParent::OnEventNeedingAckHandled() shouldn't decrement mPendingCompositionCount when it receives eCompositionCommit(AsIs) from the remote process but the composition has already been committed by a request to commit composition r=m_kato a=lizzard After fixing bug 1420849, remote process started to ignore composition events after it synthesizes eCompositionCommit event after requesting to commit composition. However, remote process still keeps returning composition events when it receives from the main process. So, if the main process has already sent eCompositionCommit(AsIs) event when it's requested to commit composition from the remote process, ContentCacheInParent::OnEventNeedingAckHandled() receives both eCompositionCommitRequestHandled and eCompositionCommit(AsIs) events for *a* composition. Therefore, mPendingCompositionCount may be decremented twice for a composition. This causes hitting MOZ_DIAGNOSTIC_ASSERT. So, ContentCacheInParent need to manage if sent composition events are ignored or not. Then, ContentCacheInParent::OnEventNeedingAckHandled() stops decrementing mPendingCompositionCount when it receives eCompositionCommit(AsIs) events which are ignored by the remote process. This patch manages it with |mIsChildIgnoringCompositionEvents| and changes |bool mIsPendingLastCommitEvent| to |uint8_t mPendingCommitCount| for making ContentCache be able to manage multiple pending commit events if its remote process is too busy. MozReview-Commit-ID: CYQDeZXl7TJ
1dc54b85de4dc4591fa46dab70a31ed79be4e41d: Bug 1420849 - Make PuppetWidget discard composition events after requesting commit composition and synthesizing eCommitComposition event until new eCompositionStart event comes r=m_kato a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 27 Nov 2017 20:34:01 +0900 - rev 714917
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1420849 - Make PuppetWidget discard composition events after requesting commit composition and synthesizing eCommitComposition event until new eCompositionStart event comes r=m_kato a=lizzard When ContentCacheInParent::RequestIMEToCommitComposition() returns true, the remote process will synthesize eCompositionCommit event. This causes destroying TextComposition event in the remote process (by IMEStateManager::DispatchCompositionEvent()). Then, IMEStateManager::DispatchCompositionEvent() will recreate new TextComposition instance when it receives new composition event. Then, it may request to commit composition to the main process via PuppetWidget accidentally. So, after PuppetWidget::RequestIMEToCommitComposition() synthesizes eCompositionCommit, PuppetWidget should discard following composition events until it receives eCompositionStart since they are unnecessary for the content and they are for the old composition, i.e., outdated events. MozReview-Commit-ID: BNRcoYxABpd
524a38fae76c36f9305b2603c1859386bc54a271: Bug 1405832 - part 4: ContentCacheInParent::OnEventNeedingAckHandled() shouldn't crash in release build r=m_kato a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Nov 2017 23:30:18 +0900 - rev 714916
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1405832 - part 4: ContentCacheInParent::OnEventNeedingAckHandled() shouldn't crash in release build r=m_kato a=lizzard For protecting main process, we should stop crashing main process in release build even when we detect our bug. However, we should keep crashing with MOZ_DIAGNOSTIC_ASSER which is enabled only on Night and Developer Edition. MozReview-Commit-ID: 5BQ46IFzXXj
8e59e9aed42125f17012405842d4b4ae44148cc0: Bug 1405832 - part 3: ContentCacheInParent::RequestIMEToCommitComposition() should call nsIWidget::NotifyIME() via TextComposition::RequestToCommit() r=m_kato a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Nov 2017 23:08:37 +0900 - rev 714915
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1405832 - part 3: ContentCacheInParent::RequestIMEToCommitComposition() should call nsIWidget::NotifyIME() via TextComposition::RequestToCommit() r=m_kato a=lizzard Now, TextComposition::RequestToCommit() manages if it has already requested IME to commit or cancel composition and this is important for redundant requests. Therefore, ContentCacheInParent::RequestIMEToCommitComposition() shouldn't call nsIWidget::NotifyIME() directly. MozReview-Commit-ID: 69VpgyK9Jk5
31bb04b6df157ce911218040ba35f37f3df2a9b6: Bug 1405832 - part 2: TextComposition::RequestToCommit() should request IME to commit or cancel composition only when it hasn't been request it yet and hasn't received commit event yet r=m_kato a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Nov 2017 22:59:04 +0900 - rev 714914
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1405832 - part 2: TextComposition::RequestToCommit() should request IME to commit or cancel composition only when it hasn't been request it yet and hasn't received commit event yet r=m_kato a=lizzard According to the log in crash reports, eCompositionCommitRequestHandled is sent to ContentCacheInParent twice or more for a composition. This causes breaking mPendingCompositionCount and mPendingEventsNeedingAck management. Currently, nsIWidget::NotifyIME() should be called only by TextComposition::RequestToCommit(). Therefore, the method should manage if it should request it actually. If the composition has already received eCompositionCommit(AsIs) event, it shouldn't request it because parent process may have already stated new composition and it shouldn't be broken by request for old composition. MozReview-Commit-ID: 2ekSa6EIeRP
0136b24f43b38f65f12e97d90ef285b2702796b4: Bug 1405832 - part 1: ContentCacheInParent::RequestIMEToCommitComposition() should increment mPendingEventsNeedingAck itself if it treat the request handled synchronously without actually requesting IME to commit composition r=m_kato a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Nov 2017 22:20:02 +0900 - rev 714913
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1405832 - part 1: ContentCacheInParent::RequestIMEToCommitComposition() should increment mPendingEventsNeedingAck itself if it treat the request handled synchronously without actually requesting IME to commit composition r=m_kato a=lizzard This is a simple bug of ContentCacheInParent. When ContentCacheInParent::RequestIMEToCommitComposition() returns true, PuppetWidget::RequestIMEToCommitComposition() will send eCompositionCommitRequestHandled pseudo event message back to the main process. This causes counting down mPendingEventsNeedingAck in ContentCacheInParent::OnEventNeedingAckHandled(). Therefore, in the normal path, ContentCacheInParent::OnCompositionEvent() increments it for receiving the pseudo event message. However, if the tab parent has already lost focus, RequestIMEToCommitComposition() returns true without requesting native IME to commit composition. So, ContentCacheInParent::OnCompositionEvent() cannot increment mPendingEventsNeedingAck for coming eCompositionCommitRequestHandled. Therefore, RequestIMEToCommitComposition() needs to increment mPendingEventsNeedingAck by itself when it won't request IME to commit composition but it returns true. MozReview-Commit-ID: 4Alwfy8avB
503f6ecc05118892f48d3613315524bcfdb0fc73: Bug 1423663 - Release Dockerfiles from Ubuntu:vivid not working after EOL r=Callek a=release
Rail Aliiev <rail@mozilla.com> - Thu, 07 Dec 2017 11:55:57 -0500 - rev 714912
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
Bug 1423663 - Release Dockerfiles from Ubuntu:vivid not working after EOL r=Callek a=release MozReview-Commit-ID: HiTT1b4I8Tt
c9fa22389f1bb4df5783c73209c093cfae477e8b: no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Tue, 12 Dec 2017 04:22:15 -0800 - rev 714911
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump bg -> a48c33a5eb1f bs -> 185c908abc5d gu-IN -> ad5427bbefa0 he -> feebeee669ef kab -> 8ec76eb5c11b pt-BR -> 5a833510cd66 sl -> b6971df009c1 sq -> 25ee68b87029 sr -> eb7e16fd2b1b th -> 5ce795de7e57 zh-CN -> 22fbea9e6f72
c9794ae9ad369c3efe94267a0a3653a874393b94: no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Tue, 12 Dec 2017 04:22:09 -0800 - rev 714910
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump bs -> 185c908abc5d es-AR -> a8b1b34502cc gu-IN -> ad5427bbefa0 pt-BR -> 5a833510cd66 sl -> b6971df009c1 sq -> 25ee68b87029 th -> 5ce795de7e57
fcd21eb1dcfeadef9eacec4c2f3f047031d18d61: no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Mon, 11 Dec 2017 05:21:29 -0800 - rev 714909
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump hy-AM -> 6319eaf727dc ka -> 0f2bc097512e kab -> ef9984caa30c nl -> d3e2d1b77c63 nn-NO -> 881a8d8aec43 uk -> 73419969a37d vi -> 9bfadbe6a1f7
e130cae4ad81cac3cab4a9aeffa63ccbcb2f8fa9: no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Mon, 11 Dec 2017 05:21:23 -0800 - rev 714908
Push 94055 by bmo:agl@chromium.org at Sun, 31 Dec 2017 23:39:06 +0000
no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump hy-AM -> 6319eaf727dc ka -> 7bec7838b62e nl -> d3e2d1b77c63 uk -> 73419969a37d wo -> 03717d4b8d3b
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip