{"push_id":2344594118,"size":47,"distinct_size":1,"ref":"refs/heads/chromium-export-cl-920261","head":"9d94e7dd468d24503161abe2b17928ce4c07767f","before":"40ee35666ab2d73c9cc31b2aea7dc98e7b31dd89","commits":[{"sha":"d04c0d50dbbf7752c27957005a5a659701b781ad","author":{"name":"L. David Baron","email":"cb70a51363da8308d3ca73cc7b3033e5d7ccb14b@dbaron.org"},"message":"Add tests for the breaking of a multicolumn across columns, including backgrounds and column rules. (#9527)\n\nThe *-nobackground-* tests pass in Firefox and Chrome, and the others\r\npass in Chrome and fail in Firefox due to what I (as a Gecko\r\nimplementor) consider to be a Firefox bug.  I haven't yet tested other\r\nengines.  (Though -nobackground-003 fails in Firefox due to a different\r\nbug, and multicol-breaking-002 doesn't trigger the background-related\r\nFirefox bug.)\r\n\r\nGiven the level of ambiguity in the multicol spec, I suspect these tests\r\nprobably test some things that aren't formally specified.  However, I\r\nthink that's probably OK for now.  One issue that I know of that they\r\ndepend on the spec for is w3c/csswg-drafts#2309.","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/d04c0d50dbbf7752c27957005a5a659701b781ad"},{"sha":"2b4cdad36bd267e39565ebaab5982b9b4c482e53","author":{"name":"joanmarie","email":"ddd59ceacb38662cb73c1d43c641e2771cbdbcd9@igalia.com"},"message":"Add initial test set for Accessible Name and Description Computation 1.1 (#9540)\n\nNote that many of the tests are currently named with a number. Those\r\ntests were taken from the original (1.0) test suite created by the\r\nPFWG, and the file names are being preserved to facilitate comparison\r\nof results.","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/2b4cdad36bd267e39565ebaab5982b9b4c482e53"},{"sha":"4d81f72949c33b312ea1a0cc35636a2bd8c9cc9a","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Rename tests in timing-model/animations to match spec section titles;\n\nIn this folder we have a mixture of tests named after the procedure they are\ntesting or the section that contains the procedure. The latter seems to be more\ncommon and makes it a little easier to check that all sections are tested so\nthis patch renames files to refer to the section titles instead. It also updates\na few of the test file titles and URLs.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: 0634cd8f08ebe0905a9188fb1398c7b5f889c5dc\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/4d81f72949c33b312ea1a0cc35636a2bd8c9cc9a"},{"sha":"78c51f736a22c330dcceac70be98b48d65dda5ac","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Use async/await in timing-model/animations tests;\n\nUsing async/await makes these tests easier to read and appears to be supported\nin all browsers now. This patch updates the tests in\nweb-animations/timing-model/animations since we will update these tests later in\nthis patch series and it will be easier if we convert them to using async first.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: c8ee4a012dae506ae06bb5b2ad50942b04c1aaaa\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/78c51f736a22c330dcceac70be98b48d65dda5ac"},{"sha":"8616b71a6fd1d5aafd1d207ce49ddfd6dd9559f7","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Move playback rate test to timing-model;\n\nThe test under web-animations/interfaces/Animation/playbackRate.html is really\ntesting the timing model so this patch moves it there. We'll simplify it in the\nnext patch.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: c2c352456a4cf62dcc12f851138b04397675a445\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/8616b71a6fd1d5aafd1d207ce49ddfd6dd9559f7"},{"sha":"496f9b98caf19b589ca5f04d235c395f654eae2b","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Simplify playback rate setting test;\n\nI didn't like the way these tests were written so I decided to rewrite them to\nmake it more clear what they are trying to test.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: b93a8879555d2fa7e7d4e00a275513a3a6338b35\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/496f9b98caf19b589ca5f04d235c395f654eae2b"},{"sha":"68544c4451651916a24b762a185d68c4bc579ff1","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Move finishing tests to timing-model;\n\nThese tests are not testing the interface so much as the 'finish an animation'\nprocedure.\n\nThis patch simply moves the tests as-is. They will be simplified in the next\npatch in this series.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: b86e1331cb36634fd33677043b61fc0c1d8485bc\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/68544c4451651916a24b762a185d68c4bc579ff1"},{"sha":"42c27bb938fb91414a13628e9e6c651f748a5f3c","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Tidy up tests for \"finishing an animation\";\n\nThese patches update these tests as follows:\n\n* Used async/await where it simplifies the tests\n* Updated the test descriptions to reflect what they are testing in the timing\n  model\n* Fixed a couple of bugs where we set the playbackRate on a pause-pending\n  animation (which causes it to no longer be pause-pending).\n\nIn the process I noticed a couple of tests that don't really belong here. They\nwill be moved in the next patch.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: 44ddf14fd3346658c3223f13652073fafbfa48fa\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/42c27bb938fb91414a13628e9e6c651f748a5f3c"},{"sha":"454b4dbd21f8f5341ec1a02fdb5e9ab16cb79ad0","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Further divide up finishing tests;\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: a1a5840a6bb53e305ba02bcbeb215659342d0edb\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/454b4dbd21f8f5341ec1a02fdb5e9ab16cb79ad0"},{"sha":"e60dd1470b69fb3c76135c57cb5ab80aca4354e1","author":{"name":"Brian Birtles","email":"913c8884b4f68b8218a318cad415807910a9ef34@gmail.com"},"message":"Add tests for Animation.updatePlaybackRate;\n\nThese tests test the behavior introduced in the following changesets to the Web\nAnimations specification:\n\n  1. https://github.com/w3c/csswg-drafts/commit/5af5e276badf4df0271bcfa0b8e7837fff24133a\n  2. https://github.com/w3c/csswg-drafts/commit/673f6fc1269829743c707c53dcb04092f958de35\n\nwhich can be viewed as a merged diff at:\n\n  https://gist.github.com/birtles/d147eb2e0e2d4d37fadf217abd709411\n\nSee the following spec issues:\n\n  1. https://github.com/w3c/csswg-drafts/issues/2059\n  2. https://github.com/w3c/csswg-drafts/issues/2266\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659\ngecko-commit: 7465cb110ae5ec2e2ca73182caf5293f0efc8fd5\ngecko-integration-branch: autoland\ngecko-reviewers: hiro","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/e60dd1470b69fb3c76135c57cb5ab80aca4354e1"},{"sha":"b52a7a29208647f209f06ac2e6321987023c196c","author":{"name":"Darren Shen","email":"4bc263165a483d2fb2630508013a82be80ff548d@chromium.org"},"message":"[css-typed-om] Make StylePropertyMap.set work with calcs.\n\nCurrently StylePropertyMap.set doesn't actually work with calcs.\nThe current way to check if something is, say, a <length> is to\ncheck its CSSStyleValue::Type. However, this doesn't return\nthe right value for CSSMathValues, whose types may be quite\ncomplicated.\n\nThe correct way is to use the CSSNumericValue matching algorthms:\nCSSNumericValue::MatchesLength, which also takes into account\nCSSMathValues and percent hints.\n\nThis patch changes the following to make this work:\n\n- Removed base types from CSSStyleValue::StyleValueType. A base type\n  like \"length\" is not really a CSSStyleValue type.\n- Removed unused StyleValueTypeToString.\n- Changed \"Percent\" to \"Percentage\" in CSSProperties.json5 as that's\n  the correct term.\n- Changed make_cssom_types to use the matching algorithms from\n  CSSNumericValue.\n\nBug: 545318\nChange-Id: I16aa71a4873e9992749f0f52ba641671d109170e\nReviewed-on: https://chromium-review.googlesource.com/901002\nCommit-Queue: Darren Shen <shend@chromium.org>\nReviewed-by: nainar <nainar@chromium.org>\nCr-Commit-Position: refs/heads/master@{#537206}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/b52a7a29208647f209f06ac2e6321987023c196c"},{"sha":"e7607dad61b547e88d1f06a67b1514a3242600ec","author":{"name":"Matt Falkenhagen","email":"995f91faad1d0f61ed99868b7c551e2c80e44a4d@chromium.org"},"message":"service worker: Disallow interception for EMBED and OBJECT requests.\n\nThis matches the service worker specification and Firefox.\n\nThis change itself is probably not enough to skip all EMBED/OBJECT\nrequests, as some requests get initiated by PepperURLLoaderHost or\nMimeHandlerViewContainer.\n\nIn implementor concerns:\nhttps://w3c.github.io/ServiceWorker/#implementer-concerns\n\"Plug-ins should not load via service workers. As plug-ins may get their\nsecurity origins from their own urls, the embedding service worker cannot\nhandle it. For this reason, the Handle Fetch algorithm makes the\npotential-navigation-or-subresource request (whose context is either <embed> or\n<object>) immediately fallback to the network without dispatching fetch event.\"\n\nIn Handle Fetch:\nhttps://w3c.github.io/ServiceWorker/#handle-fetch\n\"If request is a potential-navigation-or-subresource request, then:\nReturn null.\"\n\nR=kinuko, yhirano\n\nBug: 771933\nChange-Id: Ia04ae8dec8c968de6a73dca088aa88a67b21718a\nReviewed-on: https://chromium-review.googlesource.com/923445\nReviewed-by: Kinuko Yasuda <kinuko@chromium.org>\nCommit-Queue: Matt Falkenhagen <falken@chromium.org>\nCr-Commit-Position: refs/heads/master@{#537245}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/e7607dad61b547e88d1f06a67b1514a3242600ec"},{"sha":"ae06fa4ce5d170f7f34e979b014315e318344ec4","author":{"name":"Morten Stenshorne","email":"7c2ad3f66c77169ecf8c75255159a94f5adade71@chromium.org"},"message":"[LayoutNG] Don't add zero-width floats to the exclusion space.\n\nThe only thing such floats should affect is the block position of\nsubsequent floats (float rule §5 [1] and clearance). They should not\naffect the inline position or inline size of subsequent floats or new\nformatting contexts.\n\nThe spec isn't actually clear here, although the browsers agree on the\nabove. Submitted https://github.com/w3c/csswg-drafts/issues/2312\n\n[1] https://www.w3.org/TR/CSS22/visuren.html#float-position\n\nCq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng\nChange-Id: Ia9e724c8a58fcb017f86f26bdf90394f09414f4e\nReviewed-on: https://chromium-review.googlesource.com/919065\nReviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>\nCommit-Queue: Morten Stenshorne <mstensho@chromium.org>\nCr-Commit-Position: refs/heads/master@{#537274}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/ae06fa4ce5d170f7f34e979b014315e318344ec4"},{"sha":"b7bcc2ee447b163456488d0e26e746d5fe6b9283","author":{"name":"Emilio Cobos Álvarez","email":"46e7bbfc7c824487af96584c3673a74b15809d87@crisal.io"},"message":"Test that click events are properly dispatched to non-disabled form controls in presence of dynamic changes.\n\nCo-authored-by: Andreas Farre <afarre@mozilla.com>\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1405087\ngecko-commit: aad5349b3458bc3414e274b33fa86a1123901ff2\ngecko-integration-branch: autoland\ngecko-reviewers: bz","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/b7bcc2ee447b163456488d0e26e746d5fe6b9283"},{"sha":"00869007356d37972ad946c86c530eafc19c7b8c","author":{"name":"Andreas Tolfsen","email":"2f468e8adda935090f46a3f4c91a42aade53c29a@sny.no"},"message":"Add navigator.webdriver attribute.\n\nThis patch adds an enumerable, configurable, readonly attribute\n\"webdriver\" to the Navigator object.  The attribute is true when the\n-marionette flag has been passed to Firefox or the marionette.enabled\npreference is true.  Otherwise it is false.\n\nThe definition of the interface is found in the WebDriver standard:\n\n\thttps://w3c.github.io/webdriver/webdriver-spec.html#interface\n\nThe navigator.webdriver attribute is meant as an indication to web\nauthors that a document is visited by WebDriver.  It is important\nto stress that it is not meant as a fool-proof way to detect that\na website is being visited by a browser automation tool, but as a\ntool for web documents to take alternate code paths.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1169290\ngecko-commit: 9ddfd21554293dec5a4bf2e5375ae4f3c9f2ded0\ngecko-integration-branch: autoland\ngecko-reviewers: bz, maja_zf","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/00869007356d37972ad946c86c530eafc19c7b8c"},{"sha":"b6df67b31d90ae3c007efc47a52e41901bf25e36","author":{"name":"Emilio Cobos Álvarez","email":"46e7bbfc7c824487af96584c3673a74b15809d87@crisal.io"},"message":"Test the serialization of the font shorthand.\nbugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436031\ngecko-commit: 7806af854343c043a2645a4034fdc7812f65daad\ngecko-integration-branch: central\ngecko-reviewers: xidorn","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/b6df67b31d90ae3c007efc47a52e41901bf25e36"},{"sha":"81ada4212ece1e2f5c6cc560d6b2f45593679e93","author":{"name":"Raymond Toy","email":"1bb15d98ed9bea65ffda565f99e490d3c793ae29@chromium.org"},"message":"Fix timeouts in WPT AudioParam tests\n\nReplace the tests that are using ScriptProcessor and online contexts\nwith an offline context and verify all the output values instead of\njust one.\n\nThis change exposed a couple of issues:\n  - setTargetAtTime wasn't actually testing setTargetAtTime because a\n    linearRampToValueAtTime event was called at the same time,\n    effectively replacing the setTargetAtTime event\n  - linearRampToValue and exponentialRampToValue tests expose bugs in\n    Chrome's implementation of these when the event is scheduled in\n    the past, and there is no preceding event.\n\nBug: 812285, 626703\nChange-Id: Iad3f54dd4373411431c019de44d4c3bad07587ff\nReviewed-on: https://chromium-review.googlesource.com/919151\nCommit-Queue: Raymond Toy <rtoy@chromium.org>\nReviewed-by: Hongchan Choi <hongchan@chromium.org>\nCr-Commit-Position: refs/heads/master@{#537311}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/81ada4212ece1e2f5c6cc560d6b2f45593679e93"},{"sha":"54fa770d8e356a5f4fa7861f2103b6a7b9175eb2","author":{"name":"Fernando Jiménez Moreno","email":"0b3750d0acfcd197365fda735aa2d2bceb94dc2a@gmail.com"},"message":"Implement element.innerText setter\n\nUpstreamed from https://github.com/servo/servo/pull/20054 [ci skip]","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/54fa770d8e356a5f4fa7861f2103b6a7b9175eb2"},{"sha":"256f5784994a108de0ec043602254674a8122747","author":{"name":"Servo WPT Sync","email":"41adcc22376a25b4b77dd5e3385747a96297f624@users.noreply.github.com"},"message":"Merge pull request #9561 from w3c/sync_54fa770d8e356a5f4fa7861f2103b6a7b9175eb2\n\nMerge pull request #9561 from sync_54fa770d8e356a5f4fa7861f2103b6a7b9175eb2","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/256f5784994a108de0ec043602254674a8122747"},{"sha":"cb2d75fd13182ab3bdd7189dafe2ff7bbf4acd56","author":{"name":"jugglinmike","email":"9c718659c7cd4c715abab71c311def3c89922b67@mikepennisi.com"},"message":"wptrunner: Fix regression in config, interpreter (#9480)\n\nPrior to the application of this patch, the configuration property named\r\n`host` was required to expand the templated JSON file maintained within\r\nthe WPT CLI. By removing the property from some browser definitions\r\nwithout updating that template, commit 1b4f253 introduced failures when\r\nusing the `run` sub-command with the effected browsers.\r\n\r\nRefactor the logic for generating the configuration to use an in-memory\r\nrepresentation (instead of a file-based template) and conditionally\r\nextend this object with the `host` option for browsers which specify it.\r\nDocument the rationale for the browser which requires this\r\nfunctionality.","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/cb2d75fd13182ab3bdd7189dafe2ff7bbf4acd56"}]}
{"actor":{"display_login":"chromium-wpt-export-bot"}}