{"push_id":2451009159,"size":12,"distinct_size":1,"ref":"refs/heads/chromium-export-cl-898009","head":"36d0a89072454a9bba0c452a26bcfacdb4aa4a5a","before":"dfc1a1c06fbb7c78f5b8bbb549a876a2216fe04b","commits":[{"sha":"190c3feba3a42cbc4c32facd7994c190589d889e","author":{"name":"Liam R. E. Quin","email":"3dfd73bacfd0425b455feee5dd36c581a603bea0@w3.org"},"message":"[svg 2 text] test for length and indexed access","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/190c3feba3a42cbc4c32facd7994c190589d889e"},{"sha":"771a209d64f3c07430b5b0090bc61fc31485f0b9","author":{"name":"Tom Anderson","email":"b710446f72aee52256d8f9a2212ea008a02718e3@chromium.org"},"message":"Replace Arial with Arimo GCS font\n\nBUG=787020\nTBR=dpranke,asvitkine\n\nChange-Id: I38740d1ee9fe621eabd5416f1a87b23a71fbb7e7\nReviewed-on: https://chromium-review.googlesource.com/986812\nReviewed-by: Thomas Anderson <thomasanderson@chromium.org>\nCommit-Queue: Thomas Anderson <thomasanderson@chromium.org>\nCr-Commit-Position: refs/heads/master@{#547246}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/771a209d64f3c07430b5b0090bc61fc31485f0b9"},{"sha":"21be95d42621e2f7f4e2a211ce9d4a50d925aa73","author":{"name":"Luke Bjerring","email":"2645140b58cc64bbf16aa454157e7f7e1656f52d@users.noreply.github.com"},"message":"Revert #10240","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/21be95d42621e2f7f4e2a211ce9d4a50d925aa73"},{"sha":"fc33be9acfbf8e883fd9683c527aab22d842542b","author":{"name":"Eric Holk","email":"1099ee83d7f9134ad0c6bab27f6bbb0394494bef@chromium.org"},"message":"Delete wasm/many-memories.window.js WPT test\n\nTesting for a specific number is causing problems and determining the right\nnumber is problematic in general, as running out of memory is always a\nlegitimate possiblity. See https://github.com/WebAssembly/design/issues/1167 for\nmore discussion. In light of this, it's best to just remove the test.\n\nBug:\nChange-Id: I66e248c8ab851bca0c54fa6fe13b6e93e55f1264\nReviewed-on: https://chromium-review.googlesource.com/851081\nCommit-Queue: Brad Nelson <bradnelson@chromium.org>\nReviewed-by: Brad Nelson <bradnelson@chromium.org>\nCr-Commit-Position: refs/heads/master@{#547333}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/fc33be9acfbf8e883fd9683c527aab22d842542b"},{"sha":"1331d68a18a959d74c73142ed984c65f455ce1fe","author":{"name":"kaixinjxq","email":"14c0afb1b0371c1e752a1b4d29ca59440b4803d1@intel.com"},"message":"Add a DataTransfer test\n\n The types attribute must return this DataTransfer object's types array","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/1331d68a18a959d74c73142ed984c65f455ce1fe"},{"sha":"3589b85af366d5c53bf03cfeb5e0ccb3ac2a38e9","author":{"name":"Chris Lilley","email":"4181b934c2715a2bba60cdb3cc1b35b2777d1c23@w3.org"},"message":"Merge pull request #10172 from liamquin/svg-lists-have-length\n\n[svg 2 text] add scripted tests for length and indexed access","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/3589b85af366d5c53bf03cfeb5e0ccb3ac2a38e9"},{"sha":"d68f044162867a8283c6d4adbf19e9587b6ea2fa","author":{"name":"Tsuyoshi Horo","email":"95f17878c8ed0c64a68b3503813fe4b0676ea8c7@chromium.org"},"message":"Set SkipServiceWorker flag for synchronous loads from the main thread.\n\nBefore 5e1b52dd7e828fb2e4bd69f599c0c30eec3e873c, synchronous XHR on worker\nwas handled by service workers. It is because the |is_sync_load| was false\nwhen the sync request is from worker thread. But after the CL, the\n|is_sync_load| flag for the sync request from worker became true, so the request\nwill not go to the service worker.\n\nThis CL will fix this by\n - Set the SkipServiceWorker flag for synchronous loads from the main thread\n   in the renderer process. (FetchParameters.cpp)\n - Don't set skip_service_worker even if is_sync_load is true in the browser\n   process. (resource_dispatcher_host_impl.cc)\n\nBug: 706331,827473\nChange-Id: I186bc97f3f8d298e0a04942d0ec4b708b3022cc1\nReviewed-on: https://chromium-review.googlesource.com/989376\nReviewed-by: Kinuko Yasuda <kinuko@chromium.org>\nCommit-Queue: Tsuyoshi Horo <horo@chromium.org>\nCr-Commit-Position: refs/heads/master@{#547407}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/d68f044162867a8283c6d4adbf19e9587b6ea2fa"},{"sha":"94b33b573a069ae5170104ca581a354a35762536","author":{"name":"Chris Nardi","email":"637f5431d9b3928ad4c35e7468312ae633cdc1da@hotmail.com"},"message":"Update IRC archive link (#10266)\n\nThe link was dead; update to the new link.","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/94b33b573a069ae5170104ca581a354a35762536"},{"sha":"bc209c37228e5071e3fc8d3bcbc78c7b09db57a8","author":{"name":"Kent Tamura","email":"00b53901e8e628f98222266badb3a8be501798c4@chromium.org"},"message":"custom-elements: Add tests for callback timing with HTML parser.\n\nBug: 821831\nChange-Id: I5b3e1978e37ce34e6fb885ca1077ea90ab2f494c\nReviewed-on: https://chromium-review.googlesource.com/987972\nReviewed-by: Takayoshi Kochi <kochi@chromium.org>\nCommit-Queue: Kent Tamura <tkent@chromium.org>\nCr-Commit-Position: refs/heads/master@{#547424}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/bc209c37228e5071e3fc8d3bcbc78c7b09db57a8"},{"sha":"e4efc10a82630de47f920a737aa8ea94845191af","author":{"name":"Manuel Rego Casasnovas","email":"399fe6e1242036568b02b06b8089d6dbc5fd2900@igalia.com"},"message":"[css-grid] Fix resolution of percentage paddings and margins of grid items\n\nWe were not resolving properly percentage paddings and margins\nfor tracks that have something like minmax(auto, 100px).\nThe reason was that while computing the minimum size of a grid item,\nthe percentages were resolved against the inline size of the grid container.\nBut for grid items we shouldn't never use the grid container size,\nbut the grid area size, as that's their containing block.\n\nThe patch modifies ContainingBlockLogicalWidthForContent() and\nContainingBlockLogicalHeightForContent() in LayoutBox,\nso for grid items we return 0 if the area size hasn't been set yet.\nWe never want to use the grid container's sizes in these cases.\n\nBUG=808758\nTEST=external/wpt/css/css-grid/grid-items/grid-items-percentage-margins-*\nTEST=external/wpt/css/css-grid/grid-items/grid-items-percentage-paddings-*\n\nChange-Id: Ib142e51aee1fe623d38688469b179f01f82eb07b\nReviewed-on: https://chromium-review.googlesource.com/980756\nReviewed-by: Javier Fernandez <jfernandez@igalia.com>\nCommit-Queue: Manuel Rego Casasnovas <rego@igalia.com>\nCr-Commit-Position: refs/heads/master@{#547417}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/e4efc10a82630de47f920a737aa8ea94845191af"},{"sha":"af485dcf5f9fb6c1892908ab850b2bf49bc765a2","author":{"name":"Chris Nardi","email":"e977f1f2f1cb862b954d9c5a8bfbdfb26a9bd69a@chromium.org"},"message":"Remove test that CSSStyleSheet.media is read-only\n\nstyle-sheet-interfaces-001.html tested that styleSheet.media was\nread-only, but the spec changed to add a [PutForwards] attribute to\n|media|, meanining that the attribute is no longer truly read-only.\nassert_readonly can have side-effects if the property has a\n[PutForwards] attribute, so remove this check, as it was causing the\nnext test to fail.\n\nBug: 821780\nChange-Id: I77bee2f11484f6e679e4aee6b0641179c686d1d3\nReviewed-on: https://chromium-review.googlesource.com/989407\nReviewed-by: Emil A Eklund <eae@chromium.org>\nCommit-Queue: Chris Nardi <cnardi@chromium.org>\nCr-Commit-Position: refs/heads/master@{#547451}","distinct":false,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/af485dcf5f9fb6c1892908ab850b2bf49bc765a2"},{"sha":"36d0a89072454a9bba0c452a26bcfacdb4aa4a5a","author":{"name":"Marijn Kruisselbrink","email":"d359d875e3600efb7042edc50fb63d2a12ba0279@chromium.org"},"message":"[Mojo Blob URLs] Resolve navigation blob URLs in blink.\n\nThis makes sure that no race conditions exist between navigating to a\nblob URL and revoking it. Currently only implemented for the network\nservice code path.\n\nAlso add one more navigation-then-revoke WPT test, as the existing tests\ndidn't cover the NavigationScheduler code-path.\n\nDesign doc: https://docs.google.com/document/d/1DqVcTWE9Qb_3KpIRH2bFV-6hWEr8S92c4ppY67YL1KI/edit#heading=h.n4fzuc6mgziv\n\nFurther navigation cases are handled in https://chromium-review.googlesource.com/c/chromium/src/+/899508.\n\nBug: 800901\nCq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo\nChange-Id: Icf9a4725526b4329a2841626977292802ad2fa7a","distinct":true,"url":"https://api.github.com/repos/w3c/web-platform-tests/commits/36d0a89072454a9bba0c452a26bcfacdb4aa4a5a"}]}
{"actor":{"display_login":"chromium-wpt-export-bot"}}