5b4c249619e5c9d0421bb910eebf62bbac1f4bbf: Bug 1370890, uplift NSS_3_32_RTM, no code changes, only version numbers, r=me
Kai Engert <kaie@kuix.de> - Thu, 27 Jul 2017 19:38:41 +0200 - rev 371594
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1370890, uplift NSS_3_32_RTM, no code changes, only version numbers, r=me UPGRADE_NSS_RELEASE, DONTBUILD
f682a94b747439e679ccf3f5d2983b15152cfe93: Bug 1384713 - remove unused *MsgStartChild constants; r=billm
Nathan Froyd <froydnj@mozilla.com> - Thu, 27 Jul 2017 13:32:15 -0400 - rev 371593
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1384713 - remove unused *MsgStartChild constants; r=billm We only ever use these for passing them into Endpoint construction. Let's remove them. Removing them also shows that the corresponding field in Endpoint is essentially read-only, so we can completely avoid passing in protocol IDs to Endpoint.
75b56cf1c910b87c7fc00a07224fef94f0b512d0: Bug 1384687 - label NotifyGCEndRunnable; r=billm
Nathan Froyd <froydnj@mozilla.com> - Thu, 27 Jul 2017 13:32:15 -0400 - rev 371592
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1384687 - label NotifyGCEndRunnable; r=billm All the other timers and GC-related things in this file run on the system group, so this one can too.
f13dfb12254e979d067945061a87f515995e34a8: Bug 1384550 - Skip atoms collection if it's no longer possible r=sfink
Jon Coppeard <jcoppeard@mozilla.com> - Thu, 27 Jul 2017 18:31:07 +0100 - rev 371591
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1384550 - Skip atoms collection if it's no longer possible r=sfink
ce44b4cc02e7816f291165d8edccb566c9447f76: Bug 1383767 - add warning about unsupported recursive usage of gfxFT2LockedFace. r=me
Lee Salzman <lsalzman@mozilla.com> - Thu, 27 Jul 2017 13:30:05 -0400 - rev 371590
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1383767 - add warning about unsupported recursive usage of gfxFT2LockedFace. r=me
b4cd32bc7d14f2ea97a7021a74ecddaf0311f82d: Bug 1382555 - Change some diagnostic asserts to find out why mEnt is nof in mCT. r=mcmanus
Dragana Damjanovic <dd.mozilla@gmail.com> - Thu, 27 Jul 2017 19:10:11 +0200 - rev 371589
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1382555 - Change some diagnostic asserts to find out why mEnt is nof in mCT. r=mcmanus
bb2eeb5a2f4aedf6247b01260b00f41dd9691c21: Bug 1374270 - Support sending health ping on shutdown via PingSender. r=Dexter
Kate Ustiuzhanina <kustiuzhanina@mozilla.com> - Wed, 26 Jul 2017 11:48:21 +0100 - rev 371588
Push 47510 by cbook@mozilla.com at Fri, 28 Jul 2017 13:28:06 +0000
Bug 1374270 - Support sending health ping on shutdown via PingSender. r=Dexter
a20bd8c1a22de3e2d02c8f9ad93fb3a2062ccb19: Bug 1381083: Test. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 27 Jul 2017 00:57:02 +0200 - rev 371587
Push 47509 by ecoal95@gmail.com at Fri, 28 Jul 2017 13:09:21 +0000
Bug 1381083: Test. r=heycam MozReview-Commit-ID: E99v62sXKtX
b8755e706ea7ca93ba444ecfc3eb0fdf60e17131: Bug 1381083: Don't hold the style context if we had a frame and re-resolved the style. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 27 Jul 2017 00:45:29 +0200 - rev 371586
Push 47509 by ecoal95@gmail.com at Fri, 28 Jul 2017 13:09:21 +0000
Bug 1381083: Don't hold the style context if we had a frame and re-resolved the style. r=heycam Otherwise we risk losing track of the frame if we hit the cache. MozReview-Commit-ID: ByHGhcBwIfX
dc839a86967dafca35021b3744f6dfb39264179f: Bug 1381083: Preliminary alignment and whitespace fixup. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 27 Jul 2017 00:28:52 +0200 - rev 371585
Push 47509 by ecoal95@gmail.com at Fri, 28 Jul 2017 13:09:21 +0000
Bug 1381083: Preliminary alignment and whitespace fixup. r=heycam MozReview-Commit-ID: 9V7pqVMOAqo
258d81d739533da1d4753741119bfd18c2176483: Bug 1384027 - part3: Don't send blur notification to IME from IMEStateManager::OnChangeFocusInternal() if no window becomes active and IME wants to keep composition during deactive r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 26 Jul 2017 00:57:29 +0900 - rev 371584
Push 47508 by masayuki@d-toybox.com at Fri, 28 Jul 2017 13:08:11 +0000
Bug 1384027 - part3: Don't send blur notification to IME from IMEStateManager::OnChangeFocusInternal() if no window becomes active and IME wants to keep composition during deactive r=m_kato Currently, IMEStateManager::OnChangeFocusInternal() sends blur notification to IME when a remote process has IME focus and focus is moving from the process. However, if IME wants to keep composition even during deactive and nobody will gets focus (i.e., all windows becomes deactive), IMEStateManager shouldn't send the blur notification because it causes committing composition. Therefore, it should send blur notification only when focus is moving to a PresContext (that means that not all windows becomes deactive) or IME doesn't want to keep composition during deactive. Then, even if another window becomes active next time, IMEStateManager can send "stop IME state management" message to the composing remote process and the remote process can commit composition normally. Additionally, this patch ensures to send blur notification when IME focused TabParent or widget is being destroyed. This fixes new memory leak bug of this patch (sFocusedIMETabParent keeps grabbing the instance until shutting down in some mochitests). MozReview-Commit-ID: KYiFGo970a8
51919d68802ec622a8c24a5e839e046f57f66405: Bug 1384027 - part2: Move PuppetWidget::NotifyIMEInternal() implementation to PuppetWidget::NotifyIME() which is a method of TextEventDispatcherListener, not nsIWidget r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 26 Jul 2017 00:09:41 +0900 - rev 371583
Push 47508 by masayuki@d-toybox.com at Fri, 28 Jul 2017 13:08:11 +0000
Bug 1384027 - part2: Move PuppetWidget::NotifyIMEInternal() implementation to PuppetWidget::NotifyIME() which is a method of TextEventDispatcherListener, not nsIWidget r=m_kato nsIWidget::NotifyIME() should call only TextEventDispatcher::NotifyIME() if it's necessary. Then, TextEventDispatcher::NotifyIME() calls TextEventDispatcherListener::NotifyIME() if it's necessary. E.g., requests to IME are necessary only for TextInputProcessor or native IME handler because the composition is only owned by one of them. However, notifications are necessary for both of them since focused editor contents and its focus state are shared. So, it doesn't need to call nsBaseWidget::NotifyIMEInternal() if all NotifyIMEInternal() implementations are moved to proper TextEventDispatcherListener::NotifyIME(). Currently, nsBaseWidget::NotifyIMEInternal() is implemented only by PuppetWidget. It sends notifications and requests to the parent process for native IME. Therefore, we can move NotifyIMEInternal() implementation to TextEventDispatcherListener::NotifyIME() which is implemented by PuppetWidget. This patch moves PuppetWidget::NotifyIMEInternal() implementation to PuppetWidget::NotifyIME() of TextEventDispatcherListener class, not of nsIWidget and removes NotifyIMEInternal() completely. With this change, handling order is changed. Old behavior is, TextEventDispatcher::NotifyIME() calls TextEventDispatcherListener::NotifyIME() before handling NOTIFY_IME_OF_FOCUS and then, nsBaseWidget::NotifyIME() sends the notification to the parent process. However, new behavior is, the notification is sent before TextEventDispatcher::NotifyIME() handles NOTIFY_IME_OF_FOCUS. Therefore, with new handling order, TextEventDispatcher can have IME notification requests after setting focus correctly. Additionally, TextEventDispatcher for PuppetWidget updates the notification requests at every event dispatch via TextEventDispatcher::BeginInputTransactionInternal() by the previous patch. So, with those patches, IMEContentObserver can refer actual IME notification requests correctly even after we'll make focus notification to async message. MozReview-Commit-ID: JwdQ68BjTXL
bd4ead9b69d42eb712e30df07c32d2b8c289d543: Bug 1384027 - part1: PuppetWidget should have TextEventDispatcher like nsIWidget instance in the parent process r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 25 Jul 2017 23:27:31 +0900 - rev 371582
Push 47508 by masayuki@d-toybox.com at Fri, 28 Jul 2017 13:08:11 +0000
Bug 1384027 - part1: PuppetWidget should have TextEventDispatcher like nsIWidget instance in the parent process r=m_kato In the parent process, every nsIWidget instance like nsWindow has TextEventDispatcher instance after dispatching a keyboard event or a composition event. Then, TextEventDispatcher manages whether there is composition and handles NotifyIME. However, PuppetWidget doesn't have it unless it synthesizes keyboard events or composition events for tests. This causes PuppetWidget implementing nsIWidget::NotifyIME() with nsBaseWidget::NotifyIMEInternal() which is a virtual method only implemented by PuppetWidget. For consistent implementation around here, we should move NotifyIMEInternal() implementation to TextEventDispatcherListener::NotifyIME() which is called by TextEventDispatcher::NotifyIME(). Then, PuppetWidget can handle NotifyIME() easier. This patch creates TextEventDispatcher::BeginInputTransactionFor() which takes pointer to a dispatching event and pointer to PuppetWidget. It emulates each corresponding event dispatcher method for managing composing state and begins input transaction for the dispatching event. Unfortunately, this implementation is ugly due to duplicated code. However, this is enough for now. When we need to make TextEventDispatcher manage more states, we should add methods which are shared by both BeginInputTransactionFor() and event dispatcher method. MozReview-Commit-ID: GeP028luZjR
c8568609e10ca0de349966554906ed2670a150ef: Bug 1383041 - Update bindings for API change in WR cset 9f66b56. r=mrobinson
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 28 Jul 2017 08:18:54 -0400 - rev 371581
Push 47507 by kgupta@mozilla.com at Fri, 28 Jul 2017 12:53:45 +0000
Bug 1383041 - Update bindings for API change in WR cset 9f66b56. r=mrobinson MozReview-Commit-ID: BWXPn0b7g6t
64e6e4ef477695afedcf9b3d443cfd8819f21776: Bug 1383041 - Update bindings for API change in WR cset 9868ef4. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 28 Jul 2017 08:18:32 -0400 - rev 371580
Push 47507 by kgupta@mozilla.com at Fri, 28 Jul 2017 12:53:45 +0000
Bug 1383041 - Update bindings for API change in WR cset 9868ef4. r=jrmuizel MozReview-Commit-ID: 3Jv1HwdfkPr
caba97838c0647c6fb75ab729c0dea41bc1019a1: Bug 1383041 - Update bindings for IdNamespace changes in WR cset 6a2662c. r=kvark
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 28 Jul 2017 08:18:30 -0400 - rev 371579
Push 47507 by kgupta@mozilla.com at Fri, 28 Jul 2017 12:53:45 +0000
Bug 1383041 - Update bindings for IdNamespace changes in WR cset 6a2662c. r=kvark MozReview-Commit-ID: 32dsMgqoOvf
f413861fc69a9c82ba3f4765721baf4e4558d1da: Bug 1383041 - Update WR to cset 0748e02d1be5f889fc17de2eb81c0c363ee3aa80. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 28 Jul 2017 08:18:28 -0400 - rev 371578
Push 47507 by kgupta@mozilla.com at Fri, 28 Jul 2017 12:53:45 +0000
Bug 1383041 - Update WR to cset 0748e02d1be5f889fc17de2eb81c0c363ee3aa80. r=jrmuizel MozReview-Commit-ID: BO0bDTnS1y2
b6a15a11a52958b32e84e885b257c4ec33ea9f92: Bug 1385070 - Remove the WebRenderOMTAEnabled pref. r=ethlin
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 27 Jul 2017 16:11:17 -0400 - rev 371577
Push 47506 by kgupta@mozilla.com at Fri, 28 Jul 2017 12:20:29 +0000
Bug 1385070 - Remove the WebRenderOMTAEnabled pref. r=ethlin MozReview-Commit-ID: CWdrpzorNxq
a4d0803e76901864339252806a8d6960f681af97: Bug 1384962 - Don't set process count for user on Preferences page load, r=jaws
Timothy Guan-tin Chien <timdream@gmail.com> - Thu, 27 Jul 2017 23:41:31 +0800 - rev 371576
Push 47505 by archaeopteryx@coole-files.de at Fri, 28 Jul 2017 11:42:36 +0000
Bug 1384962 - Don't set process count for user on Preferences page load, r=jaws This is a follow-up to incomplete fix in bug 1382649. In that bug, I attempted to set the process count value to the e10s rollout value, when the user unchecks "Use default performance settings". The same function updatePerformanceSettingsBox() is actually run during page load, resulting the user set value being changed to e10s rollout value if the user decided to use the default process count. Tests are written for both patches. MozReview-Commit-ID: 4CLLcEKbS58
a0a41228220bd600b4299758a394bcffebadc0e3: Bug 1379900 - Doing elements filtering in JS to simplify XPath query in FormData::collect. r=mikedeboer
Beekill95 <nnn_bikiu0707@yahoo.com> - Sun, 23 Jul 2017 14:41:52 +0700 - rev 371575
Push 47504 by dgottwald@mozilla.com at Fri, 28 Jul 2017 11:36:19 +0000
Bug 1379900 - Doing elements filtering in JS to simplify XPath query in FormData::collect. r=mikedeboer MozReview-Commit-ID: 7VjSkV8dlq1
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip