06f77f6 | Rune Lillesveen | 27 March 2018, 00:22:42 UTC | [css-typedom] Add support for the *-gap properties. Bug: 820299 Change-Id: I596113eeea7d4c13cf689364744bff7c261f93d3 Reviewed-on: https://chromium-review.googlesource.com/978247 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545896} | 27 March 2018, 00:31:06 UTC |
f497de8 | Robert Ma | 26 March 2018, 20:24:51 UTC | Better explain test execution in resources/test/README | 26 March 2018, 21:12:14 UTC |
7988e17 | Ian Kilpatrick | 26 March 2018, 18:44:58 UTC | [css-layout-api] Allow LayoutChild(ren) to be laid out. This allows a LayoutChild to have layout performed on it, which will return a Fragment - with the correct inline and block sizes. These Fragments cannot be positioned yet, (next patch). The LayoutChild will be laid out with an available inline/block size of zero by default, and optionally can accept a fixed-inline/block size, which it must respect. Bug: 726125 Change-Id: Ie4386b8f6cd6ccec3f9e52ff332322101058836d Reviewed-on: https://chromium-review.googlesource.com/962870 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#545845} | 26 March 2018, 19:34:57 UTC |
a35b824 | Boris Zbarsky | 26 March 2018, 18:16:29 UTC | part 3. Add testing for what mutation observers happen when doing DOMTokenList.replace. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1444909 gecko-commit: bb405d71ba671812bddc20aaa935f1a2bbe53499 gecko-integration-branch: central gecko-reviewers: qdot | 26 March 2018, 18:37:35 UTC |
5957997 | fantasai | 07 February 2018, 00:55:57 UTC | [css-sizing-3] Add tests for intrinsic size contribution (width/inline-size) of non-replaced blocks with percentage widths. See https://github.com/w3c/csswg-drafts/issues/1132 | 26 March 2018, 18:13:34 UTC |
a890989 | Hwanseung Lee | 26 March 2018, 15:54:44 UTC | [css-typed-om] support block-size and inline-size block-size[1], inline-size[2], max-block-size[3], max-inline-size[4], min-block-size[5], min-inline-size[6] are added to support in whitelist. and test file are also added. [1]https://drafts.csswg.org/css-logical-1/#propdef-block-size [2]https://drafts.csswg.org/css-logical-1/#propdef-inline-size [3]https://drafts.csswg.org/css-logical-1/#propdef-max-block-size [4]https://drafts.csswg.org/css-logical-1/#propdef-max-inline-size [5]https://drafts.csswg.org/css-logical-1/#propdef-min-block-size [6]https://drafts.csswg.org/css-logical-1/#propdef-min-inline-size Bug: 820299 Change-Id: I97c589deea28bfedc82ec1b1686ceaf9979cb95e Reviewed-on: https://chromium-review.googlesource.com/973561 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545802} | 26 March 2018, 16:03:03 UTC |
3b57b11 | Josh Matthews | 26 March 2018, 14:23:24 UTC | Add base protocol to ConnectionlessProtocol. | 26 March 2018, 14:47:13 UTC |
f4388a3 | Morten Stenshorne | 26 March 2018, 14:00:45 UTC | [css-flexbox] Resolve min-width:auto on table item to min preferred size. Edge and Firefox seem to let table flex items use the sizing algorithm of the table extensively, and are therefore generally broken when it comes to flexing tables. We, on the other hand, let the flex sizing algorithm be in charge of sizing tables, so that flexing actually works. However, this causes tables with a specified main size of less than the minimum intrinsic logical width of the table to shrink below their minimum intrinsic logical width, a situation that's generally unwanted for tables. Amend by ignoring the specified main size when resolving min-width:auto on table items. Also ignore max-width/max-height. Just use the preferred minimum logical width. Bug: 821832 Change-Id: I78ca0c8e0041ea69bb606ff72d340bb3f5f9bb96 Reviewed-on: https://chromium-review.googlesource.com/964203 Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#545777} | 26 March 2018, 14:10:13 UTC |
ff4fae1 | Chandan Padhi | 26 March 2018, 10:09:55 UTC | Add support for autoGainControl and noiseSuppression to getCapabilities() This CL adds support for autoGainControl and noiseSuppression properties to MediaStreamTrack.getCapabilities() and InputDeviceInfo.getCapabilities(). Bug: 823831, 817769 Change-Id: Ifdc0e560001e000b12c8d04634d3c52de0a34cc7 Reviewed-on: https://chromium-review.googlesource.com/977251 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Chandan Padhi <c.padhi@samsung.com> Cr-Commit-Position: refs/heads/master@{#545750} | 26 March 2018, 10:19:04 UTC |
e31f590 | Hiroki Nakagawa | 26 March 2018, 09:29:42 UTC | Worker: Allow dynamic import() on DedicatedWorkerGlobalScope This CL allows dynamic import() on DedicatedWorkerGlobalScope and adds WPT tests. Note that ES Modules on DedicatedWorker is an experimental feature behind the runtime flag. Design doc: https://docs.google.com/document/d/1IMGWAK7Wq37mLehwkbysNRBBnhQBo3z2MbYyMkViEnY/edit#heading=h.637avx8i5qtn Bug: 680046 Change-Id: I1f8fed5c319aab634f96bcfabeb3c95f5dc7d9a7 Reviewed-on: https://chromium-review.googlesource.com/970127 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#545748} | 26 March 2018, 09:37:45 UTC |
4ff4c66 | Darren Shen | 26 March 2018, 01:54:20 UTC | [css-typed-om] Support font properties. We try to support as many font properties as possible. However, several font properties have not been implemented in Blink yet. Also, the computed value for font-stretch is wrong (it should be as specified, and no rounding should occur). Spec: https://drafts.css-houdini.org/css-typed-om-1/#reify-stylevalue Bug: 820299 Change-Id: I744d03a08856bd6d0df6bd07230ec80138e6e3b7 Reviewed-on: https://chromium-review.googlesource.com/977247 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545721} | 26 March 2018, 02:10:55 UTC |
d04a8fc | Robert Ma | 23 March 2018, 22:18:18 UTC | Fix some IDL tests after html.idl includes SVGElement html.idl changed in upstream https://github.com/w3c/web-platform-tests/pull/10110 and imported in https://crrev.com/c/978021 Bug: 825191 Change-Id: Ie1a04e730aabd50c615f1dab079f92eeaa22565a Reviewed-on: https://chromium-review.googlesource.com/978508 Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#545588} | 23 March 2018, 22:37:33 UTC |
7991f4b | Ovidio Henriquez | 23 March 2018, 17:54:47 UTC | bluetooth: Impl. setNextWriteResponse (descriptor) Also implements getLastWrittenValue() and converts two tests to use these. FakeRemoteGattDescriptor::setNextWriteResponse allows tests to set the next response for a write. BUG=719825 Change-Id: I2807d23a55f79eeca35338e25916c6d5e0115e89 Reviewed-on: https://chromium-review.googlesource.com/964901 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Cr-Commit-Position: refs/heads/master@{#545508} | 23 March 2018, 18:32:09 UTC |
af184df | youennf | 23 March 2018, 17:40:23 UTC | Merge pull request #10151 from youennf/wpt-export-for-webkit-183928 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=183928 | 23 March 2018, 17:40:23 UTC |
273bb41 | Ovidio Henriquez | 23 March 2018, 15:12:10 UTC | bluetooth: Add RemoveFakeDescriptor to BT test This change allows the removal of a descriptor to be simulated by the Bluetooth test interface. A generated test script was also converted to test the new interface. BUG=569709 Change-Id: Id4286a3e44cd04ee1b371938f1ef89f33458269c Reviewed-on: https://chromium-review.googlesource.com/972334 Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#545448} | 23 March 2018, 15:30:21 UTC |
2d1fd9e | Rune Lillesveen | 23 March 2018, 14:59:20 UTC | Don't skip display:none options finding selectable options. This means we can also assume a null ComputedStyle on options means they are display:none. That is a pre-requisite for fixing issue 822581. Bug: 824754 Change-Id: Ia8a400ec8eed9ecb9a85d2c93c354841ad721492 Reviewed-on: https://chromium-review.googlesource.com/975604 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545443} | 23 March 2018, 15:12:06 UTC |
a1ec330 | Blink WPT Bot | 23 March 2018, 14:42:53 UTC | PaymentRequest: Use [SecureContext] instead of manual check (#8648) Until now, we had to use IsSecureContext() to check whether an execution context is a secure context manually. But we can use [SecureContext] instead of the manual check now. After this change, all related APIs including PaymentRequest will not be exposed in non-secure context. Bug: none Change-Id: Ie5b3fc6641e882cc2844595fea350b6adb3425db | 23 March 2018, 14:42:53 UTC |
4578f69 | Luke Bjerring | 23 March 2018, 13:37:57 UTC | idlharness.js: Distinguish instance toJSON is being executed against when it's inherited (#10029) * Distinguish which instance toJSON is being executed against when inherited | 23 March 2018, 13:37:57 UTC |
b705dc1 | Ahilya Sinha | 23 March 2018, 13:09:14 UTC | Fixed lint checking directories it shouldn't be (#10147) Lint earlier checked _venv/ and .git/ which it shouldn't be checking. | 23 March 2018, 13:09:14 UTC |
174f764 | jgraham | 23 March 2018, 12:27:05 UTC | Fix python gitignore for directories. (#10131) For top level directories like _venv/ we were creating the regexp ^\_venv/$, which we were then feeding paths like _venv/bin/foo which it fails to match. Since we are matching against full paths, we certainly want to allow matching _venv/* and probably also bare _venv, so add a special case for paths with a trailing slash to allow these options. | 23 March 2018, 12:27:05 UTC |
9e2e5eb | Sergio Villar Senin | 23 March 2018, 11:33:30 UTC | [css-grid] Fix auto repeat tracks computation with definite min sizes Indefinitely sized containers use the specified definite min-size (if any) as available space in order to compute the number of auto repeat tracks to create. A bug in that code was causing the grid to be one track larger than expected. That was only happening in the case of the free space being a multiple of the total size of the autorepeat tracks. Bug: 823140 Change-Id: I6cc13df478da4ba00585fa557012391291941d1a Reviewed-on: https://chromium-review.googlesource.com/973522 Commit-Queue: Sergio Villar <svillar@igalia.com> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#545403} | 23 March 2018, 11:41:52 UTC |
b04a923 | Michael[tm] Smith | 23 March 2018, 10:42:57 UTC | cc Update messages.json | 23 March 2018, 10:57:43 UTC |
20d739e | Anne van Kesteren | 20 March 2018, 14:55:59 UTC | Add HTMLOrSVGElement to HTML's IDL And align a couple other things while there. Helps with https://github.com/whatwg/html/pull/3543. | 23 March 2018, 10:24:48 UTC |
48d50c6 | Youenn Fablet | 23 March 2018, 05:15:23 UTC | WebKit export of https://bugs.webkit.org/show_bug.cgi?id=183928 | 23 March 2018, 05:15:23 UTC |
e40c752 | Marcos Cáceres | 23 March 2018, 03:37:07 UTC | Tests for PaymentItem.type member (#9099) | 23 March 2018, 03:37:07 UTC |
4e1bb51 | Xianzhu Wang | 22 March 2018, 20:37:21 UTC | [PE] Add ToInt() for logical padding top and bottom for LayoutTableCell This reverts the logic for logical top/bottom paddings to be the same as before https://chromium-review.googlesource.com/619603. The logical top/bottom paddings are truncated like what we do for other table layouts. We still keep subpixels for logical left/right paddings to ensure correct logical width calculation. This is still the same as before https://chromium-review.googlesource.com/619603. Bug: 823824 Change-Id: Icb617bf5771d1726f767207853f4adc8275731dc Reviewed-on: https://chromium-review.googlesource.com/974315 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#545225} | 22 March 2018, 20:49:19 UTC |
9dcebcb | Robert Ma | 22 March 2018, 19:02:06 UTC | Add .tox to global .gitignore | 22 March 2018, 20:18:25 UTC |
f94a28a | Robert Ma | 21 March 2018, 17:35:46 UTC | Fix resources/test (when running locally) 1. Check the HTTP port of wptserve instead of HTTPS to avoid the unnecessary complexities of setting up SSL context (which may fail in some environments). 2. Use exponential backoff when waiting for wptserve and specify a maximum retry to avoid indefinite hang. 3. Use `terminate` instead of `kill` to give wptserve a chance to clean up, which is especially useful when running locally. WPTServe.url still returns a HTTPS URL to make sure tests that require secure context (e.g. service workers) still work. | 22 March 2018, 20:18:25 UTC |
df2e803 | Luke Bjerring | 22 March 2018, 19:15:29 UTC | Handle options for add_untested_idls (#10100) | 22 March 2018, 19:15:29 UTC |
e48a42f | Harald Alvestrand | 22 March 2018, 18:59:43 UTC | Add memory of last SDP offer/answer created This adds internal slots "LastOffer" and "LastAnswer", and uses those to check that SetLocalDescription uses an unchanged SDP offer/answer. Because modification of SDP is suspected to be used in a number of places, this change only rejects SDP with modified fingerprints (which would fail anyway), but merely counts the usage for other modifications. Bug: chromium:823036 Change-Id: I0c978d5ff3e63b0afab3ec02334c57a5aaa94cdd Reviewed-on: https://chromium-review.googlesource.com/966441 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Tommi <tommi@chromium.org> Cr-Commit-Position: refs/heads/master@{#545175} | 22 March 2018, 19:10:10 UTC |
99914e1 | Hayato Ito | 22 March 2018, 09:56:30 UTC | Reject customized built-in elements in attachShadow Element::CanAttachShadowRoot() needs to be updated because it returns wrongly true for customized built-in elements. The spec: https://dom.spec.whatwg.org/#dom-element-attachshadow Bug: 823033 Change-Id: Ia9aeb47569414830f5435f37f85d96101b9fe432 Reviewed-on: https://chromium-review.googlesource.com/970142 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#545026} | 22 March 2018, 10:06:31 UTC |
74126cb | Frédéric Wang | 22 March 2018, 07:57:21 UTC | MathML: Test italic correction of sub and super scripts attached to a large operator (#9993) | 22 March 2018, 07:57:21 UTC |
5ffa505 | Joe Downing | 22 March 2018, 07:35:35 UTC | Move KeyboardLock API methods to a 'keyboard' object This change moves the KeyboardLock API methods to a 'keyboard' namespace on the Navigator object. We are doing this work now as there has been a request for additional keyboard functionality that would also be placed on the new keyboard object and we wanted to move the KeyboardLock methods there for consistency before we launch. KeyboardLock API Spec is here: https://w3c.github.io/keyboard-lock/#API Old calling pattern: Navigator.keyboardLock(); Navigator.keyboardUnlock(); New calling pattern: Navigator.keyboard.lock(); Navigator.keyboard.unlock(); Note: The main logic in the KeyboardLock.cpp class and tests is the same as it was, however the file changed enough that git does not recognize it as a file move. BUG=680809 Change-Id: I234b2ab12d5ecd44c894ed5103863fd96fd548d4 Reviewed-on: https://chromium-review.googlesource.com/969656 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Gary Kacmarcik <garykac@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#544996} | 22 March 2018, 07:45:48 UTC |
1a8c195 | Hiroki Nakagawa | 22 March 2018, 05:53:36 UTC | Worker: Support ES Modules on DedicatedWorker behind the runtime flag This CL supports ES Modules on DedicatedWorker behind the ModuleDedicatedWorker flag and adds WPT tests. With the flag, you can specify 'type' option on the constructor of DedicatedWorker (i.e., new Worker) to start a dedicated worker as a module script. On DedicatedWorkerGlobalScope, static import is available, but dynamic import() hasn't been implemented yet. Bug: 680046 Change-Id: I3aca350228ec07be7884c7a2eb8cd351e7fd6b6e Reviewed-on: https://chromium-review.googlesource.com/967908 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#544983} | 22 March 2018, 06:21:57 UTC |
14f1aec | Yoshifumi Inoue | 22 March 2018, 04:00:01 UTC | Make Range::intersectsNode() to follow the spec This patch change |Range::intersectsNode()| to follow the spec[1]. [1] https://dom.spec.whatwg.org/#dom-range-intersectsnode Bug: 822510 Change-Id: Ifd504443355da12482b759701cddd62e2a90d7a6 Reviewed-on: https://chromium-review.googlesource.com/970044 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#544971} | 22 March 2018, 04:10:17 UTC |
f5b48cf | Marcos Cáceres | 22 March 2018, 02:27:28 UTC | Prevent false positives (#10120) | 22 March 2018, 02:27:28 UTC |
405e0e9 | Rune Lillesveen | 22 March 2018, 01:57:52 UTC | [css-typed-om] Add support for column-span. Reify as an identifier. Bug: 820299 Change-Id: I483a1e3c126e5b280a2337772584070f96cd533e Reviewed-on: https://chromium-review.googlesource.com/970263 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#544939} | 22 March 2018, 02:08:04 UTC |
0529cde | Luke Bjerring | 22 March 2018, 01:33:12 UTC | Update web-animations IDL file (#9908) | 22 March 2018, 01:33:12 UTC |
26e8a76 | Nicolás Peña | 21 March 2018, 23:20:26 UTC | Move remaining Intel/resource-timing/ tests to WPT Bug: 498037 Change-Id: I8f0e72da2aac76e5ff8ac0b4ffffd8b228e0ac42 Reviewed-on: https://chromium-review.googlesource.com/970047 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#544895} | 21 March 2018, 23:40:53 UTC |
3c0e03d | Marijn Kruisselbrink | 21 March 2018, 22:30:54 UTC | [Blobs] Correctly set mimetype of blob in FetchDataLoader. Just creating a new BlobDataHandle doesn't actually update the mimetype of the blob (if later the blob is requested through a blob: URL for example), so instead actually create a new blob wrapping the existing blob to properly change the mimetype. Bug: none Change-Id: I93b6d584178a02a74d68bdd6fcace1514ca90ec0 Reviewed-on: https://chromium-review.googlesource.com/967271 Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#544864} | 21 March 2018, 22:40:16 UTC |
b1ef882 | Harald Alvestrand | 21 March 2018, 19:52:04 UTC | Test that DTMFSender rejects properly after close This verifies that the sender throws the right error when called after the connection closing. Bug: chromium:822799 Change-Id: Id3ab4ddc65b1510526fa49b7bfe3f9f95a7f2d65 Reviewed-on: https://chromium-review.googlesource.com/968927 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#544804} | 21 March 2018, 20:03:53 UTC |
c6ed739 | Sandra Sun | 21 March 2018, 19:01:15 UTC | Implement scroll-snap-type: proximity As specified in the spec, when the snap-container has scroll-snap-type: proximity, we should only consider snap positions that are close to the current scroll offset. https://drafts.csswg.org/css-scroll-snap-1/#snap-strictness Bug: 823820 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I6312f98df421e303eb538f422ede39cea8dd5d38 Reviewed-on: https://chromium-review.googlesource.com/971466 Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Reviewed-by: Ali Juma <ajuma@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#544783} | 21 March 2018, 19:12:40 UTC |
888f7df | Chris Harrelson | 21 March 2018, 17:47:30 UTC | Make <foreignObject> a stacking context. Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/DHSUFGpZafc Bug: 723076 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I09d422e0fa9888610cfb3a8acfcea6c9f8c8de24 Reviewed-on: https://chromium-review.googlesource.com/831397 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#544756} | 21 March 2018, 18:19:40 UTC |
dbb38a6 | Luke Bjerring | 21 March 2018, 15:20:29 UTC | Update storage idl file (#9833) | 21 March 2018, 15:20:29 UTC |
5edf4f2 | Luke Bjerring | 21 March 2018, 14:49:08 UTC | Update the webvtt IDL file (#9855) * Add webvtt idl file * Update webvtt/api/interfaces.html to use IDL | 21 March 2018, 14:49:08 UTC |
b873ed6 | Luke Bjerring | 21 March 2018, 14:02:28 UTC | Update the css-typed-om IDL file (#9775) * Update css-typed-om IDL * Re-introduce commenting of CSS namespace | 21 March 2018, 14:02:28 UTC |
ab293a5 | Luke Bjerring | 21 March 2018, 13:59:57 UTC | Update payment-request IDL file (#9797) | 21 March 2018, 13:59:57 UTC |
535e962 | Manuel Rego Casasnovas | 21 March 2018, 13:42:37 UTC | [css-grid] Fix testing-utils.js We have been calling testGridTemplateColumnsRows() with and without arrays. Arrays are needed because the serialization of 2 tracks of the same size can be "100px 100px" or "repeat(2, 100px)". But in the rest of the cases we don't need an array, so we call the method with a single value. testGridTemplateColumnsRows() was not ready to support that, and it wasn't actually checking anything in that case. The patch modifies testing-utils.js, so it wraps values in an array when required. Now testGridTemplateColumnsRows() will be actually checking things. Change-Id: I7e360677c391df74dedb474922bf5c04247141c5 Reviewed-on: https://chromium-review.googlesource.com/973063 Reviewed-by: Sergio Villar <svillar@igalia.com> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#544681} | 21 March 2018, 13:53:19 UTC |
47c9322 | Robert Ma | 21 March 2018, 13:45:02 UTC | Attempt to fix ci_resources_unittest (#10116) The test wasn't running against the downloaded Firefox Nightly but system Firefox instead, which is fixed by passing the binary path to tox (which then passes it to pytest conftest.py). The pip requirements should be managed by tox. | 21 March 2018, 13:45:02 UTC |
fc04bb5 | Anne van Kesteren | 21 March 2018, 08:38:11 UTC | Test postMessage() exception order For https://github.com/whatwg/html/pull/3508 and https://github.com/whatwg/html/pull/3557. | 21 March 2018, 08:38:11 UTC |
f8920ff | Marcos Cáceres | 21 March 2018, 03:46:47 UTC | Edge doesn't do object spread yet (#10119) | 21 March 2018, 03:46:47 UTC |
92885ac | Marcos Cáceres | 21 March 2018, 01:49:00 UTC | user activation must survive postMessage() to call show() (#10090) Check that we can call pr.show() in an iframe via postMessage(), which is triggered by user activation. | 21 March 2018, 01:49:00 UTC |
66e0742 | Wanming Lin | 21 March 2018, 01:29:05 UTC | Revert "rename generic-sensor directory as sensors" (#10068) | 21 March 2018, 01:29:05 UTC |
3a83284 | Robert Ma | 20 March 2018, 18:52:04 UTC | Address comments * Renaming `check_stability.run` breaks commands.json and naming conventions, so rename the other `run` in that module instead. * Only return errors for empty results when we know for sure tests are affected. | 20 March 2018, 20:32:14 UTC |
7e214e8 | Robert Ma | 19 March 2018, 15:34:37 UTC | Exit check_stability with an error when no tests run Similar to #10030 (which was for `wpt run`), this commit makes `wpt check-stability` return a non-zero exit code when no tests run. Also fix some code smells: * `run` was redefined by `do_delayed_imports` to a different function. Rename the other `run` method in this module to `setup_and_run`. * `retcode` was unnecessarily defined in the top scope. Remove it to avoid redefinition. * `global logger` and the call to `get_parser` were extraneous in `run` (now `setup_and_run`) and hence are removed. | 20 March 2018, 20:32:14 UTC |
4d10320 | Robert Ma | 16 March 2018, 21:17:56 UTC | No longer allow Chrome stability check to fail After #10064, Chrome jobs run successfully on Travis, so we can turn the stability check back on. Fixes #9932. | 20 March 2018, 19:02:42 UTC |
dacfb44 | Joshua Bell | 20 March 2018, 17:58:31 UTC | Indexed DB: Consolidate window/worker IDL tests into any.js Also, rely on HTML and DOM interfaces for dependencies rather than inline definitions for Event, EventTarget, etc. Change-Id: I58ac6515f8d2769aec6bbf1b90d9a4105639ad24 Reviewed-on: https://chromium-review.googlesource.com/965452 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#544429} | 20 March 2018, 18:25:58 UTC |
e04e71f | Kriti Singh | 20 March 2018, 17:57:36 UTC | Stop using wrappedJSObject in marionette executor (#10041) | 20 March 2018, 17:57:36 UTC |
6e1b5f4 | Mattias Buelens | 20 March 2018, 13:27:09 UTC | ReadableStream: Readable byte stream must call pull if needed after receiving new chunk (#10018) * Fix test that allows too much pulling * Test that byte stream pulls after enqueue | 20 March 2018, 13:27:09 UTC |
31c11a7 | Luke Bjerring | 20 March 2018, 13:10:20 UTC | Update the web-share IDL file (#9843) | 20 March 2018, 13:10:20 UTC |
f2ae764 | Adam Rice | 20 March 2018, 12:30:43 UTC | Correctly reject in-progress body methods with AbortError Prior to this change, response body methods such as response.body.arrayBuffer() would reject with a TypeError if the fetch was aborted. This change makes them correctly reject with an AbortError instead. This implements stage #3 of the "Body Cancellation" section of the design doc: https://docs.google.com/document/d/1OuoCG2uiijbAwbCw9jaS7tHEO0LBO_4gMNio1ox0qlY/edit#heading=h.fvc7d7q07oio Bug: 817687 Change-Id: Ifde322d9c22485a8ba9d14fd4ffca65c4fb4745a Reviewed-on: https://chromium-review.googlesource.com/954765 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#544335} | 20 March 2018, 12:38:49 UTC |
7cb5db5 | Emilio Cobos Álvarez | 20 March 2018, 02:29:00 UTC | Make Shadow DOM account for stylesheet applicableness correctly. Summary: Also, make stuff sound in presence of CSSOM and what not. The dirty: false thing is reverting an accidental change that landed in the de-XBL stuff, which was harmless, but now wouldn't let me assert stuff properly. Reviewers: xidorn Bug #: 1445682 Differential Revision: https://phabricator.services.mozilla.com/D748 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1445682 gecko-commit: f2149d69f47cd9e7a2d0b478c2c63cb020dbfda9 gecko-integration-branch: central gecko-reviewers: xidorn | 20 March 2018, 02:40:51 UTC |
bca58b0 | moz-wptsync-bot | 16 March 2018, 13:38:52 UTC | Port XHR to WorkerRef, bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1445883 gecko-commit: 0f81334efa0a008db8931a41eef2d26a77d0e800 gecko-integration-branch: mozilla-inbound gecko-reviewers: smaug | 20 March 2018, 02:29:46 UTC |
c51eaff | Eric Willigers | 20 March 2018, 02:13:15 UTC | Merge pull request #10099 from csnardi/patch-9 Update serialization of drop-shadow | 20 March 2018, 02:13:15 UTC |
234faac | Hwanseung Lee | 20 March 2018, 00:47:12 UTC | [css-typed-om] support pointer-events property pointer-events[1] are added to support in whitelist. there are some camelcase keywords in pointer-events. actually pre-defined keywords are interpreted ASCII case-insensitively[2]. so it was changed to accept camelcase keyword in tests. and test file are also added. [1]https://svgwg.org/svg2-draft/interact.html#PointerEventsProperty [2]https://drafts.csswg.org/css-values-4/#keywords Bug: 820299 Change-Id: Iccc0f88a69bbec68964ef55bcc5c471fea765ccf Reviewed-on: https://chromium-review.googlesource.com/968581 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Cr-Commit-Position: refs/heads/master@{#544232} | 20 March 2018, 01:39:03 UTC |
3ec34e5 | Joshua Bell | 19 March 2018, 22:26:22 UTC | Web Platform Tests: add /interfaces/webaudio.idl and corresponding test The Web Audio tests (in /webaudio) have idlharness test on an interface-by-interface basis, but the new hotness is to have the IDL fragments consolidated. This also allows dependent specs to include the master interface definitions. Bug: 679813,697123,785409,823431 Change-Id: I60bc8415627b8b3f43c13060e4bf65f47bc17c2b Reviewed-on: https://chromium-review.googlesource.com/965401 Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#544173} | 19 March 2018, 22:50:31 UTC |
49cbe8a | Chris Nardi | 19 March 2018, 18:15:09 UTC | Test both parsing orders | 19 March 2018, 18:15:09 UTC |
6a53acc | Chris Nardi | 19 March 2018, 18:03:21 UTC | Remove obsolete invalid parsing test for drop-shadow https://github.com/w3c/fxtf-drafts/issues/231 was resolved by allowing this grammar in the spec. | 19 March 2018, 18:03:21 UTC |
730eca9 | Chris Nardi | 19 March 2018, 17:57:13 UTC | Update serialization of drop-shadow After https://github.com/w3c/fxtf-drafts/issues/240, the serialization order of drop-shadow() was changed to be the color (if specified), then the length values. This matches the behavior of Firefox/Chrome/WebKit. Update the test to match this change to the spec. | 19 March 2018, 17:57:13 UTC |
2667757 | Sandra Sun | 19 March 2018, 16:31:26 UTC | scroll-snap-align should specify inline and block. Currently, we parse the two values in scroll-snap-align for x and y. However, according to the spec, https://drafts.csswg.org/css-scroll-snap-1/#scroll-snap-align, the two values specify the alignment in the inline axis and block axis. This patch renames the two values and handles the vertical writing mode for inline and block alignments. Bug: 821645 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I78acff0df4698b3f9c0f7443e61e3bad75379b14 Reviewed-on: https://chromium-review.googlesource.com/967890 Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Ali Juma <ajuma@chromium.org> Cr-Commit-Position: refs/heads/master@{#544055} | 19 March 2018, 16:41:36 UTC |
5bb0c83 | Geoffrey Sneddon | 19 March 2018, 16:29:24 UTC | Remove dependency on external server for background-attachment-004 (#10092) | 19 March 2018, 16:29:24 UTC |
69cee83 | Manuel Rego Casasnovas | 19 March 2018, 16:01:26 UTC | Fix sizing of orthogonal elements with percentage margins LayoutBox::FillAvailableMeasure() was not considering the case of orthogonal elements when computing the margins. The margins ended up being properly calculated but the size of the orthogonal elements was wrong, as they considered to have more or less space than the available one. The method is modified in order to use the containing block inline size in order to resolve the percentages: https://www.w3.org/TR/css-writing-modes-3/#dimension-mapping BUG=808758 TEST=external/wpt/css/css-writing-modes/sizing-orthogonal-percentage-margin-00*.html Change-Id: Ib8c81dcd14589b3fefe806de3f8f75c000b1cac9 Reviewed-on: https://chromium-review.googlesource.com/968522 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#544047} | 19 March 2018, 16:21:19 UTC |
f281dad | Geoffrey Sneddon | 19 March 2018, 15:19:55 UTC | Rename host -> browser_host and host_ip -> server_host | 19 March 2018, 16:03:31 UTC |
be69acd | Geoffrey Sneddon | 16 March 2018, 16:55:00 UTC | Get rid of hardcoded web-platform.test in wpt/run.py | 19 March 2018, 16:03:31 UTC |
785ef2f | Geoffrey Sneddon | 16 March 2018, 16:45:04 UTC | Get rid of redundant host/certificate_domain definitions | 19 March 2018, 16:03:31 UTC |
66076b4 | Geoffrey Sneddon | 16 March 2018, 16:44:36 UTC | Make host_ip always exist in the normalised config | 19 March 2018, 16:03:31 UTC |
5dee619 | Robert Ma | 19 March 2018, 15:55:31 UTC | Fix a typo in a resource file name (#9986) (#10077) | 19 March 2018, 15:55:31 UTC |
919015d | xlai | 19 March 2018, 15:32:35 UTC | Improve wpt testing on OffscreenCanvas convertToBlob Same as canvas.toBlob(), the OffscreenCanvas.convertToBlob() are running on idle tasks by default. When idle tasks do not begin for a long time, they force encoding on the current thread. As idle tasks are not enabled on layout tests unless "--enable-threaded-compositing" flag is turned on, we therefore do both virtual and non-virtual tests to ensure complete test coverage of both execution paths--idle-task mode and force-encoding mode. The non-virtual tests need to be marked as [Slow] as the CanvasAsyncBlobCreator is waiting for the idle tasks for a threshold time before switching to force-encoding mode. Bug: 817091 Change-Id: I2c7da9e27ee2d24e1a5e6ee1c36597b46f052aca Reviewed-on: https://chromium-review.googlesource.com/964395 Reviewed-by: Justin Novosad <junov@chromium.org> Commit-Queue: Olivia Lai <xlai@chromium.org> Cr-Commit-Position: refs/heads/master@{#544036} | 19 March 2018, 15:42:31 UTC |
9b3bb05 | Mariana Meireles | 19 March 2018, 14:52:27 UTC | Allow passing stability options through command line (Fixes #9877) (#9945) repeat_loop = --verify-repeat-loop repeat_restart = --verify-repeat-restart (disable) chaos_mode = --verify-no-chaos-mode max_time = --verify-max-time (disable) output_results = --verify-no-output-results | 19 March 2018, 14:52:27 UTC |
c37c863 | Kent Tamura | 19 March 2018, 07:03:33 UTC | custom-elements: Simplify builtin-coverage.html Produce classes for custom elements by eval() and string concatenation. Change-Id: I834a3eb8abbcc4bc36646d63215b86f415ec8da9 Reviewed-on: https://chromium-review.googlesource.com/968001 Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#543983} | 19 March 2018, 07:22:26 UTC |
918f968 | Darren Shen | 19 March 2018, 06:54:15 UTC | [css-typed-om] Add support for min/max-width/height. Add support & tests for (min/max)-(width/height). Note that the typed om spec specifies the old specs for these properties: https://drafts.csswg.org/css21/visudet.html Bug: 820299 Change-Id: I9c65f7f24d84b83ea2e2f167f8fb86be967eff06 Reviewed-on: https://chromium-review.googlesource.com/968003 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#543980} | 19 March 2018, 07:03:29 UTC |
7a976a5 | moz-wptsync-bot | 16 March 2018, 11:12:05 UTC | WPT should use toString() and not toSource(), bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1446285 gecko-commit: fb42e9c14d4ea418b876787791e9aabdd082855c gecko-integration-branch: mozilla-inbound gecko-reviewers: smaug | 19 March 2018, 06:22:58 UTC |
e676f7b | moz-wptsync-bot | 16 March 2018, 17:19:41 UTC | Flush the document, not the shell, in cross-doc getComputedStyle situations. We flushed the style of the original doc, but not layout, and thus the iframe resize wasn't noticed, and the style flush on the child presShell wasn't sufficient. Do a style flush on the child document instead, so that it flushes layout on the parent document too if needed. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1443492 gecko-commit: 9cbafe1855ccac5fd2f0c2e549e830a66a72f84f gecko-integration-branch: mozilla-inbound gecko-reviewers: dbaron | 19 March 2018, 06:21:57 UTC |
1f80be4 | Darren Shen | 19 March 2018, 05:47:13 UTC | [css-typed-om] Add support for motion path properties. This patch adds support for motion path properties. We had to modify the computed style computation for <position> values. Previously, we parse a <position> value as a CSSValuePair, but compute them to a CSSValueList containing two items. This is very strange, so we just compute to a CSSValuePair. Since both serialize to the same string, this has no behavioural changes on CSSOM. Bug: 820299 Change-Id: I2131055dad0785eb47ea2d2d89f00229f4376bae Reviewed-on: https://chromium-review.googlesource.com/967915 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#543975} | 19 March 2018, 05:56:19 UTC |
10c525d | Hwanseung Lee | 19 March 2018, 01:17:13 UTC | [css-typed-om] support some properties -2- mix-blend-mode[1], object-fit[2], table-layout[3], text-orientation[4] are added to support in whitelist. and test file are also added. [1]https://drafts.fxtf.org/compositing-2/#propdef-mix-blend-mode [2]https://drafts.csswg.org/css-images-4/#propdef-object-fit [3]https://drafts.csswg.org/css-tables-3/#propdef-table-layout [4]https://drafts.csswg.org/css-writing-modes-4/#propdef-text-orientation Bug: 820299 Change-Id: I25a15000053a63e9aa776801e5676bf1adf5e9c5 Reviewed-on: https://chromium-review.googlesource.com/967902 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Cr-Commit-Position: refs/heads/master@{#543960} | 19 March 2018, 01:24:48 UTC |
790e660 | Darren Shen | 19 March 2018, 00:26:33 UTC | [css-typed-om] Clean up CSSUnitValue tests. This patch: - Adds mutation tests for CSSUnitValue.value. - Clean up code style. Bug: 774887 Change-Id: I5a6398c4a4a2ad86f60165780ee8d48bb3d8b0a1 Reviewed-on: https://chromium-review.googlesource.com/954642 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#543959} | 19 March 2018, 00:36:58 UTC |
e87f380 | Harris Hancock | 17 March 2018, 06:00:58 UTC | Fetch: add used body replacement test for Request constructor See Fetch change https://github.com/whatwg/fetch/pull/675. Specifically, that PR allows Requests with disturbed bodies to be used as the first parameter to the Request constructor, as long as the RequestInit dictionary contains a body member with which to replace the used body. As of this writing, no browser implements this change. | 17 March 2018, 06:00:58 UTC |
ecd2c46 | Ovidio Henriquez | 15 March 2018, 20:28:05 UTC | bluetooth: FakeBluetoothChooser stub impl. This change adds a new FakeBluetoothChooser interface stub to expand on. The design for this class is detailed in the following document: https://docs.google.com/document/d/1XFl_4ZAgO8ddM6U53A9AfUuZeWgJnlYD5wtbXqEpzeg BUG=719827 Change-Id: I34169ce62dd5b35796639b7643d899b8315cc4c7 Reviewed-on: https://chromium-review.googlesource.com/909726 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#543479} | 17 March 2018, 02:11:13 UTC |
53ea2c3 | Ian Kilpatrick | 16 March 2018, 20:51:08 UTC | [shapes] Remove shape-outside avoiding behaviour for new-FCs/replaced. See intent: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/pfDg-VAeKWs This makes new formatting contexts behave exactly like floats would when they are positioned. I.e. they don't look at the shape-outside of the float, and instead as positioned for their margin box. I've added a .tentative test as per the intent. This will allow us to have a (relatively) simple implementation of css-shapes in LayoutNG as we only have to consider the shape area for line-boxes. \o/ Bug: 820520 Change-Id: Ib07600a291eb4838675a9a1068c5fc16cac0633f Reviewed-on: https://chromium-review.googlesource.com/739961 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#543813} | 16 March 2018, 21:00:29 UTC |
ed51dbb | Robert Ma | 16 March 2018, 17:56:06 UTC | Mute wget when downloading chrome deb | 16 March 2018, 20:36:35 UTC |
c929502 | teh-f00l | 16 March 2018, 18:22:50 UTC | Make lint work when directories are passed in (#9995) Allow passing command line arguments to lint specifying directories they want checked. | 16 March 2018, 18:22:50 UTC |
bb066ef | Robert Ma | 16 March 2018, 16:18:07 UTC | Try to fix a WebDriver error | 16 March 2018, 17:02:47 UTC |
654dc43 | Robert Ma | 16 March 2018, 00:32:55 UTC | Pass the binary path of Chrome to wpt run in CI ChromeDriver doesn't honor PATH and uses /opt/google/chrome/chrome by default (which is usually the stable channel), so we need to explicitly pass the desired binary path to wpt run (which in turn passes to chromedriver via capabilities) in Travis CI (both stability check and infrastructure test). | 16 March 2018, 17:02:47 UTC |
89ba944 | jimevans | 16 March 2018, 14:46:32 UTC | webdriver: fix test_parent_htmldocument to expect error and test invalid relative xpath (#10058) When the context element is `document.documentElement`, and an attempt is made to find elements from that context element using an XPath of `..`, a snapshot is returned containing the `document` object. While this is apparently the correct behavior for XPath, the WebDriver spec says that if the object in the snapshot is not an element, we should return an error with error code "invalid selector." The test_parent_htmldocument test in both find_element_from_element.py and find_elements_from_element.py expect a success in this case. This commit changes the tests to correctly expect an error from the driver. | 16 March 2018, 14:46:32 UTC |
1cbb928 | Tomoyuki Shimizu | 16 March 2018, 12:46:37 UTC | [presentation-api] check if a URL with an unsupported scheme is ignored (#9966) Completes `PresentationRequest` constructor test with change [latest change made in Presentation API](https://github.com/w3c/presentation-api/pull/447). The following tests are added: - To check if an instance of `PresentationRequest` with URLs including one with an unsupported scheme is successfully constructed - To check if `NotSupportedError` is thrown when only single or multiple URLs with unsupported schemes are specified | 16 March 2018, 12:46:37 UTC |
5033883 | Geoffrey Sneddon | 16 March 2018, 12:09:06 UTC | Add test for what ".." on documentElement returns (#10055) | 16 March 2018, 12:09:06 UTC |
74b0e6c | Chandan Padhi | 16 March 2018, 11:33:40 UTC | Implement InputDeviceInfo.getCapabilities() for video devices Bug: 817769 Change-Id: I3f06b5f2360c570ff8c5b4bd800ca1014cc7d088 Reviewed-on: https://chromium-review.googlesource.com/956383 Commit-Queue: Chandan Padhi <c.padhi@samsung.com> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Raymes Khoury <raymes@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#543664} | 16 March 2018, 11:42:41 UTC |
8f61f07 | moz-wptsync-bot | 15 March 2018, 23:08:40 UTC | Port EventSource in Web Workers to WorkerRef, bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1445740 gecko-commit: 83cf165404102d1d22070a2e22fe99ab2ea28b8f gecko-integration-branch: mozilla-inbound gecko-reviewers: smaug | 16 March 2018, 11:13:24 UTC |
14b8462 | moz-wptsync-bot | 13 March 2018, 19:14:33 UTC | Fix a bunch of typo in the doc bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1444628 gecko-commit: 220a09bc56cde59c0f1764fab4e8fb6814caa39f gecko-integration-branch: central gecko-reviewers: ahal | 16 March 2018, 11:12:37 UTC |
2fdd035 | Brian Burg | 16 March 2018, 04:56:07 UTC | WebDriver: REGRESSION(86d68c3198c): missing 'sys' import in fixtures.py This adds extra [Error] results whenever there's a problem during teardown. I can't debug the actual failure if the test runner itself raises an exception. | 16 March 2018, 10:00:32 UTC |