8ab5323b26bd78946c40b631953c70b2c87a2b6c: Bug 1336124 - Remove unused B2G code in session teardown. r=maja_zf, a=test-only
Andreas Tolfsen <ato@mozilla.com> - Thu, 02 Feb 2017 16:10:18 +0000 - rev 378246
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1336124 - Remove unused B2G code in session teardown. r=maja_zf, a=test-only MozReview-Commit-ID: CHmdB7BvBT8
73551688c6ac22ec1d479ef77f519fd212a90cc9: Bug 1336124 - Add assert.session for checking if session is active. r=maja_zf, a=test-only
Andreas Tolfsen <ato@mozilla.com> - Thu, 02 Feb 2017 16:09:14 +0000 - rev 378245
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1336124 - Add assert.session for checking if session is active. r=maja_zf, a=test-only MozReview-Commit-ID: CmHFag2q1V2
9b8c5ed2e94a4311c450017696923fb52021880a: No bug, Automated HPKP preload list update from host bld-linux64-spot-166 - a=hpkp-update
ffxbld - Tue, 07 Feb 2017 07:27:07 -0800 - rev 378244
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
No bug, Automated HPKP preload list update from host bld-linux64-spot-166 - a=hpkp-update
cc8652056af98ec6331d1dfc8143fcb9984fb49e: No bug, Automated HSTS preload list update from host bld-linux64-spot-166 - a=hsts-update
ffxbld - Tue, 07 Feb 2017 07:27:05 -0800 - rev 378243
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
No bug, Automated HSTS preload list update from host bld-linux64-spot-166 - a=hsts-update
4116e3e124601c356950880ad01f015626b21345: Bug 1336445 - Don't select the first tab if switch_to_window() is called with a chrome window handle. r=ato a=test-only
Henrik Skupin <mail@hskupin.info> - Sun, 05 Feb 2017 15:55:10 +0100 - rev 378242
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1336445 - Don't select the first tab if switch_to_window() is called with a chrome window handle. r=ato a=test-only Using switch_to_window() with a chrome window handle should not change the selected tab within a browser window. It means we first have to check if it is a chrome handle, and only if it's not, we should care about content window handles. MozReview-Commit-ID: IcmCcmVy26T
2a4e9d28de7198d08e1553d1c242116e55734fc8: Bug 1322277 - Default socket timeout has to be larger than the default page load timeout. r=ato a=test-only
Henrik Skupin <mail@hskupin.info> - Mon, 06 Feb 2017 13:11:38 +0100 - rev 378241
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1322277 - Default socket timeout has to be larger than the default page load timeout. r=ato a=test-only Until we can remove the socket timeout parameter it has to be set a default value which is larger than the longest timeout as defined by the WebDriver spec. In that case it's 300s for page load. Also add another minute so that slow running builds have enough time to send the timeout error to the client. MozReview-Commit-ID: EOBW4mozDT1
6aea5d06cc3efaafa676d5c1c4c7301009cf3a22: Bug 1322277 - Fix usage of capabilities in start_session. r=ato a=test-only
Henrik Skupin <mail@hskupin.info> - Mon, 06 Feb 2017 13:03:18 +0100 - rev 378240
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1322277 - Fix usage of capabilities in start_session. r=ato a=test-only Capabilities as passed into start_session() can be desiredCapabilities and requiredCapabilities. As such the parameter name should be clear. MozReview-Commit-ID: GPNv4g9HMO2
3d0d4b01628523b12ebc0c27cda85922bb27157e: Bug 1336086 - remove mozilla::services::_external_Get*Service; r=bsmedberg,jesup a=gchang
Nathan Froyd <froydnj@mozilla.com> - Fri, 03 Feb 2017 11:52:02 -0500 - rev 378239
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1336086 - remove mozilla::services::_external_Get*Service; r=bsmedberg,jesup a=gchang Removing the exported symbols is straightforward enough. The only wrinkle is that PeerConnectionCtx.cpp gets compiled with and without MOZILLA_INTERNAL_API. When compiling without MOZILLA_INTERNAL_API, mozilla::services::Get*Service was redirected to the _external_* symbol variants. But as the _external_* symbols no longer exist, PeerConnectionCtx.cpp's code no longer worked. Fortunately, PeerConnectionCtx.cpp already contains a few #ifdef MOZILLA_INTERNAL_API blocks to handle internal/external compilation; fixing this newest issue was just a matter of extending existing blocks and adding new ones. The key observation is that we never added any observers when compiling without MOZILLA_INTERNAL_API, so we can #ifdef out the removals of observers, as those would have no effect, and simply skip getting the observer service for the observer additions if we're compiling without MOZILLA_INTERNAL_API.
2de292c7c4895fdec7faed2a9bd5f25ab9c0a3f0: Bug 1335194 - Enable the GPU process test-kill button on Aurora. (bug 1335194, r=gwright a=gchang
David Anderson <danderson@mozilla.com> - Tue, 31 Jan 2017 11:06:33 -0800 - rev 378238
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1335194 - Enable the GPU process test-kill button on Aurora. (bug 1335194, r=gwright a=gchang
c2bfbcf5430ca1be059d69920a2e6be147ad0478: Bug 1314803 - Remove supportsHardwareH264 from about:support r=mattwoodrow a=gchang
George Wright <george@mozilla.com> - Thu, 26 Jan 2017 13:11:17 -0500 - rev 378237
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1314803 - Remove supportsHardwareH264 from about:support r=mattwoodrow a=gchang
98cb18e24433146585f0e983d93d4a50aa5801e4: Bug 1314803 - Report correct values for Azure backends when the GPU process is enabled on Windows r=mattwoodrow a=gchang
George Wright <george@mozilla.com> - Wed, 25 Jan 2017 13:08:40 -0500 - rev 378236
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1314803 - Report correct values for Azure backends when the GPU process is enabled on Windows r=mattwoodrow a=gchang
0626ee6448dbbfa2dfff78cc2f40cd07f5291233: Bug 1279925 - Add Win10AU versions of tahoma.ttf and tahomabd.ttf to the GDEF blacklist in harfbuzz. r=jrmuizel a=gchang
Jonathan Kew <jkew@mozilla.com> - Thu, 02 Feb 2017 16:22:11 +0000 - rev 378235
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1279925 - Add Win10AU versions of tahoma.ttf and tahomabd.ttf to the GDEF blacklist in harfbuzz. r=jrmuizel a=gchang
fcc32735c01d504767a0dee94c6bc706b6a23b5e: Backed out changeset 4928b37a5650 (bug 1333385) for browser_net_json-b64.js failures.
Ryan VanderMeulen <ryanvm@gmail.com> - Mon, 06 Feb 2017 20:58:16 -0500 - rev 378234
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Backed out changeset 4928b37a5650 (bug 1333385) for browser_net_json-b64.js failures.
295a39d8aa6b0255a5467970303f1bb8ff0bd7ed: Bug 1320170 - dom/media should use nsIPrincipal (and PrincipalInfo) instead origin as string. r=rjesup, r=ehsan, a=lizzard
Andrea Marchesini <amarchesini@mozilla.com> - Sat, 28 Jan 2017 18:29:13 +0100 - rev 378233
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1320170 - dom/media should use nsIPrincipal (and PrincipalInfo) instead origin as string. r=rjesup, r=ehsan, a=lizzard
4928b37a565058ba218024d0dc3fe1508a88a34d: Bug 1333385 - Fix base64 json in netmonitor. r=jdescottes, a=gchang
Adrien Enault <schwartzmorn+bugzilla@gmail.com> - Thu, 26 Jan 2017 18:18:22 +0100 - rev 378232
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1333385 - Fix base64 json in netmonitor. r=jdescottes, a=gchang
9ad41a8fca06705ca8ccc8fecf96b9730f095079: Bug 1317947 - Land NSS NSS_3_29_RTM in FF53. a=lizzard
Franziskus Kiefer <franziskuskiefer@gmail.com> - Mon, 06 Feb 2017 11:05:15 +0100 - rev 378231
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1317947 - Land NSS NSS_3_29_RTM in FF53. a=lizzard
cb11989283f92e3613a2e1f091599b566b4270fc: Bug 1336448 - Disable helper thread logging in Tracelogger. r=bbouvier, a=jcristau
Hannes Verschore <hv1989@gmail.com> - Fri, 03 Feb 2017 16:15:00 -0500 - rev 378230
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1336448 - Disable helper thread logging in Tracelogger. r=bbouvier, a=jcristau
f8aab6b954303483feae6ce898ebb848fafcbd04: Bug 1320972 - Allow a max difference of 1 on Android for 722923-1.html. a=test-only
Mats Palmgren <mats@mozilla.com> - Fri, 03 Feb 2017 14:58:00 -0500 - rev 378229
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1320972 - Allow a max difference of 1 on Android for 722923-1.html. a=test-only
05fae22830c0365b8173be4a2584ff0375b547a1: 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, a=jcristau
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 03 Feb 2017 18:01:33 +0900 - rev 378228
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +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, a=jcristau 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
ee21650b00374a2363f08866dff5f64cbcce63ce: 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, a=jcristau
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 03 Feb 2017 14:30:22 +0900 - rev 378227
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +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, a=jcristau 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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip