86c9dfebb236af7cbc9ce2927a0b837d870ff3ef: Bug 1222285 - Part 2: Making the keyboard events of modifier keys been suppressed when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Thu, 31 Aug 2017 11:14:14 +0800 - rev 705625
Push 91532 by bmo:tihuang@mozilla.com at Thu, 30 Nov 2017 12:40:23 +0000
Bug 1222285 - Part 2: Making the keyboard events of modifier keys been suppressed when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein This patch makes 'Shift', 'Alt' and 'AltGraph' been suppressed for content when fingerprinting resistance is enabled. Chrome can still get these events. The reason behind this is that websites can still observe key combinations to tell which keyboard layout is using even we spoof the keyboardEvent.code, keyboardEvent.keyCode and modifier states. For example, the AZERTY France keyboard, the digit keys of it requires the user press the Shift key. So, it is easy to differentiate AZERTY and QWERTY keyboard by observing whether a Shift key generates its own before the digit keys. There are similar issues for 'Alt' and 'AltGraph' as well. MozReview-Commit-ID: 3CwCgvey4lK
029c3a560ae88bde9c74d52d3ee9b895648e55a7: Bug 1222285 - Part 1: Spoofing the keyboard event to mimc a certain keyboard layout according to the content-language of the document when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Tue, 29 Aug 2017 11:33:27 +0800 - rev 705624
Push 91532 by bmo:tihuang@mozilla.com at Thu, 30 Nov 2017 12:40:23 +0000
Bug 1222285 - Part 1: Spoofing the keyboard event to mimc a certain keyboard layout according to the content-language of the document when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein This patch makes Firefox to spoof keyboardEvent.code, keyboardEvent.keycode and modifier states, for 'Shift', 'Alt', 'Control' and 'AltGraph', when 'privacy.resistFingerprinting' is true. Firefox will spoof keyboard events as a certain keyboard layout according to the content language of the document, for example, we use US English keyboard for English content. Right now, it only supports English contents, we will add more support for more languages later. The spoofing only affects content, chrome can still see real keyboard events. MozReview-Commit-ID: 40JPvwLmMMB
207d23c927262703cc4366f36161e5e9ec0481e8: Bug 1222285 - Part 3: Add a test case to check whether keyEvents been correctly spoofed and modifier keys been correctly suppressed. r?masayuki,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Tue, 05 Sep 2017 16:01:02 +0800 - rev 705623
Push 91531 by bmo:tihuang@mozilla.com at Thu, 30 Nov 2017 12:33:55 +0000
Bug 1222285 - Part 3: Add a test case to check whether keyEvents been correctly spoofed and modifier keys been correctly suppressed. r?masayuki,arthuredelstein This patch adds a test case which generates Keyboard events for English content and test whether the keyboard events been spoofed as US English QWERTY keyboard events. In addition, it also tests that whether the modifier keys been suppressed. MozReview-Commit-ID: d6uZxJJayk
9359d982c1e5b386f8baaf57eb8a3cb52edff60c: Bug 1222285 - Part 2: Making the keyboard events of modifier keys been suppressed when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Thu, 31 Aug 2017 11:14:14 +0800 - rev 705622
Push 91531 by bmo:tihuang@mozilla.com at Thu, 30 Nov 2017 12:33:55 +0000
Bug 1222285 - Part 2: Making the keyboard events of modifier keys been suppressed when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein This patch makes 'Shift', 'Alt' and 'AltGraph' been suppressed for content when fingerprinting resistance is enabled. Chrome can still get these events. The reason behind this is that websites can still observe key combinations to tell which keyboard layout is using even we spoof the keyboardEvent.code, keyboardEvent.keyCode and modifier states. For example, the AZERTY France keyboard, the digit keys of it requires the user press the Shift key. So, it is easy to differentiate AZERTY and QWERTY keyboard by observing whether a Shift key generates its own before the digit keys. There are similar issues for 'Alt' and 'AltGraph' as well. MozReview-Commit-ID: 3CwCgvey4lK
6faa6c924e46031b74f54e84013e3ec2b265fa63: Bug 1222285 - Part 1: Spoofing the keyboard event to mimc a certain keyboard layout according to the content-language of the document when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Tue, 29 Aug 2017 11:33:27 +0800 - rev 705621
Push 91531 by bmo:tihuang@mozilla.com at Thu, 30 Nov 2017 12:33:55 +0000
Bug 1222285 - Part 1: Spoofing the keyboard event to mimc a certain keyboard layout according to the content-language of the document when 'privacy.resistFingerprinting' is true. r?masayuki,arthuredelstein This patch makes Firefox to spoof keyboardEvent.code, keyboardEvent.keycode and modifier states, for 'Shift', 'Alt', 'Control' and 'AltGraph', when 'privacy.resistFingerprinting' is true. Firefox will spoof keyboard events as a certain keyboard layout according to the content language of the document, for example, we use US English keyboard for English content. Right now, it only supports English contents, we will add more support for more languages later. The spoofing only affects content, chrome can still see real keyboard events. MozReview-Commit-ID: 40JPvwLmMMB
bba45b9bec9a9a9aea896d98521f31d159c935cd: Bug 1414322 - Use WebDriver conformant interactability checks for sendKeysToElement. draft
Henrik Skupin <mail@hskupin.info> - Fri, 10 Nov 2017 20:29:04 +0100 - rev 705620
Push 91530 by bmo:hskupin@gmail.com at Thu, 30 Nov 2017 12:33:01 +0000
Bug 1414322 - Use WebDriver conformant interactability checks for sendKeysToElement. Enables webdriver spec keyboard interactability tests for 'Element Send Keys' by default by re-using the same capability 'moz:webdriverClick' from 'Element Click'. It can be disabled by turning off this preference. Also various webplatform tests for webdriver spec have been added which cover both the scroll into view action, and keyboard interactability check. Existing Marionette unit tests will be run in both modes, until we can get rid of the legacy mode. MozReview-Commit-ID: dFB8sQ6CN5
ccb84ad06c1d4dbb964c84e76e3c3fb920773296: Bug 1414322 - Refactor sendKeysToElement methods. draft
Henrik Skupin <mail@hskupin.info> - Thu, 09 Nov 2017 20:39:51 +0100 - rev 705619
Push 91530 by bmo:hskupin@gmail.com at Thu, 30 Nov 2017 12:33:01 +0000
Bug 1414322 - Refactor sendKeysToElement methods. Each call to sendKeysToElement should go through the interaction module, and never by directly calling event.sendKeysToElement. This will make sure that keyboard interactability checks will always be performed, even for chrome scope like alerts or modal dialogs. MozReview-Commit-ID: GoDKjMsNZsq
e37d50126afe69b30767b9d17f3c024c1b41aa7d: Bug 1414322 - Update Marionette accessibility tests for non keyboard-interactable elements. draft
Henrik Skupin <mail@hskupin.info> - Tue, 28 Nov 2017 17:18:37 +0100 - rev 705618
Push 91530 by bmo:hskupin@gmail.com at Thu, 30 Nov 2017 12:33:01 +0000
Bug 1414322 - Update Marionette accessibility tests for non keyboard-interactable elements. Because with webdriver interactability checks turned on, accessability checks are done afterward, and like in this case would even never run due to <h1> is not a keyboard-interactability element, which causes an ElementNotInteractableException. As such those obsolete tests can be removed now. MozReview-Commit-ID: 6pw5TCgMb7l
a7a812c6922c61fd50603c8c5fadc745f5182206: Bug 1414322 - Refactor keyboard and visibility tests. draft
Henrik Skupin <mail@hskupin.info> - Fri, 10 Nov 2017 11:01:40 +0100 - rev 705617
Push 91530 by bmo:hskupin@gmail.com at Thu, 30 Nov 2017 12:33:01 +0000
Bug 1414322 - Refactor keyboard and visibility tests. Both 'test_text.py' and 'test_typing.py' contained nearly duplicated tests for send_keys(), which have been removed from test_text.py now. The HTML testcase file 'javaScript.html' was used in various tests whereby it's initial purpose was to test keyboard events. As such unit tests have been updated to use inline HTML, or another more generic HTML testcase file. Also parts of the the file related to visibility checks have been moved to 'visibility.html'. MozReview-Commit-ID: CEWPPGdAffW
de9fbf68a4de858d0af6885e77a8fa1027d7de3c: Bug 1421968 - Enable ESLint rule mozilla/use-services by default, but whitelist it for various directories still to be fixed. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Tue, 28 Nov 2017 19:24:12 +0000 - rev 705616
Push 91529 by bmo:standard8@mozilla.com at Thu, 30 Nov 2017 12:21:11 +0000
Bug 1421968 - Enable ESLint rule mozilla/use-services by default, but whitelist it for various directories still to be fixed. r?Mossop MozReview-Commit-ID: KOZWr7FiDQZ
6d0fd09be3bcd16ba841e37f5d00eb6fffaff5cd: Bug 1421968 - Fix more instances of .getService to use Services.jsm where possible. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Thu, 30 Nov 2017 12:04:16 +0000 - rev 705615
Push 91529 by bmo:standard8@mozilla.com at Thu, 30 Nov 2017 12:21:11 +0000
Bug 1421968 - Fix more instances of .getService to use Services.jsm where possible. r?Mossop MozReview-Commit-ID: 2EbsWq7VPrI
ef0498ab5e9ea06157069bd81d2f5b970695cb5b: Bug 1417842 - Make Cu.readFile and Cu.readURI UTF-8 aware. r?kmag draft
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Thu, 30 Nov 2017 20:10:44 +0900 - rev 705614
Push 91528 by VYV03354@nifty.ne.jp at Thu, 30 Nov 2017 12:14:22 +0000
Bug 1417842 - Make Cu.readFile and Cu.readURI UTF-8 aware. r?kmag MozReview-Commit-ID: NwQSoAFzjL
7d1de0d0bddc874d2eacd58ac96d389f8bae9b7e: Bug 1035091: Disable @-moz-document on author sheets on nightly and early beta. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 29 Nov 2017 22:16:46 +0100 - rev 705613
Push 91527 by bmo:emilio@crisal.io at Thu, 30 Nov 2017 12:01:21 +0000
Bug 1035091: Disable @-moz-document on author sheets on nightly and early beta. r?xidorn MozReview-Commit-ID: AAUs1jJifjS
ba04a5b6dcb911fac87c23ef18b6a2f0334c8287: Bug TBD: Don't treat RowGroups as containing blocks. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 29 Nov 2017 16:38:53 +0100 - rev 705612
Push 91527 by bmo:emilio@crisal.io at Thu, 30 Nov 2017 12:01:21 +0000
Bug TBD: Don't treat RowGroups as containing blocks. MozReview-Commit-ID: 2mEfzBVb7XN
1d922229944fd4069376dd21f2414ad432190841: Bug 975644: Enable position sticky in table parts. r?dbaron draft
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 29 Nov 2017 16:11:25 +0100 - rev 705611
Push 91527 by bmo:emilio@crisal.io at Thu, 30 Nov 2017 12:01:21 +0000
Bug 975644: Enable position sticky in table parts. r?dbaron MozReview-Commit-ID: 85nCuChHdTa
2130373dbdf6ccf3a3521b39fde595977977604c: Bug 1421481 - Increase allowed number of webgl contexts on mobile. r?snorp draft
Jamie Nicol <jnicol@mozilla.com> - Thu, 30 Nov 2017 11:40:57 +0000 - rev 705610
Push 91526 by bmo:jnicol@mozilla.com at Thu, 30 Nov 2017 11:47:12 +0000
Bug 1421481 - Increase allowed number of webgl contexts on mobile. r?snorp This was previously limited to 2 per principal and 4 total on mobile. Mobile GPU drivers have progressed a lot since the limit was put in place, and the strict limit is causing webcompat issues on google maps. Increase to 8 per principal and 16 in total, bringing us closer in line with Chrome. MozReview-Commit-ID: 8Tsbrjr4KCE
57a25ac34fbd7cf8884f3241976efe58569d53e7: Bug 1358247 - Reply VR vibrate promises to the individual channels; r?kip draft
Daosheng Mu <daoshengmu@gmail.com> - Thu, 30 Nov 2017 19:37:07 +0800 - rev 705609
Push 91525 by bmo:dmu@mozilla.com at Thu, 30 Nov 2017 11:37:42 +0000
Bug 1358247 - Reply VR vibrate promises to the individual channels; r?kip MozReview-Commit-ID: 4NwYNkwKUMR
c16ade73ef5a5c8d0510d4d979f80475c1edeead: Bug 1421565 - Propagate allocation failure. r?bbouvier draft
Lars T Hansen <lhansen@mozilla.com> - Thu, 30 Nov 2017 12:22:10 +0100 - rev 705608
Push 91524 by bmo:lhansen@mozilla.com at Thu, 30 Nov 2017 11:25:21 +0000
Bug 1421565 - Propagate allocation failure. r?bbouvier These guards were mistakenly removed when bug 1377576 landed, because I misunderstood how the allocators for these five node types could fail - they can return nullptr for reasons other than allocation failure. I was warned about that but I misunderstood it anyway :( Anyhow, this puts the guards back. MozReview-Commit-ID: 4A0GdFRkeHn
8596ae787e5c6df067fb1d4560d20a6670446e74: Merge mozilla-central to mozilla-inbound. r=merge a=merge CLOSED TREE
Margareta Eliza Balazs <ebalazs@mozilla.com> - Thu, 30 Nov 2017 12:56:57 +0200 - rev 705607
Push 91524 by bmo:lhansen@mozilla.com at Thu, 30 Nov 2017 11:25:21 +0000
Merge mozilla-central to mozilla-inbound. r=merge a=merge CLOSED TREE
ba283baf4e98aa3a5f45a17981077b98697aa73a: Backed out changeset 65334d5e3012 (bug 1417039) for frequently failing in devtools/client/jsonview/test/browser_jsonview_chunked_json.js (Bug 1421520) r=backout a=backout
shindli <shindli@mozilla.com> - Thu, 30 Nov 2017 12:22:01 +0200 - rev 705606
Push 91524 by bmo:lhansen@mozilla.com at Thu, 30 Nov 2017 11:25:21 +0000
Backed out changeset 65334d5e3012 (bug 1417039) for frequently failing in devtools/client/jsonview/test/browser_jsonview_chunked_json.js (Bug 1421520) r=backout a=backout
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip