Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
sort by:
Revision Author Date Message Commit Date
3bacf41 Sriram 23 January 2018, 13:38:05 UTC Upstream track-cue-rendering-horizontal.html Bug: 782555 Change-Id: I5c09a86b8290aee9288596055388976af3aa5818 23 January 2018, 13:38:05 UTC
9c8964b Bhagirathi Satpathy 23 January 2018, 12:17:09 UTC MessageEvent initMessageEvent should throw error in case of no argument MessageEvent initMessageEvent method should throw NotEnoughArguments error in case of no argument. Bug: Change-Id: I522f120456db3e30b4aa2f83144871fbe58e27fc Reviewed-on: https://chromium-review.googlesource.com/880263 Commit-Queue: Bhagirathi Satpathy <bhagirathi.s@samsung.com> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#531209} 23 January 2018, 12:26:38 UTC
14017b1 Wanming Lin 23 January 2018, 08:28:59 UTC Merge pull request #9131 from kaixinjxq/proximity_common Add Proximity Sensor tests and delete outdated tests 23 January 2018, 08:28:59 UTC
59e8791 Takashi Sakamoto 23 January 2018, 08:14:05 UTC Revert "Fix retargeting of result in elementFromPoint and elementsFromPoint" This reverts commit dd944882a245a5117b50cb417138d92f32d931d6. Reason for revert: This causes WebKit Linux Trusty ASAN buildbot failure. https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20ASAN/builds/8618 23:46:29.565 3877 ==1==ERROR: AddressSanitizer: use-after-poison on address 0x7ead60c0dbf0 at pc 0x00000dca937a bp 0x7ffd86b90c10 sp 0x7ffd86b90c08 23:46:29.565 3877 READ of size 8 at 0x7ead60c0dbf0 thread T0 (content_shell) 23:46:29.565 3877 #0 0xdca9379 in operator==<const blink::TreeScope, const blink::TreeScope> third_party/WebKit/Source/platform/heap/Member.h:128:27 23:46:29.565 3877 #1 0xdca9379 in blink::TreeScope::Retarget(blink::Element const&) const third_party/WebKit/Source/core/dom/TreeScope.cpp:393:0 23:46:29.565 3877 #2 0xdca8894 in blink::TreeScope::HitTestPointInternal(blink::Node*) const third_party/WebKit/Source/core/dom/TreeScope.cpp:267:10 23:46:29.565 3877 #3 0xdca8325 in HitTestPoint third_party/WebKit/Source/core/dom/TreeScope.cpp:254:10 23:46:29.566 3877 #4 0xdca8325 in blink::TreeScope::ElementFromPoint(double, double) const third_party/WebKit/Source/core/dom/TreeScope.cpp:245:0 23:46:29.566 3877 #5 0xc9353a7 in elementFromPoint third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h:38:23 Original change's description: > Fix retargeting of result in elementFromPoint and elementsFromPoint > > Currently elementFromPoint and elementsFromPoint are not per spec, and it may > return null incorrectly. This change adds retargeting of the result with > respect to the context object, and adds some tests that are similar to > elementFromPoint tests in WebKit, but with some corrected cases: > https://git.webkit.org/?p=WebKit-https.git;a=blob;f=LayoutTests/fast/shadow-dom/DocumentOrShadowRoot-prototype-elementFromPoint.html;h=a8dc4da2430713521b9ba77c742db10397a8e638;hb=HEAD > > Spec: > https://w3c.github.io/webcomponents/spec/shadow/#extensions-to-the-documentorshadowroot-mixin > > Bug: 759947 > Change-Id: I6aece5e9cc826124772c6ce13c806865055b2b9b > Reviewed-on: https://chromium-review.googlesource.com/808446 > Commit-Queue: Rakina Zata Amni <rakina@chromium.org> > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > Reviewed-by: Hayato Ito <hayato@chromium.org> > Reviewed-by: Takayoshi Kochi <kochi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#531139} TBR=kochi@chromium.org,dgozman@chromium.org,hayato@chromium.org,pfeldman@chromium.org,rakina@chromium.org Change-Id: Id62abd371d93627d3178b63ca189cecfe9ff44d4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 759947 Reviewed-on: https://chromium-review.googlesource.com/880264 Reviewed-by: Takashi Sakamoto <tasak@google.com> Commit-Queue: Takashi Sakamoto <tasak@google.com> Cr-Commit-Position: refs/heads/master@{#531178} 23 January 2018, 08:24:07 UTC
6356b9e kaixinjxq 23 January 2018, 05:50:43 UTC Add Proximity Sensor tests and delete outdated tests 23 January 2018, 05:57:36 UTC
34a8c8a Ovidio Henriquez 19 January 2018, 19:43:00 UTC Add RemoveFakeService to BT test interface This change allows the removal of a service to be simulated by the Bluetooth test interface. To test the new function the script for generating service is removed tests is also updated to make use of the new function. BUG=569709 Change-Id: Ibb1c1dcfe3e7928c6628402d4a434847faf69e4e Reviewed-on: https://chromium-review.googlesource.com/825946 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Cr-Commit-Position: refs/heads/master@{#530582} 23 January 2018, 04:42:36 UTC
eb574c6 Charles Vazac 19 January 2018, 22:04:21 UTC Fix ServerTiming results for resources that fail TAO check Per spec (https://w3c.github.io/server-timing/#processing-model), resources that fail the TAO check should return an empty array for the serverTiming attribute. Bug: 802321 Change-Id: I0bca0f38f0a975f7c85f4d8837a901bd8475d9b7 Reviewed-on: https://chromium-review.googlesource.com/870990 Commit-Queue: Yoav Weiss <yoav@yoav.ws> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Cr-Commit-Position: refs/heads/master@{#530622} 23 January 2018, 04:32:10 UTC
8f6cb93 Ian Clelland 19 January 2018, 16:25:10 UTC Catch unexpected exceptions in sync-xhr test. With this change, only the expected NetworkError from send() will be propagated to the feature policy test framework. Other errors (including NetworkErrors from other calls) will be prefixed with "UnexpectedException:" and will cause the tests to fail. Bug: 661283 Change-Id: I75e2fa6526211cc87c65f5f03e926903ae1ba22e Reviewed-on: https://chromium-review.googlesource.com/874270 Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#530527} 23 January 2018, 04:23:58 UTC
a19b359 Darren Shen 20 January 2018, 06:55:38 UTC [css-typed-om] Update paint style map behaviour for invalid properties. Custom paint callbacks receive a computed style map (implemented as FilteredComputedStylePropertyMap) that contain only properties specified in inputProperties(). For forwards-compatiblity, inputProperties() is allowed to have "invalid" or shorthand properties, which are not allowed to be in the styleMap. As resolved in [1], the style map should ignore any invalid/shorthand properties. Furthermore, if a custom property is specified in inputProperties(), it should have a default value of CSSUnparsedValue() (not "null"). These changes also require changes in custom paint tests. Namely: - Can no longer get "border-radius" from the style map. Have to use a longhand property like "border-left-radius". - Getting custom properties like "--bar" will have a default value of CSSUnparsedValue. [1] https://github.com/w3c/css-houdini-drafts/issues/523 Bug: 803690 Change-Id: I148b52568de698f69ee0bf594a2b92a9751ea484 Reviewed-on: https://chromium-review.googlesource.com/874984 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Xida Chen <xidachen@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#530763} 23 January 2018, 04:13:44 UTC
2ea087e Rakina Zata Amni 23 January 2018, 03:40:31 UTC Fix retargeting of result in elementFromPoint and elementsFromPoint Currently elementFromPoint and elementsFromPoint are not per spec, and it may return null incorrectly. This change adds retargeting of the result with respect to the context object, and adds some tests that are similar to elementFromPoint tests in WebKit, but with some corrected cases: https://git.webkit.org/?p=WebKit-https.git;a=blob;f=LayoutTests/fast/shadow-dom/DocumentOrShadowRoot-prototype-elementFromPoint.html;h=a8dc4da2430713521b9ba77c742db10397a8e638;hb=HEAD Spec: https://w3c.github.io/webcomponents/spec/shadow/#extensions-to-the-documentorshadowroot-mixin Bug: 759947 Change-Id: I6aece5e9cc826124772c6ce13c806865055b2b9b Reviewed-on: https://chromium-review.googlesource.com/808446 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Cr-Commit-Position: refs/heads/master@{#531139} 23 January 2018, 03:51:32 UTC
a24f9d2 Darren Shen 23 January 2018, 02:29:15 UTC [css-typed-om] Clean up StylePropertyMap.get tests. This patch does the following to clean up the StylePropertyMap.get tests for WPT: - We split happy cases and sad cases into separate files. - We removed the .tentative extension. - Added additional tests for style map liveness. Bug: 774887 Change-Id: I4143b6358f0d2b11fbb34be03696d5eea00bd0fa Reviewed-on: https://chromium-review.googlesource.com/878104 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#531129} 23 January 2018, 03:29:30 UTC
2fc60fe Chris Cunningham 23 January 2018, 01:41:22 UTC De-dup two mediasource layout tests. Affected tests: http/tests/media/media-source/mediasource-addsourcebuffer.html http/tests/media/media-source/mediasource-is-type-supported.html The above were deleted after reconciling with their upstream WPT versions. Reconciling generally just adds new test conditions without removing any from the upstream version. The exception being the QuoteExceeded source buffer tests, where I've replicated the replacement of the original test with 2 new tests from the blink version. Change-Id: I2d3d483cf38e77eed3f26b5aab7fea0991a66723 Reviewed-on: https://chromium-review.googlesource.com/875161 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#531106} 23 January 2018, 02:29:11 UTC
3757743 Ovidio Henriquez 23 January 2018, 00:50:58 UTC bluetooth: Migrate canonicalize filter tests This change migrates the requestDevice/canonicalizeFilter tests to wpt/. BUG=509038 Change-Id: Idc05c345d12d83f0df1e88774defee70ac5a2eaf Reviewed-on: https://chromium-review.googlesource.com/837729 Reviewed-by: Conley Owens <cco3@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#531085} 23 January 2018, 02:05:53 UTC
a4f05cb Javier Fernandez 23 January 2018, 00:38:36 UTC [css-align] The 'left' and 'right' values must be invalid in block axis The CSS WG resolved to remove the 'left' and 'right' values from the block/cross axis alignment properties. https://github.com/w3c/csswg-drafts/issues/1403 This CL changes the CSS parsing logic of all the CSS Box Alignment properties, both block-axis (align-{self, items, content} and inline-axis (justify-{self, items, content}). Additionally, the alignment shorthands (place-{self, items, content}) have been also changed to respect the new syntax. This change also affects the Grid Layout alignment logic. Bug: 802095 Change-Id: Id848ce22a9b2d69ecf2bfd58503f590e4b2fe4db Reviewed-on: https://chromium-review.googlesource.com/877519 Reviewed-by: meade_(do not use) <meade@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#531074} 23 January 2018, 01:53:58 UTC
ca5f14e Mikhail Pozdnyakov 22 January 2018, 21:30:23 UTC [Sensors]Provide error codes from SensorProvider Return error codes from the SensorProvider.GetSensor() method. In future it will be used to return correct errors in Generic Sensor API (e.g. 'NotAllowedError' if permissions are denied). Bug: 796894 Change-Id: I613c6f3792fde3c05142f1b4cf809655b4acb15f Reviewed-on: https://chromium-review.googlesource.com/864325 Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Alexander Shalamov <alexander.shalamov@intel.com> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Mikhail Pozdnyakov <mikhail.pozdnyakov@intel.com> Cr-Commit-Position: refs/heads/master@{#530997} 22 January 2018, 21:49:36 UTC
289fa0d Chris Lilley 22 January 2018, 18:22:02 UTC original test from https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=5188 22 January 2018, 18:22:02 UTC
ce7b5aa Chris Lilley 22 January 2018, 18:14:45 UTC original test from https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=5188 22 January 2018, 18:14:45 UTC
8d6c628 Philip Jägenstedt 22 January 2018, 15:05:21 UTC Move test for navigator.deviceMemory to its own dir with OWNERS Directory name matching https://w3c.github.io/device-memory/. Change-Id: If32f07b659aca91a63fd17ca80de4afb1cd525c2 Reviewed-on: https://chromium-review.googlesource.com/876423 Reviewed-by: Fadi Meawad <fmeawad@chromium.org> Reviewed-by: Shubhie Panicker <panicker@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#530859} 22 January 2018, 15:24:12 UTC
a9c9f5f Carlos Garcia Campos 22 January 2018, 13:49:02 UTC webdriver: response.py::test_pageLoadStrategy is using wrong capabilities Browser options should be included in alwaysMatch. 22 January 2018, 14:00:50 UTC
ec2a84a L. David Baron 21 January 2018, 17:26:21 UTC Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/9fe69ff0762da191fbd2b9fc0718e96f1ab4137e . 22 January 2018, 11:07:41 UTC
5eaa47b Manuel Rego Casasnovas 19 January 2018, 12:46:34 UTC [css-grid] Fix for flexible tracks, gutters and spanning items In IndefiniteSizeStrategy::FindUsedFlexFraction() we were not subtracting the size of the gutters when we call FindFrUnitSize(). If an item spans several tracks, we cannot pass the MaxContentForChild() directly, we need to subtract the gutters as they are treated as fixed size tracks in the algorithm. The spec text is pretty clear regarding this (https://drafts.csswg.org/css-grid/#algo-find-fr-size): "Let leftover space be the space to fill minus the base sizes of the non-flexible grid tracks." Gutters are treated as fixed-size tracks for the purpose of the track sizing algorithm, so we need to subtract them from the leftover space while finding the size of an "fr". BUG=802021 TEST=external/wpt/css/css-grid/layout-algorithm/grid-find-fr-size-gutters-001.html Change-Id: If066852826a0ba0072a9fd996f11c0d653610b97 Reviewed-on: https://chromium-review.googlesource.com/868659 Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Reviewed-by: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Sergio Villar <svillar@igalia.com> Cr-Commit-Position: refs/heads/master@{#530491} 22 January 2018, 10:09:43 UTC
6aa9181 Darren Shen 22 January 2018, 04:06:11 UTC [css-typed-om] Throw exception if serializing unsupported CSSMathValues Currently, there are some CSSMathValues that can't be serialized because we have not implemented the calc lv4 spec [1]. This patch makes toString throw an exception if we try to serialize to a calc value that is not yet valid in Blink. We fix the web platform test to match the lv4 spec, but we still leave the test as .tentative as the spec is still a draft. [1] https://drafts.csswg.org/css-values-4/#calc-notation Bug: 803739 Change-Id: I12253dbfcd58f0f0d8def26368e93e873ddc8323 Reviewed-on: https://chromium-review.googlesource.com/877200 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#530804} 22 January 2018, 04:14:30 UTC
7a4c0d6 Wanming Lin 22 January 2018, 04:03:31 UTC Merge pull request #9118 from Honry/screenorien-idl Use IDL harness tests for Screen Orientation API 22 January 2018, 04:03:31 UTC
99266a9 Wanming Lin 23 January 2018, 02:30:03 UTC Use IDL harness tests for Screen Orientation API 23 January 2018, 02:34:24 UTC
bc7544a J.C. Jones 21 January 2018, 22:14:25 UTC Add @jcjones to the webauthn test owners (#9097) 21 January 2018, 22:14:25 UTC
31f021a Marcos Cáceres 19 January 2018, 21:02:59 UTC Add PaymentRequest.id must be UUID tests 19 January 2018, 21:02:59 UTC
c35e3d1 Tomoyuki Shimizu 19 January 2018, 16:45:38 UTC [presentation-api] Stop using EventWatcher for IndexedDB (#9046) * stop using EventWatcher for IndexedDB, similar to what was done in #5334. * simplify checking IndexedDB without creating an object store 19 January 2018, 16:45:38 UTC
cd052aa Rune Lillesveen 19 January 2018, 10:27:36 UTC Use new ComputedStyle instance for kNoChange. Even if the computed style doesn't change, AffectedBy* flags may have changed, which means we need to set the current ComputedStyle to the new instance. We can however skip any invalidation diffs. This is a re-land of the revert of this functionality which did not make us recover from the memory regression reported in 771294. Bug: 768406, 771294 Change-Id: Icc7eeee8a982eed53243d52d04d45e313d79a10d Reviewed-on: https://chromium-review.googlesource.com/870391 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#530468} 19 January 2018, 10:38:52 UTC
fd582f3 Sriram 19 January 2018, 09:36:30 UTC Upstream track-webvtt-non-snap* and track-webvtt-two-cue-layout* tests Upstream the below tests from media/track/ to wpt 1. track-webvtt-non-snap-to-lines.html 2. track-webvtt-two-cue-layout-after-first-end.html Bug: 782555 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ie3a0e7c7662821d605b9beddd0dd0e6ed3e10870 Reviewed-on: https://chromium-review.googlesource.com/875571 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: srirama chandra sekhar <srirama.m@samsung.com> Cr-Commit-Position: refs/heads/master@{#530458} 19 January 2018, 09:46:29 UTC
be1298d Bhagirathi Satpathy 19 January 2018, 08:48:47 UTC HTMLLinkElement relList attribute should be [SameObject] This patch contains 1. HTMLLinkElement relList attribute should be [SameObject]. https://html.spec.whatwg.org/multipage/semantics.html#the-link-element 2. Unified a, area and link element relList attribute test. Bug: Change-Id: Iec5b2b2d2bc35502e173128194060fd30a9f3fac Reviewed-on: https://chromium-review.googlesource.com/867800 Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Bhagirathi Satpathy <bhagirathi.s@samsung.com> Cr-Commit-Position: refs/heads/master@{#530451} 19 January 2018, 08:58:11 UTC
b834fde Xida Chen 19 January 2018, 06:59:58 UTC [PaintWorklet] Do null check for document paint definition In quite a few functions in the CSSPaintImageGeneratorImpl class, we check whether the document paint definition of a particular name exists or not, but we never do null check on that definition. This could lead to crash if the document paint definition is a null ptr. This CL fixes the problem by doing null check. It also changes one layout test to execise this code path. The change to the layout test also fixes the problem that this layout test passes in the browser that doesn't support paint worklet. Bug: 802970, 768683 Change-Id: Ia952ad977b63af643410b0973cc8034fac504f9f Reviewed-on: https://chromium-review.googlesource.com/869891 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#530441} 19 January 2018, 07:09:39 UTC
a0c2adf Gyuyoung Kim 19 January 2018, 05:03:12 UTC Reland "[USVString] Change the type of url with USVString in navigator.sendBeacon" This is a reland of I66825c20395ea6fd6b26e32fc8f6508fd85aeef7. Original CL caused a memory leak for the layout test. This CL fixes it speculatively. Bug: 790860 Change-Id: I0daac689085625b4954bac34991e28addea6f8e1 Reviewed-on: https://chromium-review.googlesource.com/874977 Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Cr-Commit-Position: refs/heads/master@{#530424} 19 January 2018, 05:13:49 UTC
29f6596 Javier Fernandez 19 January 2018, 03:31:22 UTC [css-align] overflow-position keyword must have a fixed position There were several discussions to avoid ambiguities with the complex values, specially when it comes to define the place-xxx shorthands. One of the sources of problems is the 'overflow-position' keyword. The CSS WG has decided to change the syntax of all the CSS Box Alignment properties so that the 'overflow-position' keyword always precede the 'self-position' or the 'content-position' keywords. https://github.com/w3c/csswg-drafts/issues/1446#event-1125715434 In order to apply this change to the Content Distribution properties' (align-content and justify-content) syntax I had to completely re-implement their parsing function. Thanks to this I addressed also the issue with the content-distribution fallback, which cannot be specified explicitly now. https://github.com/w3c/csswg-drafts/issues/1002#ref-commit-c38cac4 Bug: 802098, 802247 Change-Id: I57315a475940c00d0c0dafbb4f1b32a2c6c1ff68 Reviewed-on: https://chromium-review.googlesource.com/868531 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: meade_UTC10 <meade@chromium.org> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#530416} 19 January 2018, 04:08:14 UTC
2edfb50 Hayato Ito 19 January 2018, 02:17:11 UTC Don't dispatch events when target is shadow-including ancestor of relatedTarget See the discussion at https://github.com/whatwg/dom/pull/336 for details. Blink implemented it at https://codereview.chromium.org/2384403002, however, it turned out that both the web platform test and the implementation were wrong. This CL fixed the implementation, as well as the web platform test. Compatibility risk is almost none about this change. Bug: 655494 Change-Id: I084cd6b748c304f5f2b395f0b62ba02025385a98 Reviewed-on: https://chromium-review.googlesource.com/869693 Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#530392} 19 January 2018, 02:26:30 UTC
a9ed355 J.C. Jones 18 January 2018, 22:55:13 UTC Merge pull request #7500 from apowers313/webauthn-wd05-api-updates WebAuthn WD-07 API updates 18 January 2018, 22:55:13 UTC
a6714ab Stephen McGruer 18 January 2018, 21:30:35 UTC Revert "[USVString] Change the type of url with USVString in navigator.sendBeacon" This reverts commit f164b48cc02fbcb3c27cf53910818423fb11e3ae. Reason for revert: Appears to cause usvstring-reflection.html test failures on WebKit Linux Trusty Leak, e.g.: https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20Leak/14513 04:33:47.078 30339 worker/3 external/wpt/html/dom/usvstring-reflection.html failed: 04:33:47.078 30339 worker/3 leak detected: ({"numberOfLiveDocuments":[1,2],"numberOfLiveNodes":[4,18],"numberOfLivePausableObjects":[2,3],"numberOfLiveResources":[0,3]}) Original change's description: > [USVString] Change the type of url with USVString in navigator.sendBeacon > > Latest spec has used USVString instead of DOMString for url argument. > - spec: https://w3c.github.io/beacon/#dom-navigator-sendbeacon > > This CL replaces DOMString type with USVString type according to the spec. > > Bug: 790860 > Change-Id: I66825c20395ea6fd6b26e32fc8f6508fd85aeef7 > Reviewed-on: https://chromium-review.googlesource.com/869970 > Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org> > Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> > Cr-Commit-Position: refs/heads/master@{#530123} TBR=tyoshino@chromium.org,gyuyoung.kim@lge.com Change-Id: I36a251d058756f509daa330c952546b7a1064130 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 790860 Reviewed-on: https://chromium-review.googlesource.com/874050 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#530154} 18 January 2018, 22:00:56 UTC
9e9aede Darren Shen 18 January 2018, 21:19:57 UTC [css-typed-om] Upstream style value subclass tests as tentative This patch upstreams style value subclass tests as tentative WPTs. We modified the include paths to match WPT. Our plan is to eventually clean up these tests and remove the tentative label. TBR=nainar@chromium.org Bug: 774887 Change-Id: Ia0b683eb41fa0f65bfdce54315ea687123a78a76 Reviewed-on: https://chromium-review.googlesource.com/872475 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#530269} 18 January 2018, 21:40:50 UTC
9fbcfa4 Gyuyoung Kim 18 January 2018, 12:31:49 UTC [USVString] Change the type of url with USVString in navigator.sendBeacon Latest spec has used USVString instead of DOMString for url argument. - spec: https://w3c.github.io/beacon/#dom-navigator-sendbeacon This CL replaces DOMString type with USVString type according to the spec. Bug: 790860 Change-Id: I66825c20395ea6fd6b26e32fc8f6508fd85aeef7 Reviewed-on: https://chromium-review.googlesource.com/869970 Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Cr-Commit-Position: refs/heads/master@{#530123} 18 January 2018, 21:22:36 UTC
944948d Nicolas Pena 18 January 2018, 19:19:49 UTC Add takeRecords() for PerformanceObserver Intent to Implement and Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/xEXD9C48c1k Bug: chromium:799929 Change-Id: Ic8c0f3fdf9f515f58effc4f8ac73591604f9a9af Reviewed-on: https://chromium-review.googlesource.com/820892 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Timothy Dresser <tdresser@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#530219} 18 January 2018, 19:29:51 UTC
672fbff Stephen McGruer 18 January 2018, 17:12:24 UTC Start porting position:sticky tests to javascript-tests Previously the position:sticky tests were all reftests. This was not really necessary as sticky positioning can be observed via js-readable data, so converting them to js tests improves the runtime of the suite. To ensure that user-agents properly render sticky objects, a basic rendering ref test is created. Bug: None Change-Id: I2cc1635cbaa73b20f610e22085520e50e2b88d26 Reviewed-on: https://chromium-review.googlesource.com/854997 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#530172} 18 January 2018, 17:31:15 UTC
ee350b1 Manuel Rego Casasnovas 18 January 2018, 15:31:44 UTC Merge pull request #9089 from mrego/fix-image [css-grid] More fixes grid-alignment-implies-size-change tests 18 January 2018, 15:31:44 UTC
1f69b42 Manuel Rego Casasnovas 18 January 2018, 14:14:05 UTC [css-grid] More fixes grid-alignment-implies-size-change tests More issues detected on w3c/csswg-drafts#2194. This time it's fixing the relative path to an image. The patch copies the 100x100-green.png file under the relative support/ folder and modifies the paths to it in the tests. 18 January 2018, 14:15:25 UTC
506cf5b Sriram 18 January 2018, 13:00:34 UTC Upstream track-cue-rendering-after-controls-[added|removed].html tests Upstream the below tests from media/track/ to wpt 1. track-cue-rendering-after-controls-added.html 2. track-cue-rendering-after-controls-removed.html Bug: 782555 Change-Id: I0de38969de04575ae87ffb20c3766f19c0d5269e Reviewed-on: https://chromium-review.googlesource.com/872990 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: srirama chandra sekhar <srirama.m@samsung.com> Cr-Commit-Position: refs/heads/master@{#530128} 18 January 2018, 13:25:28 UTC
549dc64 Brian Burg 17 January 2018, 23:01:09 UTC webdriver: add missing __init__.py files to help pytest disambiguate test files with the same basename. 18 January 2018, 11:54:59 UTC
4f82697 Darren Shen 18 January 2018, 10:53:29 UTC [css-typed-om] Clean up StylePropertyMap.delete tests. This patch does the following to clean up the StylePropertyMap.delete tests for WPT: - We split happy cases and sad cases into separate files. - We used to test delete by calling .delete and then checking if .has returns false. There are a few problems with this: - it's arbitrary why we use .has (and not, say, .get) to check if the property was deleted. - our tests for .delete depend on .has to be implemented correctly. - we are not actually testing that the property was removed from element's style (i.e. the style map may not propagate changes to the element's style correctly and the tests wouldn't catch that). So, to avoid these downsides, we change the tests to call .delete and then checking the element's actual style from CSSOM. - For some reason declared didn't have .delete tests but had an expectation file. We add a test for declared .delete, which is basically the same as the inline tests but using a rule instead of an element. - We removed the .tentative extension. Bug: 774887 Change-Id: Ie911b62e493d0ce371b85b1a1a0597fac4ca3f4e Reviewed-on: https://chromium-review.googlesource.com/872515 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#530113} 18 January 2018, 11:43:21 UTC
fdeb00d Shanmuga Pandi M 18 January 2018, 10:03:30 UTC Upstream svg/dom/SVGAnimated*.html to web-platform-tests Bug: 636710 Change-Id: Ib16d67e6abe0b64fe426146dd38cacd0db9f0d59 Reviewed-on: https://chromium-review.googlesource.com/872555 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Shanmuga Pandi <shanmuga.m@samsung.com> Cr-Commit-Position: refs/heads/master@{#530104} 18 January 2018, 10:24:33 UTC
ddfc95c Anthony Ramine 18 January 2018, 09:10:40 UTC Merge pull request #9084 from w3c/sync_08e864fd23048d707cc42bed8538e644d8dec950 Merge pull request #9084 from sync_08e864fd23048d707cc42bed8538e644d8dec950 18 January 2018, 09:10:40 UTC
4d63494 Anthony Ramine 18 January 2018, 09:10:27 UTC Merge pull request #9083 from w3c/sync_9934f16e251b3f430114013e2c7c9dce1b961968 Merge pull request #9083 from sync_9934f16e251b3f430114013e2c7c9dce1b961968 18 January 2018, 09:10:27 UTC
08e864f tigercosmos 18 January 2018, 09:10:15 UTC implement range input sanitization Upstreamed from https://github.com/servo/servo/pull/19761 [ci skip] 18 January 2018, 09:10:16 UTC
9934f16 Anthony Ramine 18 January 2018, 09:10:14 UTC Don't bind hostname when running wptrunner for Servo Upstreamed from https://github.com/servo/servo/pull/19738 [ci skip] 18 January 2018, 09:10:16 UTC
0343d0d Darren Shen 18 January 2018, 06:33:31 UTC [css-typed-om] Clean up CSSUnparsedValue serialization test This patch cleans up the CSSUnparsedValue serialization tests to make it more suitable for WPT. We remove the .tentative extension. Bug: 774887 Change-Id: Ifaca6831f0ee60b1515a719ed13438dc1842134f Reviewed-on: https://chromium-review.googlesource.com/871990 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#530072} 18 January 2018, 07:00:58 UTC
70d0ebb Manuel Rego Casasnovas 18 January 2018, 05:25:55 UTC Merge pull request #9071 from mrego/fix-grid-alignment-implies-size-change-tests [css-grid] Fix grid-alignment-implies-size-change tests 18 January 2018, 05:25:55 UTC
40f4239 Darren Shen 18 January 2018, 03:12:12 UTC [css-typed-om] Upstream CSSPositionValue serialization to WPT. This patch upstreams the CSSPositionValue serialization test [1] to WPT. Note that the original test was accidentally deleted in [2]. [1] https://chromium.googlesource.com/chromium/src/+/4853213e011c9f5b8bc67f4dd966a3213e71fd87/third_party/WebKit/LayoutTests/typedcssom/stylevalue-serialization/cssPositionValue.html [2] https://chromium.googlesource.com/chromium/src/+/ce65e32cc96765afe77a7388c1a2a876b37d593e Bug: 774887 Change-Id: I1a88925ac37802ae47aff35e65f72592fcfb7f9e Reviewed-on: https://chromium-review.googlesource.com/869010 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#530033} 18 January 2018, 04:18:40 UTC
6c7a03e Darren Shen 18 January 2018, 00:23:56 UTC [css-typed-om] Upstream style property map tests as tentative This patch upstreams style property map tests as tentative WPTs. We modified the include paths to match WPT. Our plan is to eventually clean up these tests and remove the tentative label. TBR=nainar@chromium.org Bug: 774887 Change-Id: I20e6e025e9a78678db4e63ce3a82905d0fa3b20d Reviewed-on: https://chromium-review.googlesource.com/871731 Reviewed-by: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#529960} 18 January 2018, 02:45:12 UTC
ff62197 Ian Kilpatrick 18 January 2018, 00:05:19 UTC [css-layout-api] Adds LayoutWorkletGlobalScope and proxy. Additionally adds relevant tests. After this patch CSS.layoutWorklet.addModule() should work correctly. This is effectively a clone of PaintWorkletGlobalScope & related classes. Bug: 726125 Change-Id: If4fef01fb518b0e549f05d91407699f249924ce1 Reviewed-on: https://chromium-review.googlesource.com/869467 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#529955} 18 January 2018, 01:47:32 UTC
0e5303d Darren Shen 17 January 2018, 21:21:35 UTC [css-typed-om] Upstream serialization & normalization tests as tentative This patch upstreams serialization and normalization tests as tentative WPTs. We modified the include paths to match WPT. We also copied the existing resources in our layout tests. Our plan is to eventually clean up these tests and remove the tentative label. Bug: 774887 Change-Id: I7651b8003bb7917157c6f6008b7093c8e85d9a2d Reviewed-on: https://chromium-review.googlesource.com/869631 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#529893} 18 January 2018, 01:38:26 UTC
6b99066 Wanming Lin 18 January 2018, 01:32:42 UTC Merge pull request #6769 from Honry/sensor/linearaccelerationsensor Add functional tests for LinearAccelerationSensor 18 January 2018, 01:32:42 UTC
aeebec8 Wanming Lin 18 January 2018, 01:32:07 UTC Merge pull request #7431 from Honry/sensor/more-layout-tests Generic Sensor: import tests from Chromium Layout test suite 18 January 2018, 01:32:07 UTC
1f28397 Wanming Lin 18 January 2018, 01:29:58 UTC Recurse to nested arrays in reading arrays (#8797) Use assert_object_equals instead of assert_array_equals which would compare individual values in nested arrays 18 January 2018, 01:29:58 UTC
54307bd Wanming Lin 18 January 2018, 01:29:16 UTC Sensor FP tests need title (#8965) 18 January 2018, 01:29:16 UTC
bf0f93a Eric Willigers 18 January 2018, 00:44:39 UTC Merge pull request #8719 from ewilligers/path-error-handling Test that invalid paths do not render 18 January 2018, 00:44:39 UTC
c6beb77 Eric Willigers 18 January 2018, 00:36:27 UTC Merge pull request #8720 from ewilligers/closepath-completes-segment SVG: closepath completes command by initial point 18 January 2018, 00:36:27 UTC
33e0b54 Eric Willigers 18 January 2018, 00:22:47 UTC Merge pull request #8990 from ewilligers/masking Parsing tests for clip, clip-path, clip-rule 18 January 2018, 00:22:47 UTC
e856c3d Manuel Rego Casasnovas 17 January 2018, 22:15:20 UTC Process items in DOM order in check-layout-th.js If you have a test with 5 elements with class "foobar" and you use checkLayout(".foobar"), if the 2nd element has a failure you'll get something like "FAIL .foobar 4". However, you'd be expecting something like "FAIL .foobar 2". This patch will make that when you get a message like "FAIL .foobar 2" it's actually the 2nd element with class "foobar" in the DOM, and not the 2nd starting from the bottom (like it happens now). The fact of not using the DOM order, but the reverse one, was changed long time ago in r141147 (https://webkit.org/b/105407) to avoid problems with offsetTop, as results were moving things down. But if that's the case, adding a <div id="log"> at the bottom of the test will fix it and the results will be easier to understand. On top of that, it's worth highlight that this order stuff doesn't affect to any of the check-layout-th.js tests. The patch modifies a few expected failures that were showing the wrong indexes. Change-Id: I209092e14ab5594f1ee1a440a3a2dbe54d9e15d9 Reviewed-on: https://chromium-review.googlesource.com/870035 Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#529906} 18 January 2018, 00:14:35 UTC
9cde3fe Eric Willigers 18 December 2017, 05:44:44 UTC Test that invalid paths do not render Paths with no data set, and invalid path commands appearing after valid commands, do not contribute to rendering or bounding box calculations. https://svgwg.org/svg2-draft/single-page.html#changes-paths "Define ‘path’, ‘polygon’ and ‘polyline’ elements with no data set (empty or zero valid commands) to not render." 17 January 2018, 23:43:09 UTC
60f818c John Jansen 17 January 2018, 23:06:39 UTC Use -- for MicrosoftWebDriver parameters (#9070) MicrosoftWebDriver requires "--" not "-". I don't want to change the cmd_args() function because that may be used by other drivers on Windows. 17 January 2018, 23:06:39 UTC
5d2bdef Chris Cunningham 17 January 2018, 20:45:27 UTC Delete blink MSE config change tests to de-dup with upstream wpt. The deletion is limited to the config-change tests to scope the work of reconciling differences between blink and wpt. Non-config-change tests are also present in both folders and may be de-dupped later on. There were a few things to reconcile in the de-duping. 1) test js 2) files For 1) The mediasource-config-changes.js differed slightly. This CL brings in the more verbose comments from blink while keeping a few additional asserts from wpt. I also opportunistically merged comments/asserts in mediasource-play.html. For 2) The upstream WebM config change files match. The upstream MP4 config change files are slightly different, but just as good. Their history all takes the form here https://github.com/w3c/web-platform-tests/commits/master/media-source/mp4/test-a-128k-44100Hz-1ch.mp4 With the intial commit matching what we have and the later commit remuxing to tweak movie-fragment relative addresssing. FOR POSTERITY... DETAILS OF MOVEI-FRAG-RELATIVE-ADDRESSING: MSE spec requires MovieFragBox (MOOF) must use movie-fragment relative addresssing https://www.w3.org/TR/mse-byte-stream-format-isobmff/#movie-fragment-relative-addressing 1. First TRUN in a TrackFragmentBox (TRAF) has data-offset-present flag set (0x01) -- AND EITHER-- 2a. every TrackFragmentBox (in its header TFHD) has default-base-is-moof flag (0x20000) 2b. OR MovieFragBox (MOOF) contains a single TRAF and that box (in its TFHD) DOES NOT SET base-data-offset-present flag (0x1) DO WE ENFORCE THE ABOVE? 1. no. we allow both data_offset_present as well as not present https://cs.chromium.org/chromium/src/media/formats/mp4/box_definitions.cc?rcl=b768fa508f99dd9a6a4cf7689d6ecccd1b66a5fb&l=1327 2a. no. we comment that we would like to, but that it would fail a lot of otherwise valid files https://cs.chromium.org/chromium/src/media/formats/mp4/box_definitions.cc?rcl=105b3747c5eab20245f2e13834d33701f4ec2e50&l=1282 2b. yes, but we go further. we assert that all TFHDs DO NOT set base-data-offset-present (regardless of how many are in the given MOOF) https://cs.chromium.org/chromium/src/media/formats/mp4/box_definitions.cc?rcl=242b78c83ad56851fb49f0f9e2001cdeecebd935&l=1283 Aaron's original files met req 1, but do not meet 2a (tfhd.flags == 0), but does meet 2b (flags are 0, and every MOOF has only one TRAF Aarons updated files (in wpt) meet req 1, also meet 2a (tfhd.flags == 0x20000), also meets 2b (every MOOF has only one TRAF, none set base-data offset-present) In short, either would be fine and the latest files go above and beyond the requirements. Change-Id: I91fca61196d7d8d0bf0f45655269fdb48b3ce852 Reviewed-on: https://chromium-review.googlesource.com/862993 Reviewed-by: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#529870} 17 January 2018, 22:05:55 UTC
d9fef5c Ovidio Henriquez 17 January 2018, 20:45:21 UTC bluetooth: Migrate generated server tests This change migrates the scripts to generate GATT server tests and the generated tests themselves to wpt/. BUG=509038 Change-Id: Ie9fbc6442f232b61091cd2f83c832974450936e8 Reviewed-on: https://chromium-review.googlesource.com/843065 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#529857} 17 January 2018, 21:37:14 UTC
235abce Manuel Rego Casasnovas 17 January 2018, 20:55:59 UTC [css-grid] Fix grid-alignment-implies-size-change tests This should fix w3c/csswg-drafts#2194 as it's moving the style-change.js script under css/css-grid/alignment/support/ folder. On top of that it's fixing those tests as the second checkLayout() call was never checked. This was because by default checkLayout() calls done(), and the test thinks it has already finished. Modified the call to checkLayout() in the script style-change.js and calling manually done() in the tests fixes the problem. 17 January 2018, 20:55:59 UTC
9e00941 Ian Clelland 17 January 2018, 17:13:11 UTC Treat policy-disallowed sync xhr as a network error Bug: 661283 Change-Id: I311cef40e03a264ca9db601842477d502e7cf12d Reviewed-on: https://chromium-review.googlesource.com/804057 Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org> Reviewed-by: Rick Byers <rbyers@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#529775} 17 January 2018, 19:17:10 UTC
39c94cc arthursonzogni 17 January 2018, 15:02:01 UTC Upgrade Insecure Requests: OOPIF support, bugfixes & tests. This CL fixes several bugs with Upgrade Insecure Requests. The main one is that URL were compared against the 'upgrade insecure navigation set' of the frame that is navigating instead of the frame that has initiated the navigation. It fixes bug 796538. 8 new tests are added to ensure regressions won't happen anymore. Finally, it adds the support for OOPIF. The 'upgrade insecure navigations set' is now replicated across the different processes. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation BUG=670219, 796538 Change-Id: I1d138989a1873cd902435de25845ae660769ff98 Reviewed-on: https://chromium-review.googlesource.com/848836 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#529732} 17 January 2018, 17:33:51 UTC
c3c0eec Vincent Scheib 17 January 2018, 15:01:48 UTC bluetooth web platform test readme section for generator.py Bug: Change-Id: I3b851d54ec3a763abaa602d41f4be87a7915b30f Reviewed-on: https://chromium-review.googlesource.com/864624 Reviewed-by: Conley Owens <cco3@chromium.org> Commit-Queue: Vincent Scheib <scheib@chromium.org> Cr-Commit-Position: refs/heads/master@{#529612} 17 January 2018, 17:13:04 UTC
f6c8e01 Bhagirathi Satpathy 17 January 2018, 15:01:41 UTC Modified location |href| atribute type from DOMString to USVString location |href| is implemented as URLString which is typedefed as (DOMString or TrustedURL). As per spec, |href| should be USVString. Since URLString is used only for |href| attribute, So 'DOMString' is modified to 'USVString' in typedef. https://html.spec.whatwg.org/multipage/history.html#location Bug: 790860 Change-Id: Ia76a5bb760216978a85316b29cb7415c6585feef Reviewed-on: https://chromium-review.googlesource.com/866619 Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Bhagirathi Satpathy <bhagirathi.s@samsung.com> Cr-Commit-Position: refs/heads/master@{#529556} 17 January 2018, 17:02:25 UTC
a88102c Anne van Kesteren 17 January 2018, 08:26:50 UTC HTML: correct RenderingContext typedef See https://github.com/whatwg/html/pull/3363. 17 January 2018, 15:35:50 UTC
90a4eac Marijn Kruisselbrink 16 January 2018, 21:22:39 UTC Set explicit_timeout to true in nested window test environment in blob URL tests. This way the tests will timeout when the outer window decides time has expired, rather than let the nested window decide it earlier. This mimics the behavior of fetch_tests_from_worker, since WorkerTestEnvironment always behaves as if explicit_timeout is set to true. This should fix spurious timeouts of this test that aren't detected as timeouts by our test runner (and specifically cases where we don't actually consider the test as timed out). Bug: 801078 Change-Id: I3a884bd746afcefd5cbe5008db7df4a609eb0044 Reviewed-on: https://chromium-review.googlesource.com/865002 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#529500} 17 January 2018, 15:12:33 UTC
0c2ee4f Ella Ge 16 January 2018, 16:52:48 UTC Use integer subtraction to calculate movement_x/y This CL changes the calculation of movement_x/y from "floor(cur_pos - last_pos)" to "floor(cur_pos) - floor(last_pos)" We store mouse event coordinates as pointF, If we have mouse move like: 0 -> 1.4 -> 2.8 -> 4.2 "floor(cur_pos - last_pos)" will get movement: 0->1.4=1; 1.4->2.8=1; 2.8->4.2=1. in total is 3. So that'll lose fraction part movement. To get correct movement_x/y, need to use "floor(cur_pos) - floor(last_pos)" instead. Bug: 795179 Change-Id: Iabae78962541cacc9f6a79eb0290a610f1818f02 Reviewed-on: https://chromium-review.googlesource.com/862903 Commit-Queue: Ella Ge <eirage@chromium.org> Reviewed-by: Timothy Dresser <tdresser@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#529440} 17 January 2018, 15:12:27 UTC
0ad436b Georg Neis 16 January 2018, 16:16:42 UTC [ES6 Modules] Fix a test. This test incorrectly assumed a particular evaluation order in the presence of an async module script. Bug: Change-Id: I77faf777227cbfbe57a58e3779cbaca6dd3c9585 Reviewed-on: https://chromium-review.googlesource.com/859769 Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#529434} 17 January 2018, 15:01:36 UTC
d2af033 Mike West 16 January 2018, 14:02:52 UTC CSP: Implement 'prefetch-src' behind a flag. As discussed in https://github.com/w3c/webappsec-csp/issues/107, 'prefetch-src' gives developers the ability to control the endpoints from which resources may be prefetched. Bug: 801561 Change-Id: Ifedd78e3101ea66d242c6f3c7a2f49385a681bd1 Reviewed-on: https://chromium-review.googlesource.com/864362 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Cr-Commit-Position: refs/heads/master@{#529413} 17 January 2018, 15:01:33 UTC
93c6598 jgraham 17 January 2018, 12:50:33 UTC Remove all remaining references to b2g (#9052) 17 January 2018, 12:50:33 UTC
d5566dc Marcos Cáceres 17 January 2018, 08:51:53 UTC refactor: use assert_unreached where possible (#9045) 17 January 2018, 08:51:53 UTC
4eb38a4 Eric Willigers 17 January 2018, 00:19:11 UTC Merge pull request #8717 from ewilligers/SVGAnimatedPathData-removed Test that SVGAnimatedPathData is not supported 17 January 2018, 00:19:11 UTC
f89badb Eric Willigers 17 January 2018, 00:18:00 UTC Merge pull request #8716 from ewilligers/SVGGeometryElement-rect Test that geometry elements have path length 17 January 2018, 00:18:00 UTC
3bd9f46 Eric Willigers 17 January 2018, 00:17:17 UTC Merge pull request #8714 from ewilligers/pathLength Test pathDistance attribute 17 January 2018, 00:17:17 UTC
b4b9ec4 Geoffrey Sneddon 16 January 2018, 19:49:24 UTC Add slow etc. markers to some tools.wpt tests This makes it possible to run these locally in a test-debug cycle in a reasonable time. 16 January 2018, 21:53:27 UTC
223c99d Geoffrey Sneddon 16 January 2018, 19:46:16 UTC Fix tools.wpt.stability throwing because of a cyclic import The import was added in bad11688098ff2050305a075cbd03d4794affceb, but it seems like tools.wpt.markdown.err_string is seemingly just dead code so we can fix the cycle by deleting the code that needs it. This adds a pretty much unrelated test for wpt.tools.stability, but this gives us test coverage of it being able to be imported! (It's also the only function in the module I could figure out how to test…) 16 January 2018, 21:53:27 UTC
9b10724 Chris Lilley 16 January 2018, 19:33:41 UTC css 2.1 class selector tests, also for Selectors 3 16 January 2018, 19:33:41 UTC
262e3e1 Ms2ger 16 January 2018, 15:02:50 UTC In assert_throws, check that the exception is a non-null object. We were bitten once again by the surprising JavaScript incident that made `typeof null` return "object". This commit adds a check that we're dealing with a real object. This commit also moves these checks up-front, as it was duplicated between the code paths that handle an object `code` argument and a string `code` argument, respectively. 16 January 2018, 15:34:52 UTC
5c5f37c Geoffrey Sneddon 16 January 2018, 11:04:07 UTC Get ImageBitmap tests working with MP4 too 16 January 2018, 15:24:32 UTC
0ceb77c Geoffrey Sneddon 15 January 2018, 15:22:21 UTC Fix #9012: Add an MP4 copy of images/pattern.png 16 January 2018, 15:24:32 UTC
35231c2 Geoffrey Sneddon 16 January 2018, 14:11:42 UTC Merge pull request #8524 from gsnedders/flake8-wptrunner Run flake8 on wptrunner, and run the same flakes everywhere 16 January 2018, 14:11:42 UTC
6cc8fc5 Sriram 16 January 2018, 09:29:18 UTC Upstream track-cues-rendering-[line*, transformed*] tests Upstream the below tests from media/track/ to wpt 1. track-cue-rendering-line-doesnt-fit.html 2. track-cue-rendering-transformed-video.html Bug: 782555 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Iec392fee700df036650c9d87abea9ffe970bf492 Reviewed-on: https://chromium-review.googlesource.com/867188 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: srirama chandra sekhar <srirama.m@samsung.com> Cr-Commit-Position: refs/heads/master@{#529387} 16 January 2018, 09:38:11 UTC
da1d4e3 Rune Lillesveen 16 January 2018, 08:49:19 UTC Rebuild layout tree through assigned slots. We skip slotted slots for layout tree rebuilding when slots are not part of the flat tree. As slots can be rendered when they are part of the flat tree we need to rebuild through assigned children of slots, not distributed nodes. Also, when marking ancestors for layout tree rebuilding, mark slots and slots to which they are assigned. Added css-scoping suite to virtual suite for IncrementalShadowDOM in order to test styling of slots in flat tree. Bug: 660265 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Id88cbfba32a021b2380f7e41d8784d3956575206 Reviewed-on: https://chromium-review.googlesource.com/866746 Reviewed-by: Hayato Ito <hayato@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#529382} 16 January 2018, 08:56:40 UTC
37585cb Timothy Gu 26 December 2017, 07:26:56 UTC Do not assume document stringifies to HTMLDocument Per current spec, document should stringify to "[object Document]". Work to remove "HTMLDocument" is tracked in https://github.com/whatwg/dom/issues/221. 16 January 2018, 05:13:56 UTC
bad1168 Geoffrey Sneddon 30 November 2017, 19:49:36 UTC Standardise our flake8 setup This moves everything to running the same set of flakes, and changes what's needed to make them all pass. 16 January 2018, 01:38:04 UTC
d0dac59 Geoffrey Sneddon 30 November 2017, 19:24:27 UTC Make wptrunner use most of the same flakes as other tools 16 January 2018, 01:37:11 UTC
46466c8 Geoffrey Sneddon 30 November 2017, 19:05:44 UTC Start running flake8 on wptrunner 16 January 2018, 01:25:43 UTC
3561e2b Xida Chen 15 January 2018, 23:50:45 UTC [PaintWorklet] Let PaintRenderingContext2D override two virtual functions I noticed that the BaseRenderingContext2D class has IsAccelerated() and CanCreateCanvas2DBuffer() that are not overridden by PaintRenderingContext2D. These two functions should be overridden, otherwise when drawImage() is called by a PaintRenderingContext2D object, it will reach the base version of these two function and hit the NOTREACHED() check and will crash. The reason that there is no crash at this moment is that one of the layout test is not correctly written. This CL fix the crash and the layout test as well. Bug: None Change-Id: I26b54fe5d757bee1199ca2dad953b56b4e5efb1f Reviewed-on: https://chromium-review.googlesource.com/867516 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by: Justin Novosad <junov@chromium.org> Cr-Commit-Position: refs/heads/master@{#529346} 16 January 2018, 00:04:52 UTC
03d67ae csnardi 16 January 2018, 00:01:56 UTC Add references for CSS2/selectors (#9019) Many CSS2/selectors tests were missing references. This change adds in references for a large number of these tests. 16 January 2018, 00:01:56 UTC
83ac24a arthursonzogni 15 January 2018, 12:33:55 UTC CSP: Fix blocked form submission with target="_blank" This fixes bug 798698. It happens when the "form-action 'self'" CSP is used and a form submission with the attribute "target='_blank'" happens. Since the form-action CSP is checked against the CSP of the new windows instead of the one of the old window, it was blocked. This regression probably started after this CL (which is good): https://chromium-review.googlesource.com/c/chromium/src/+/765969. Solution was to disable browser side checks and only rely on renderer side checks for the initial load. Bug: 798698 Change-Id: Iade17b80f493af265ddb86fe95305d96c7ce0975 Reviewed-on: https://chromium-review.googlesource.com/857503 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#529255} 15 January 2018, 20:07:00 UTC
99b7b90 Fredrik Söderquist 15 January 2018, 18:33:07 UTC Fix offset-anchor alignment for offset-path The anchor point should align with the point on the path/shape/... Also avoid recomputing transform-origin in ApplyMotionPathTransform since the function takes origin_x/y as arguments, so those can be used rather than recomputing the value(s). Change-Id: I3c173cdc3d307057a37564a37b0e87044dbeaf9d Reviewed-on: https://chromium-review.googlesource.com/808885 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#529282} 15 January 2018, 19:25:22 UTC
back to top