6cdf1ba0b78d1454bf95aaf73479f213048c84e3: servo: Merge #20277 - Enable /webvr/ tests (from servo:test-webvr); r=jdm
Anthony Ramine <n.oxyde@gmail.com> - Mon, 12 Mar 2018 10:32:52 -0400 - rev 766498
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
servo: Merge #20277 - Enable /webvr/ tests (from servo:test-webvr); r=jdm Source-Repo: https://github.com/servo/servo Source-Revision: 5feb13ac66eb256db8ef41d75ddf9c6c4e0ecd54
09af3a6b460a8eec7cf26f5f5cb177e932ec755b: Bug 1444852 - nsIFrame::BuildDisplayListForChild Remove the init step as the result is unused r=miko
Sylvestre Ledru <sledru@mozilla.com> - Mon, 12 Mar 2018 12:28:00 +0100 - rev 766497
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1444852 - nsIFrame::BuildDisplayListForChild Remove the init step as the result is unused r=miko MozReview-Commit-ID: G07Fwu1aw0M
5db3b0cf00bf579b08aa2452b5aca1f05896fd54: Backed out changeset adf758d8cff9 (bug 1423220) for frequent mochitest browser chrome failures on dom/base/test/browser_bug1303838.js
Cosmin Sabou <csabou@mozilla.com> - Mon, 12 Mar 2018 16:57:12 +0200 - rev 766496
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Backed out changeset adf758d8cff9 (bug 1423220) for frequent mochitest browser chrome failures on dom/base/test/browser_bug1303838.js
b850d95a18ae963c2217d1828c83284f782c6167: servo: Merge #20216 - Switch from servo/angle to the mozangle crate (from servo:mozangle); r=emilio
Simon Sapin <simon.sapin@exyr.org> - Mon, 12 Mar 2018 09:23:52 -0400 - rev 766495
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
servo: Merge #20216 - Switch from servo/angle to the mozangle crate (from servo:mozangle); r=emilio https://github.com/servo/mozangle Source-Repo: https://github.com/servo/servo Source-Revision: 345c373192a30329c2c4f70631ab0792fc348f7d
e07105d9698efa45ed5e08e8536414e08bba5762: Bug 1343451 - part 5: Make GeckoEditableSupport dispatch dummy eKeyDown and eKeyUp event during composition always r=jchen
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 27 Feb 2018 17:24:35 +0900 - rev 766494
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1343451 - part 5: Make GeckoEditableSupport dispatch dummy eKeyDown and eKeyUp event during composition always r=jchen On Android, GeckoEditableSupport has already dispatched eKeyDown event and eKeyUp event even during composition. I.e., the pref which will be enabled by bug 354358 has already been set to true only on Android. On the other hand, GeckoEditableSupport does not dispatch them if content listens to "input", "compositionstart", "compositionupdate" or "compositionend". So, different from the other platforms, we cannot test this behind pref ("dom.keyboardevent.dispatch_during_composition") even in Nightly. Therefore, this patch enables new behavior only when it's Nightly build or early Beta. And sets mKeyCode and mKeyNameIndex of the dummy KeyboardEvents to NS_VK_PROCESSKEY and KEY_NAME_INDEX_Process. MozReview-Commit-ID: Fuy0Ir2xiO5
dc4a2a5932c35d71aad9ad108ba3f8064b88b392: Bug 1343451 - part 4: Make TextInputHandler dispatches eKeyDown event with marking it as "processed by IME" r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 23 Feb 2018 23:09:43 +0900 - rev 766493
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1343451 - part 4: Make TextInputHandler dispatches eKeyDown event with marking it as "processed by IME" r=m_kato First of all, TextInputHandler::HandleKeyDown() dispatches an eKeyDown event before sending IME. This is different behavior from Gecko on the other platforms and it means TextInputHandler does not know if the eKeyDown event will be handled by IME. Therefore, we need to make TextInputHandler dispatch an eKeyDown event dispatch when it needs to dispatch another event. Therefore, this patch makes TextInputHandler not dispatch an eKeyDown even from its HandleKeyDown() unless it's already has composition (because if it's already had composition, any eKeyDown event except modifier keys should be marked as "processed by IME" for compatibility with the other browsers). For dispatching eKeyDown event only once for a native keydown event, this patch implements TextInputHandlerBase::MaybeDispatchCurrentKeydownEvent() to check whether eKeyDown event has already been dispatched for the event and if it's not so, dispatches eKeyDown event. Note that on macOS, dead keys are implemented as IME. However, we need to treat dead keys as is. Therefore, if current keydown event is a dead keydown event, MaybeDispatchCurrentKeydownEvent() should NOT mark dispatching eKeyDown event and its following eKeyDown event as "processed by IME". MozReview-Commit-ID: 7epk8wdAznd
9561ed261d044ca0588fd61886ea9aeb9f0c408a: Bug 1343451 - part 3-2: Make IMContextWrapper dispatch eKeyDown event or eKeyUp event if IME handles native key event but we have not dispatched DOM event for it yet r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 22 Feb 2018 20:56:08 +0900 - rev 766492
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1343451 - part 3-2: Make IMContextWrapper dispatch eKeyDown event or eKeyUp event if IME handles native key event but we have not dispatched DOM event for it yet r=m_kato Currently, IMContextWrapper doesn't dispatch eKeyDown event and eKeyUp event if it's handled by IME. However, for conforming to UI Events, it should not eat given keyboard events completely. This patch makes IMContextWrapper dispatches eKeyDown event or eKeyUp event before dispatching first event of composition events or content command event. MozReview-Commit-ID: H2jHpViTH5Q
84a5ec921442ee16179f94c18aa5d93731cd4292: Bug 1343451 - part 3-1: Make KeymapWrapper::InitKeyEvent() mark given key event as "processed by IME" if it has been handled by IME r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 22 Feb 2018 19:52:53 +0900 - rev 766491
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1343451 - part 3-1: Make KeymapWrapper::InitKeyEvent() mark given key event as "processed by IME" if it has been handled by IME r=m_kato For conforming UI Events spec, KeymapWrapper::InitKeyEvent() should initialize mKeyCode and mKeyNameIndex with NS_VK_PROCESSKEY and KEY_NAME_INDEX_Process if given keyboard event has already been handled by IME. For making it know if given keyboard event has been handled by IME, this patch adds additional bool argument to it and its callers. Note that this patch changes keyCode value and key value of "keydown" event if it's fired before "compositionstart" since Chromium does so on Linux. MozReview-Commit-ID: FC3tfyeeopU
b34d48936db822dc9d51b2186d9012e06d1aa4ef: Bug 1343451 - part 2: KeyboardLayout and NativeKey should use native key code value to check if the key event was handled by IME r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 01 Mar 2017 15:58:50 +0900 - rev 766490
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1343451 - part 2: KeyboardLayout and NativeKey should use native key code value to check if the key event was handled by IME r=m_kato On Windows, VK_PROCESSKEY key message is sent if the key event is handled by IME (in IMM mode or IMM-IME). Therefore, we can set WidgetKeyboardEvent::mKeyCode to NS_VK_PROCESSKEY and WidgetKeyboardEvent::mKeyNameIndex to KEY_NAME_INDEX_Process simply when we receive VK_PROCESSKEY. MozReview-Commit-ID: 9B8Q7rwfXYD
4dce7ab14f7190236420e1dad932bb6efc128645: Bug 1343451 - part 1: Declare (DOM|NS)_VK_PROCESSKEY for keyCode value during composition r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 01 Mar 2017 15:41:43 +0900 - rev 766489
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1343451 - part 1: Declare (DOM|NS)_VK_PROCESSKEY for keyCode value during composition r=smaug When native key event is handled by IME, we should set keyCode to 0xE5 (229, VK_PROCESS of virtual keycode of Windows) for behaving same as the other browsers. This patch declares it same as other keyCode values. MozReview-Commit-ID: 666bB1qOEgv
f20cbd6c20fdaa3a4bc0dd950a09588911a9c838: Bug 1444431 - Filter logs from familiar logging targets. r=jgraham
Andreas Tolfsen <ato@sny.no> - Sun, 11 Mar 2018 15:51:00 +0000 - rev 766488
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1444431 - Filter logs from familiar logging targets. r=jgraham geckodriver uses log 0.4, but it depends on a version of hyper that uses log 0.3. Previously this meant that geckodriver's logger could only see messages from crates using log 0.4, and had no access to messages from hyper or other crates using log 0.3. However, log 0.3.9 added interoperability so that programs built with a mix of log 0.3 and log 0.4 can again display messages from all crates. This patches geckodriver::logging to contain a whitelist of logged targets we care about. Currently this list includes geckodriver, mozprofile, mozrunner, mozversion, and webdriver. This will revert us to the behaviour prior to upgrading hyper to use log 0.3.9, and would be similar to the old implementation we had for filtering logs we had when geckodriver used slog. Thanks-to: Matt Brubeck <mbrubeck@mozilla.com> MozReview-Commit-ID: 6Xj0k6VD1dQ
adf758d8cff9f0b3a6d160f54419746791b99f8b: Bug 1423220 - Enable tab warming by default for Nightly builds. r=dao
Mike Conley <mconley@mozilla.com> - Wed, 31 Jan 2018 12:10:03 -0500 - rev 766487
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1423220 - Enable tab warming by default for Nightly builds. r=dao MozReview-Commit-ID: 8bz1U1WSzy5
e3dae8b7e2f2f25cb67c27ea54ddb967b304f58b: Bug 1443392 - Send resize event when FRAMECHANGED flag is set even if the window isn't resized. r=jimm
Xidorn Quan <me@upsuper.org> - Tue, 06 Mar 2018 17:47:15 +1100 - rev 766486
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1443392 - Send resize event when FRAMECHANGED flag is set even if the window isn't resized. r=jimm MozReview-Commit-ID: 9wpiFr9Tw9c
62453a779f13a47cd76eb527bc948e6d42e8f60f: Bug 1401129 - Release geckodriver 0.20.0. r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Mar 2018 16:06:59 +0000 - rev 766485
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Release geckodriver 0.20.0. r=whimboo MozReview-Commit-ID: Lip1pab8D0f
7a1e77dd53f6ea39c364acda678c3bb52405fee4: Bug 1401129 - Note changes for geckodriver 0.20.0 release. r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Mar 2018 16:05:35 +0000 - rev 766484
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Note changes for geckodriver 0.20.0 release. r=whimboo MozReview-Commit-ID: 1vb4nzpUlYD
eadd632eefb0fd7ba128ff1d49540ebbb8ec0bc2: Bug 1401129 - Release webdriver 0.35.0. r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Mar 2018 16:05:08 +0000 - rev 766483
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Release webdriver 0.35.0. r=whimboo MozReview-Commit-ID: lnoyZZbtcF
313304bfbfa562aaaaaf8de761b9d5cc118959af: Bug 1401129 - Release mozrunner 0.6.0. r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Mar 2018 14:26:10 +0000 - rev 766482
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Release mozrunner 0.6.0. r=whimboo MozReview-Commit-ID: 2nljPi3HN5b
32c9b97fc10b5e9f2f4e1466067f85b7f607dcec: Bug 1401129 - Release mozversion 0.1.3. r=whimboo
Andreas Tolfsen <ato@sny.no> - Mon, 12 Mar 2018 11:48:18 +0000 - rev 766481
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Release mozversion 0.1.3. r=whimboo MozReview-Commit-ID: JMUOjttq31L
95793c4be21c192b86914287284a079c67aee89e: Bug 1401129 - Add peer review note to automation files. r=whimboo
Andreas Tolfsen <ato@sny.no> - Mon, 12 Mar 2018 11:47:28 +0000 - rev 766480
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Add peer review note to automation files. r=whimboo MozReview-Commit-ID: 47708JTKoro
b5e15e66b86a2b2b219cf5cce6350b536a17f4d9: Bug 1401129 - Restore extensions.shield-recipe-client.api_url in automation tools. r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Mar 2018 15:47:09 +0000 - rev 766479
Push 102335 by bmo:cmanchester@mozilla.com at Mon, 12 Mar 2018 22:26:14 +0000
Bug 1401129 - Restore extensions.shield-recipe-client.api_url in automation tools. r=whimboo The extensions.shield-recipe-client.api_url preference was replaced with app.normandy.api_url in bug 1436113. There are multiple automation tools in the tree that target out-of-tree release channels and removing the old preference would break these. This patch re-adds the old preference with a note of when it was removed. MozReview-Commit-ID: HhTfRFkRQTC
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip