213ae1ab70d470365ab5ee3a4778c225153074cb: Bug 1421518 - add user-gestures test for the autoplay policy. r=jwwang
Alastor Wu <alwu@mozilla.com> - Tue, 05 Dec 2017 10:50:56 +0800 - rev 394950
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1421518 - add user-gestures test for the autoplay policy. r=jwwang Mouse click or keyboard press are the events which could activate the page and allow the page to autoplay. Other events are not. MozReview-Commit-ID: FjhcBSH0mCX
b2db8b6d26d0828c6db93237e7050756ac0907be: Bug 1374338 - Search all ranges to avoid filtering r=mats
Adam Gashlin <agashlin@mozilla.com> - Fri, 01 Dec 2017 14:53:20 -0800 - rev 394949
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1374338 - Search all ranges to avoid filtering r=mats MozReview-Commit-ID: uu35565lfP
87305b25064ef513e0890696849bf0b06c48a586: Bug 1422289 - ContentLinkHandler should guess icon type from the extension when type is not defined. r=mak
Ed Lee <edilee@mozilla.com> - Fri, 01 Dec 2017 14:11:08 -0800 - rev 394948
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1422289 - ContentLinkHandler should guess icon type from the extension when type is not defined. r=mak MozReview-Commit-ID: HfuqudW77jM
793d2834b3e3c2d1411216740161f1735f5fa70d: Bug 1422995 - Use waitForNextFrame() instead of waitForFrame() to make sure the next requestAnimationFrame callback happen. r=birtles
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 05 Dec 2017 09:13:42 +0900 - rev 394947
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1422995 - Use waitForNextFrame() instead of waitForFrame() to make sure the next requestAnimationFrame callback happen. r=birtles With the conformant Promise handling (bug 1193394) and performing micro task checkpoint in Animation tick (bug 1416966), if we call waitForFrame() inside the callback for Animation.ready.then it will still be done in the same refresh driver's tick. MozReview-Commit-ID: GQJiDHHUlyD
afc17c7465c2371b7ba0f50c92ec065c099e9fd3: Bug 1403759 - part 2: Handle edit/selection commands like insertNewline: in TextInputHandler::HandleCommand() r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 02 Dec 2017 14:53:10 +0900 - rev 394946
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1403759 - part 2: Handle edit/selection commands like insertNewline: in TextInputHandler::HandleCommand() r=m_kato Let's make TextInputHandler::HandleCommand() handle other commands which are caused by Backspace, Delete, Tab, ArrowUp, ArrowDown, ArrowRight, ArrowLeft, PageUp, PageDown, Home, End and Escape keys with various modifiers. This patch makes Korean users can do most key operation in editor even with composing Hangul character. Note that this patch has a hack for cancelOperation: command. The command is typically fired for Escape key press. However, it's also fired for Command + Period. Unfortunately, this behavior is really odd if subclass of NSResponder implements |void cancelOperation:(id)sender|. If it's implemented, Cocoa doesn't call its |void keyDown:(NSEvent)theEvent|. Instead, it calls only |void doCommandBySelector:(SEL)aSelector| and |void cancelOperation:(id)sender| when Command + Period is pressed. Therefore, we cannot dispatch keydown nor keypress event for this key combination if we implement it. Therefore, this patch doesn't implement the method but handle it in doCommandBySelector even though the super class of ChildView cannot handle the command with this path. MozReview-Commit-ID: 4hS23SiwNJv
f5039cf4ead7e14b067052ab1ecff2277ecbeace: Bug 1403759 - part 1: Make TextInputHandler::InsertNewline() treat other commands r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 02 Dec 2017 10:46:31 +0900 - rev 394945
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1403759 - part 1: Make TextInputHandler::InsertNewline() treat other commands r=m_kato Currently, we handle insertNewline: of NSResponder with TextInputHandler::InsertNewline(). However, its implementation is useful for handling some other commands. So, let's rename it to HandleCommand() and make it take Command as its argument for handling specific behavior of each command. MozReview-Commit-ID: GgzQdTlVtYl
525f2f1623850d9de7f0b1995f0c68fe1a14e0cc: Bug 1422875 - Fix fake constraint to not apply to screensharing (on all platforms but android). r=pehrsons
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 04 Dec 2017 11:56:28 -0500 - rev 394944
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1422875 - Fix fake constraint to not apply to screensharing (on all platforms but android). r=pehrsons MozReview-Commit-ID: K35vaNAolEy
ba4cd2e93fec96898e55a1c4d23ed2a077c17d84: Bug 1422875 - Fix fake constraint to not apply to screensharing for media.navigator.permission.device codepath (aka Android) r=pehrsons
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 04 Dec 2017 11:25:50 -0500 - rev 394943
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1422875 - Fix fake constraint to not apply to screensharing for media.navigator.permission.device codepath (aka Android) r=pehrsons MozReview-Commit-ID: L9IIalMuFoC
d4e6ca9ed4da23167a30da7fb0ca5a1f19f14636: Bug 1421641 - Handle event listeners in mozSystemGroup and do full field states reset when clearing populated form. r=lchang
Ray Lin <ralin@mozilla.com> - Thu, 30 Nov 2017 16:31:44 +0800 - rev 394942
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1421641 - Handle event listeners in mozSystemGroup and do full field states reset when clearing populated form. r=lchang MozReview-Commit-ID: DcYD79LeA4N
87f5eb24ef4b510fa73db427e80bc011f6160bde: Bug 1414834 - re-land print IPC changes from bug 1319423; r=bobowen
Alex Gaynor <agaynor@mozilla.com> - Fri, 03 Nov 2017 14:37:15 -0400 - rev 394941
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1414834 - re-land print IPC changes from bug 1319423; r=bobowen With this patch print IPC no longer requires the child process to create files. Instead files are opened by the parent and a file descriptor is sent to the child. This will allow us to sandbox child processes more aggressively. MozReview-Commit-ID: GQWTYLV01kj
c7633e5266c0da789ce4503fb0a09979efa2580d: Bug 1421170 - Move the declarations of CustomElementUpgradeReaction and CustomElementCallbackReaction to CustomElementRegistry.cpp; r=smaug
Edgar Chen <echen@mozilla.com> - Tue, 28 Nov 2017 14:52:32 +0800 - rev 394940
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1421170 - Move the declarations of CustomElementUpgradeReaction and CustomElementCallbackReaction to CustomElementRegistry.cpp; r=smaug The CustomElementUpgradeReaction and CustomElementCallbackReaction are only used inside CustomElementRegistry.cpp, so we don't need to expose them in header file. MozReview-Commit-ID: 9lYwHeFIODi
ef99e0f85f43877252d3f39793e48041dd42d8a8: Backed out 4 changesets (bug 1420117) for mochitest failures layout/style/test/test_counter_descriptor_storage.html r=backout on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Tue, 05 Dec 2017 02:16:59 +0200 - rev 394939
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Backed out 4 changesets (bug 1420117) for mochitest failures layout/style/test/test_counter_descriptor_storage.html r=backout on a CLOSED TREE Backed out changeset 2560a150250d (bug 1420117) Backed out changeset 5cceea9740eb (bug 1420117) Backed out changeset 83b36cccea28 (bug 1420117) Backed out changeset f7292e7fee0e (bug 1420117)
9037e227d8ac796d570cfd094632700dd8abd59e: Backed out 1 changesets because the gecko part (bug 1420117) has to be backed out for the mochitests r=backout on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Tue, 05 Dec 2017 02:15:45 +0200 - rev 394938
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Backed out 1 changesets because the gecko part (bug 1420117) has to be backed out for the mochitests r=backout on a CLOSED TREE Backed out changeset baada68cad47
8ce23dc83f5dd00ead5a9b8dcdbc83c502c28805: merge mozilla-central to autoland. r=merge a=merge
Sebastian Hengst <archaeopteryx@coole-files.de> - Tue, 05 Dec 2017 01:37:16 +0200 - rev 394937
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
merge mozilla-central to autoland. r=merge a=merge
950dc8896010c8465d5a9075f015d12bf8880b9d: servo: Merge #19379 - Implemented sanitize_value for time input (from SWW13:htmlinput_sanitize_time); r=KiChjang
Simon Wörner <git@simon-woerner.de> - Mon, 04 Dec 2017 15:44:58 -0600 - rev 394936
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
servo: Merge #19379 - Implemented sanitize_value for time input (from SWW13:htmlinput_sanitize_time); r=KiChjang Implemented value sanitization for `<input type=time/>`. The value has the be valid time string (https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#valid-time-string) or set to empty string. --- The following test results look expected to me, but I'm not sure: ``` ▶ Unexpected subtest result in /html/semantics/forms/the-input-element/type-change-state.html: │ FAIL [expected PASS] change state from time to text │ → assert_equals: input.value should be foobar after change of state expected " foobar " but got "" │ FAIL [expected PASS] change state from time to search │ → assert_equals: input.value should be foobar after change of state expected " foobar " but got "" │ FAIL [expected PASS] change state from time to tel │ → assert_equals: input.value should be foobar after change of state expected " foobar " but got "" │ FAIL [expected PASS] change state from time to url │ → assert_equals: input.value should be foobar after change of state expected "foobar" but got "" │ FAIL [expected PASS] change state from time to password │ → assert_equals: input.value should be foobar after change of state expected " foobar " but got "" │ │ @http://web-platform.test:8000/html/semantics/forms/the-input-element/type-change-state.html:53:15 │ Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1489:20 │ test@http://web-platform.test:8000/resources/testharness.js:511:9 └ @http://web-platform.test:8000/html/semantics/forms/the-input-element/type-change-state.html:37:9 ▶ Unexpected subtest result in /html/semantics/forms/the-input-element/type-change-state.html: │ FAIL [expected PASS] change state from color to time │ → assert_equals: input.value should be #000000 after change of state expected "#000000" but got "" │ │ @http://web-platform.test:8000/html/semantics/forms/the-input-element/type-change-state.html:55:15 │ Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1489:20 │ test@http://web-platform.test:8000/resources/testharness.js:511:9 └ @http://web-platform.test:8000/html/semantics/forms/the-input-element/type-change-state.html:37:9 ``` All other tests do now `PASS` instead of `FAIL`. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix *part of* #19172 - [x] There are tests for these changes - [x] All tests `PASS` Source-Repo: https://github.com/servo/servo Source-Revision: eed3adc957fb3c52de24c560112533963572f525
facb23d70335db103f23fe988345f4b3d00aa8c9: bug 1397837 - remove vestigial references to "code signing" from PSM r=Cykesiopka,snorp
David Keeler <dkeeler@mozilla.com> - Fri, 01 Dec 2017 16:16:20 -0800 - rev 394935
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
bug 1397837 - remove vestigial references to "code signing" from PSM r=Cykesiopka,snorp As of bug 1257362, the platform does not verify code signing certificates in general, so anything involving the code signing trust of certificates can go. MozReview-Commit-ID: 9g9kM62xfYZ
bd96153b3e7c4503b60cd9eeda847a12492d0b87: Bug 1421806 - Use a custom element for the payment request dialog contents. r=jaws
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Fri, 01 Dec 2017 14:15:04 -0800 - rev 394934
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1421806 - Use a custom element for the payment request dialog contents. r=jaws The payment-dialog contents are already tested via browser-chrome tests MozReview-Commit-ID: IsFH2FteBpf
562dbac7f65ce1a567c715981541fab3e56c9d52: Bug 1421806 - Create a mixin to subscribe to payment store changes. r=jaws
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Thu, 30 Nov 2017 14:37:09 -0800 - rev 394933
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1421806 - Create a mixin to subscribe to payment store changes. r=jaws MozReview-Commit-ID: IGvvx7JDRtP
a68d5f4b11c097514273f273dfdfcc2b074c2fa1: Bug 1422432 - Remove PrintJSStack(). r=mrbkap
Andrew McCreight <continuation@gmail.com> - Fri, 01 Dec 2017 16:16:11 -0800 - rev 394932
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Bug 1422432 - Remove PrintJSStack(). r=mrbkap MozReview-Commit-ID: 8ObqjMxAzIR
0eea6706d04ad431d12911173b7406a1f23a3b6d: Backed out 1 changesets (bug 1422407) for failing browser chrome browser/extensions/shield-recipe-client/test/browser/browser_Heartbeat.js r=backout on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Tue, 05 Dec 2017 00:52:12 +0200 - rev 394931
Push 33025 by shindli@mozilla.com at Tue, 05 Dec 2017 09:57:50 +0000
Backed out 1 changesets (bug 1422407) for failing browser chrome browser/extensions/shield-recipe-client/test/browser/browser_Heartbeat.js r=backout on a CLOSED TREE Backed out changeset a726c48b2540 (bug 1422407)
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip