024606c3a9503ace4c89f5aba6ddf01dd5db6ee9: Bug 1253919 - Enable support for the logical values of CSS 'float' and 'clear' properties for all channels. r=dbaron
Jonathan Kew <jkew@mozilla.com> - Fri, 21 Apr 2017 16:01:04 +0100 - rev 354283
Push 89439 by jkew@mozilla.com at Fri, 21 Apr 2017 15:02:23 +0000
Bug 1253919 - Enable support for the logical values of CSS 'float' and 'clear' properties for all channels. r=dbaron
88d4303e68f7933b30a40a574586f80f51d3d99d: Merge mozilla-central to mozilla-inbound
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 21 Apr 2017 16:00:58 +0200 - rev 354282
Push 89438 by cbook@mozilla.com at Fri, 21 Apr 2017 14:01:25 +0000
Merge mozilla-central to mozilla-inbound
c8198aa6e7677e90cc7f1e2df0a14a5cc2719055: Backed out changeset 35ef9cd54519 (bug 1358142) for breaking android nightlys
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 21 Apr 2017 15:55:13 +0200 - rev 354281
Push 89438 by cbook@mozilla.com at Fri, 21 Apr 2017 14:01:25 +0000
Backed out changeset 35ef9cd54519 (bug 1358142) for breaking android nightlys
954eeda43262d24d17672287a297378316936fb3: Bug 1357680 part 1 - Track Ion-inlined scripts explicitly so we can inline functions with unknown properties. r=bhackett
Jan de Mooij <jdemooij@mozilla.com> - Fri, 21 Apr 2017 10:05:12 +0200 - rev 354280
Push 89437 by jandemooij@gmail.com at Fri, 21 Apr 2017 13:40:39 +0000
Bug 1357680 part 1 - Track Ion-inlined scripts explicitly so we can inline functions with unknown properties. r=bhackett
a2a4a9a0231dac78e0a224627756400693bcf28b: Bug 867815 - Fix visitIteratorStart shape/group guard for unboxed objects r=bhackett
Jon Coppeard <jcoppeard@mozilla.com> - Fri, 21 Apr 2017 14:14:25 +0100 - rev 354279
Push 89436 by jcoppeard@mozilla.com at Fri, 21 Apr 2017 13:23:39 +0000
Bug 867815 - Fix visitIteratorStart shape/group guard for unboxed objects r=bhackett
0d56e78960ef470c77009ad35a378527f5e9eb1b: Bug 867815 - Add post barrier for visitIteratorStart r=jandem
Jon Coppeard <jcoppeard@mozilla.com> - Wed, 19 Apr 2017 15:19:50 +0100 - rev 354278
Push 89436 by jcoppeard@mozilla.com at Fri, 21 Apr 2017 13:23:39 +0000
Bug 867815 - Add post barrier for visitIteratorStart r=jandem
9cb018faeab32ae8ddb6d2e74d193a544ea43e07: Merge mozilla-central to mozilla-inbound
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 21 Apr 2017 11:43:14 +0200 - rev 354277
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Merge mozilla-central to mozilla-inbound
dd530a59750adcaa0d48fa4f69b0cdb52715852a: Bug 1358402 - Keep 'marionette.defaultPrefs.enabled' around as fallback. r=ato a=tomcat
Henrik Skupin <mail@hskupin.info> - Fri, 21 Apr 2017 11:16:06 +0200 - rev 354276
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1358402 - Keep 'marionette.defaultPrefs.enabled' around as fallback. r=ato a=tomcat With bug 1344748 landed the default preferences and their handling has been changed. Builds starting with Firefox 54.0 can handle that, but previous releases don't enable Marionette at all after a restart under special conditions (invalidating 'update.status' file before the restart). To prevent the bustage we have to keep the preference 'marionette.defaultPrefs.enabled' around until the next ESR release is out. MozReview-Commit-ID: AB3liJlb6M7
950b641e2b9c5109ee8df6b2d39f09529d0f3c38: merge mozilla-inbound to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 21 Apr 2017 10:57:02 +0200 - rev 354275
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
merge mozilla-inbound to mozilla-central a=merge
7b43acb948540e6687bab6d508dcf6add5823e03: Backed out 9 changesets (bug 1353689) for web platform reftest failures
Iris Hsiao <ihsiao@mozilla.com> - Fri, 21 Apr 2017 13:38:28 +0800 - rev 354274
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Backed out 9 changesets (bug 1353689) for web platform reftest failures Backed out changeset 80ac3ea1427e (bug 1353689) Backed out changeset 9a5b36fefb22 (bug 1353689) Backed out changeset 44c5f4b4cdfc (bug 1353689) Backed out changeset 7f2790b4c963 (bug 1353689) Backed out changeset 8d8d2824a763 (bug 1353689) Backed out changeset d3ced5751998 (bug 1353689) Backed out changeset 5179ebf1e982 (bug 1353689) Backed out changeset ebf24732e9b3 (bug 1353689) Backed out changeset e81924e4cff3 (bug 1353689)
ca065b2e52d9068d713074a5b0f49920f681c40a: Bug 1217700 part.4 Add automated tests for IMEContentObserver r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 19 Apr 2017 21:57:58 +0900 - rev 354273
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1217700 part.4 Add automated tests for IMEContentObserver r=m_kato IMEContentObserver notifies IME of 3 notifications at most when editor is changed. The order is: 1. text change (with merged range if 2 or more change occurred during an edit transaction) 2. selection change (only the latest selection change. other changes occurred before that during an editor transaction are ignored) 3. position change (scrolled, resized, window moved, etc) This does not check the behavior in designMode because some operation in testWithHTMLEditor() causes unexpected behavior, e.g., moving focus. It *might* be bug of design mode. However, it doesn't matter for this bug. The important thing of this bug is, there should be automated tests for IMEContentObserver. And fortunately, IMEContentObserver does not check the type of editor. So, it's enough to test only contenteditable element for HTMLEditor at least for now. Therefore, I gave up to test it in designMode for now. MozReview-Commit-ID: 7L6ZlbVMU2P
ab221fb1ba32534ad3df2478051161c37579791e: Bug 1217700 part.3 Expose text change, selection change and position change notifications to nsITextInputProcessorCallback with nsITextInputProcessorNotification r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 20 Apr 2017 20:17:03 +0900 - rev 354272
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1217700 part.3 Expose text change, selection change and position change notifications to nsITextInputProcessorCallback with nsITextInputProcessorNotification r=smaug For testing IMEContentObserver, text change, selection change and position change notifications should be exposed to JS with nsITextInputProcessorNotification. MozReview-Commit-ID: 3PUhKXRwnAn
0ea1fc4888f06e0b9dde84ad60aa7632fc2ccb1a: Bug 1217700 part.2 IMEContentObserver should observe all possible notifications and check if it should be notified when it occurs r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 13 Apr 2017 14:32:12 +0900 - rev 354271
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1217700 part.2 IMEContentObserver should observe all possible notifications and check if it should be notified when it occurs r=m_kato IMEContentObserver can store pointer of IMENotificationRequests of its mWidget. Therefore, it can check the requests dynamically when it receives content change or layout change. This patch makes IMEContentObserver stores IMENotificationRequests as pointer and check it at every change notification received. Additionally, notification request may be changed due to focus move or something. Therefore, this patch makes IMEContentObserver and IMEContentObserver::IMENotificationSender() check if the notifications are still necessary. MozReview-Commit-ID: 2uU2wN15D8v
640ff6dddc6cb411d55b9c897670fa1a690865d1: Bug 1217700 part.1 nsIWidget should return reference to IMENotificationRequests r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 15 Apr 2017 01:35:58 +0900 - rev 354270
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1217700 part.1 nsIWidget should return reference to IMENotificationRequests r=m_kato IMEContentObserver may need to change notifications to send when TextInputProcessor begins input transaction. In current design, IMEContentObserver needs to retrieve IMENotificationRequests at every change. However, if nsIWidget returns a reference to its IMENotificationRequests, IMEContentObserver can call it only once. For that purpose, this patch changes nsIWidget::GetIMENotificationRequests() to nsIWidget::IMENotificationRequestsRef() and make it return |const IMENotificationRequests&|. However, if the lifetime of the instance of IMENotificationRequest is shorter than the widget instance's, it's dangerous. Therefore, it always returns TextEventDispatcher::mIMENotificationRequests. TextEventDispatcher's lifetime is longer than the widget. Therefore, this guarantees the lifetime. On the other hand, widget needs to update TextEventDispatcher::mIMENotificationRequests before calls of nsIWidget::IMENotificationRequestsRef(). Therefore, this patch makes TextEventDispatcher update proper IMENotificationRequests when it gets focus or starts new input transaction and clear mIMENotificationRequests when it loses focus. Note that TextEventDispatcher gets proper requests both from native text event dispatcher listener (typically, implemented by native IME handler class) and TextInputProcessor when TextInputProcessor has input transaction because even if TextInputProcessor overrides native IME, native IME still needs to know the content changes since they may get new input transaction after that. However, there may not be native IME handler in content process. If it runs in Android, PuppetWidget may have native IME handler because widget directly handles IME in e10s mode for Android. Otherwise, native IME handler is in its parent process. So, if TextInputHandler has input transaction in content process, PuppetWidget needs to behave as native event handler. Therefore, this patch makes PuppetWidget inherit TextEventDispatcherListener and implements PuppetWidget::IMENotificationRequestsRef(). MozReview-Commit-ID: 2SW3moONTOX
f866afd3d2d2d5aa026bd03227b13def53c50add: Bug 1257451 - Make |mach run| use --debugger-args instead of --debugparams, like the mochitest/reftest commands do. r=gps
Cameron McCormack <cam@mcc.id.au> - Fri, 21 Apr 2017 13:17:31 +1000 - rev 354269
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1257451 - Make |mach run| use --debugger-args instead of --debugparams, like the mochitest/reftest commands do. r=gps MozReview-Commit-ID: ChB9KjNKbHO
32ae2383a6d4cdfc2998851f5566783e2ef7716b: Bug 1348053 - add the UrgentStart flag to the channel when the loading is initiated by a user interaction for quicker network response. r=cpearce
JW Wang <jwwang@mozilla.com> - Mon, 10 Apr 2017 15:23:11 +0800 - rev 354268
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1348053 - add the UrgentStart flag to the channel when the loading is initiated by a user interaction for quicker network response. r=cpearce MozReview-Commit-ID: 1tk9k8u1zTu
52e6fe988bd5e387e2a2e16df49bc0f1199eeb20: Bug 1358362- stylo: Whitelist ShapeSource outparams in bindings to satisfy heap write analysis; r=bholley
Manish Goregaokar <manishearth@gmail.com> - Thu, 20 Apr 2017 14:49:53 -0700 - rev 354267
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1358362- stylo: Whitelist ShapeSource outparams in bindings to satisfy heap write analysis; r=bholley MozReview-Commit-ID: BzJg6b8DDxB
99fe1b020ce287a7165630e4ec06ef75c1660ae9: Bug 1297481 - add shutdown state to protocolproxyservice r=bagder
Patrick McManus <mcmanus@ducksong.com> - Wed, 19 Apr 2017 08:42:09 -0400 - rev 354266
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1297481 - add shutdown state to protocolproxyservice r=bagder the protocol proxy service asserts that is in a clean state at dtor - normally this happens through observe("xpcom-shutdown") but its actually possible of other events in the xpcom run queue to 'unitialize' things before the dtor.. add a state in which fail codes are returned instead. MozReview-Commit-ID: XaNQEZUsRP
e535df594d220cdf32b45a1c068ad779ff3ad578: Bug 1357986 - Use helper functions of TimeUnit to make code more readable. r=kaku
JW Wang <jwwang@mozilla.com> - Mon, 17 Apr 2017 16:35:04 +0800 - rev 354265
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1357986 - Use helper functions of TimeUnit to make code more readable. r=kaku 1. using media::TimeUnit to save some typing. 2. replace TimeUnit() with TimeUnit::Zero(). 3. replace TimeUnit::FromXXX(0) with TimeUnit::Zero(). 4. replace TimeUnit::FromMicroseconds(std::numeric_limits<int64_t>::max()) with TimeUnit::FromInfinity(). 5. replace some uses of int64_t with TimeUnit. 6. replace t > TimeUnit() with t.IsPositive(). MozReview-Commit-ID: 6hC94PXx86i
e7a44be96de2543b5dd0dd8e797e0502645513bc: Bug 1357983 - remove media::Microseconds. r=gerald
JW Wang <jwwang@mozilla.com> - Mon, 17 Apr 2017 14:34:36 +0800 - rev 354264
Push 89435 by cbook@mozilla.com at Fri, 21 Apr 2017 09:49:54 +0000
Bug 1357983 - remove media::Microseconds. r=gerald media::TimeUnit can take its place. We don't want 2 things for the same purpose to cause confusion. MozReview-Commit-ID: 3z6hbgXFsxP
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip