81bce4779be2feca70ace6a1a616b0c7dc042e6b: Bug 1413326 - Discard stacktraces of WebDriver errors in response. r?whimboo draft
Andreas Tolfsen <ato@sny.no> - Wed, 17 Jan 2018 14:19:24 +0000 - rev 721591
Push 95882 by bmo:ato@sny.no at Wed, 17 Jan 2018 14:25:05 +0000
Bug 1413326 - Discard stacktraces of WebDriver errors in response. r?whimboo This patch changes Marionette to discard stacktraces from errors that extends the WebDriverError prototype. This has the effect that programming errors (such as TypeError, RangeError, et al.) will be sent with a stacktrace because WebDriver related errors are considered "expected". When Marionette returns with an element not found error, this is intended behaviour and a stacktrace is of extremely limited value. Indeed, including the stacktrace might mislead users to think that the returned error is an implementation problem in the driver. Programming errors will also be logged in full through error.report in stdout, as usual. MozReview-Commit-ID: 12UIEmQ0uoG
e07dd380a84614a3e6b8a9000883af092197b021: Bug 1427952 - Make hostname in Canvas permission prompt more prominent. r?johannh draft
Prathiksha <prathikshaprasadsuman@gmail.com> - Wed, 17 Jan 2018 20:03:55 +0530 - rev 721590
Push 95881 by bmo:prathikshaprasadsuman@gmail.com at Wed, 17 Jan 2018 14:22:47 +0000
Bug 1427952 - Make hostname in Canvas permission prompt more prominent. r?johannh MozReview-Commit-ID: DKUCWoDLutu
724dfb33df76b4f7835f6e34614a7f6a65b5051a: Bug 1430925 - Avoid JSON Viewer test timeouts when RequireJS fails draft
Oriol Brufau <oriol-bugzilla@hotmail.com> - Mon, 15 Jan 2018 03:45:36 +0100 - rev 721589
Push 95880 by bmo:oriol-bugzilla@hotmail.com at Wed, 17 Jan 2018 14:13:51 +0000
Bug 1430925 - Avoid JSON Viewer test timeouts when RequireJS fails MozReview-Commit-ID: AEawTHPW2Fn
38d7d0900fadb598a7d8776bd98fb9d00a33af70: Bug 1429511 - Update mozrunner crate repo URL. r?jgraham draft
Andreas Tolfsen <ato@sny.no> - Fri, 12 Jan 2018 16:12:30 +0000 - rev 721588
Push 95879 by bmo:ato@sny.no at Wed, 17 Jan 2018 13:57:34 +0000
Bug 1429511 - Update mozrunner crate repo URL. r?jgraham MozReview-Commit-ID: 8NCsKp4q2JQ
f597fd65740da8ec3264d561725fd78bf4640e15: Bug 1429511 - Move geckodriver to in-tree mozrunner. r?jgraham draft
Andreas Tolfsen <ato@sny.no> - Fri, 12 Jan 2018 15:36:55 +0000 - rev 721587
Push 95879 by bmo:ato@sny.no at Wed, 17 Jan 2018 13:57:34 +0000
Bug 1429511 - Move geckodriver to in-tree mozrunner. r?jgraham This deletes the third-party mozrunner crate off crates.io in favour of using the in-tree version from testing/mozbase/rust/mozrunner. MozReview-Commit-ID: 6xQZ99FYrdP
29496d12f023c52e20466000c2e679c9cf67351c: Bug 1429511 - Move Rust port of mozrunner to central. r?ahal draft
Andreas Tolfsen <ato@sny.no> - Fri, 12 Jan 2018 15:31:20 +0000 - rev 721586
Push 95879 by bmo:ato@sny.no at Wed, 17 Jan 2018 13:57:34 +0000
Bug 1429511 - Move Rust port of mozrunner to central. r?ahal This moves the Rust crate mozrunner into central from GitHub. The old repository will be graveyarded: https://github.com/jgraham/rust_mozrunner The git history is not considered important, hence this does not overlay that onto central like we did for testing/geckodriver and testing/webdriver. MozReview-Commit-ID: J4ZYdow2Lkw
fca51cb43951784007d9997d0c95da5269053dd5: Bug 1404378 - Enable browser_webconsole_iframe_wrong_hud.js in new console frontend; r=jdescottes. draft
Nicolas Chevobbe <nchevobbe@mozilla.com> - Wed, 17 Jan 2018 09:23:12 +0100 - rev 721585
Push 95878 by bmo:nchevobbe@mozilla.com at Wed, 17 Jan 2018 13:56:25 +0000
Bug 1404378 - Enable browser_webconsole_iframe_wrong_hud.js in new console frontend; r=jdescottes. MozReview-Commit-ID: HBfA7lXjVdI
4047a16519ad6e76db2fa6e0717f3b20ee85ebc0: Bug 1430152 - Move geckodriver to in-tree mozversion. r?jgraham draft
Andreas Tolfsen <ato@sny.no> - Fri, 12 Jan 2018 16:09:28 +0000 - rev 721584
Push 95877 by bmo:ato@sny.no at Wed, 17 Jan 2018 13:53:34 +0000
Bug 1430152 - Move geckodriver to in-tree mozversion. r?jgraham MozReview-Commit-ID: A8yb1joLYfv
7e2e0484a193cc4823e0e7f73174469d93ce2917: Bug 1430152 - Move Rust port of mozversion to central. r?ahal draft
Andreas Tolfsen <ato@sny.no> - Fri, 12 Jan 2018 16:08:07 +0000 - rev 721583
Push 95877 by bmo:ato@sny.no at Wed, 17 Jan 2018 13:53:34 +0000
Bug 1430152 - Move Rust port of mozversion to central. r?ahal This moves the Rust crate mozversion into central from GitHub. The old repository will be graveyarded: https://github.com/jgraham/mozversion The git history is not considered important, hence this does not overlay that onto central like we did for testing/geckodriver and testing/webdriver. MozReview-Commit-ID: HeBggGmGsg6
24a6b3749509fc358b0d14a1f2cdf6579c237fd0: Bug 1431041: Make placeholder apply to <input type="number">. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 17 Jan 2018 14:52:01 +0100 - rev 721582
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1431041: Make placeholder apply to <input type="number">. r?smaug MozReview-Commit-ID: GLbdLxHLiH4
d70725608877139352cfa747e76dcc5f7411b548: fixup! Bug 1430844: Make resize reflow sound re. viewport units. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 17 Jan 2018 14:42:53 +0100 - rev 721581
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
fixup! Bug 1430844: Make resize reflow sound re. viewport units. r?bz
d8ffa1911feb040140ea75be9212ba3182f018bb: Bug 1409672: Hook in the invalidator stuff. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 16 Jan 2018 15:14:39 +0100 - rev 721580
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1409672: Hook in the invalidator stuff. r?xidorn MozReview-Commit-ID: EoSMrYPS7dl
94923d45b9d4938dafd21e135947fdafea7d39da: Bug 1428491: Remove redundant mBindingManager member in ServoStyleSet. r=heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 05 Jan 2018 20:17:26 +0100 - rev 721579
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1428491: Remove redundant mBindingManager member in ServoStyleSet. r=heycam MozReview-Commit-ID: KMiivgik0fr
4a415ca3fb22087d39622677610fff694d74b049: Bug 1428491: Make the style set know about a document, not a pres context. r=heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 05 Jan 2018 13:51:08 +0100 - rev 721578
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1428491: Make the style set know about a document, not a pres context. r=heycam MozReview-Commit-ID: I7T41NiHuJv
26778f0b8737a3c9b33f21585560173f7572ff0f: Bug 1430844: Add assertions that would've caught this. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 16 Jan 2018 20:48:58 +0100 - rev 721577
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1430844: Add assertions that would've caught this. r?bz MozReview-Commit-ID: 1UfhIRn2We2
9c758aff01688660cc63828601505a4fe2778f25: Bug 1430844: Make resize reflow sound re. viewport units. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 16 Jan 2018 19:42:28 +0100 - rev 721576
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1430844: Make resize reflow sound re. viewport units. r?bz In particular, we set the pres context visible area _before_ processing restyles. This causes inconsistencies when resolving viewport units. In particular, the resulting style tree will have some units resolved in terms of the old size, and some in terms of the new size, depending on whatever is dirty, because we don't flush the pending media query changes. Also, some sizes are resolved against the unconstrained size because of the shrink-to-fit stuff. Fix this by flushing _before_ in this case, instead of after, since we're going to set the size to an actual value later when reflowing the root frame. MozReview-Commit-ID: ExI5yTJCjGp
369cdef4398437c6193ad3dabd619ab1abaff2f3: Bug 1430608: Make nsMediaFeatures work with a document, not a pres context. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 15 Jan 2018 15:33:25 +0100 - rev 721575
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1430608: Make nsMediaFeatures work with a document, not a pres context. r?heycam Returning a zero-sized viewport in the case there's no shell / pres context. For now, no other change yet. After this we can start tweaking the ShadowRoot Stylist setup, and even try to return computed styles without a document \o/. MozReview-Commit-ID: 3cT2PKQISri
4fdc02834e6291dc439bff0f5f6fcca9feccfc6a: Bug 1429248: Special-case pseudo style attributes to avoid ignoring doc colors. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 10 Jan 2018 00:45:23 +0100 - rev 721574
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1429248: Special-case pseudo style attributes to avoid ignoring doc colors. r?heycam That way color pickers work even when this setting is on. We always know that pseudo-element style attributes are trusted. MozReview-Commit-ID: 6IdmRaMzj6I
0ac9b67599d749fb273bf60ece999965f40578c1: Bug 1429846: Fix slotted invalidation. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 11 Jan 2018 17:39:47 +0100 - rev 721573
Push 95876 by bmo:emilio@crisal.io at Wed, 17 Jan 2018 13:53:03 +0000
Bug 1429846: Fix slotted invalidation. r?heycam This is a partial revert of https://github.com/servo/servo/commit/ce1d8cd232dfbc9e0a52f9467ba2bc209087ea63 If you're in a shadow tree, you may not be slotted but you still need to look at the slotted rules, since a <slot> could be a descendant of yours. Just use the same invalidation map everywhere, and remove complexity. This means that we can do some extra work while trying to gather invalidation if there are slotted rules, but I don't think it's a problem. The test is ported from https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/fast/css/invalidation/slotted.html?l=1&rcl=58d68fdf783d7edde1c82a642e037464861f2787 Curiously, Blink fails the test as written, presumably because they don't flush styles from getComputedStyle correctly (in their test they do via updateStyleAndReturnAffectedElementCount), due to <slot>s not being in the flat tree in their implementation. MozReview-Commit-ID: 6b7BQ6bGMgd
159d23009bb3d0c20166d84ea73cbe12e17844e7: Bug 1430575 - Add validity state check for WebDriver:ElementClear. r?automatedtester draft
Andreas Tolfsen <ato@sny.no> - Mon, 15 Jan 2018 17:17:11 +0000 - rev 721572
Push 95875 by bmo:ato@sny.no at Wed, 17 Jan 2018 13:45:56 +0000
Bug 1430575 - Add validity state check for WebDriver:ElementClear. r?automatedtester This patch checks that the element satisfies its form control constraints, as well as being empty, before deciding not to clear the element. This will make it possible to clear elements that have invalid input. The "clear a resettable element" algorithm is missing a check of the <input> element's ValidityState. WebDriver:ElementClear has a subtle bug that only manifests in Gecko because Blink rejects invalid key input to validation fields such as <input type=number>, but Gecko does not. The value property of <input type=number> will not be updated unless the input is actually valid, which means the first step of the algorithm will pass irregardless of whether the user has actually modified it. MozReview-Commit-ID: C2M3Fl1iKx6
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip