Pull http://w3c-test.org/geolocation-API/ tests |
||||||||
Issue descriptionAs said, pull them so we can start tracking our implementation against them. (I think I did it once but most failed due to our test server not using https:// but I'm not 100% sure).
,
Apr 12 2017
,
Apr 12 2017
,
Apr 13 2017
Found the reason this wasn't evident and I'm making a PR for it: https://github.com/w3c/web-platform-tests/pull/5559
,
May 4 2017
,
May 5 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9924ab42f638a24c64ec0dc9c450bf6bbf294e3a commit 9924ab42f638a24c64ec0dc9c450bf6bbf294e3a Author: foolip <foolip@chromium.org> Date: Fri May 05 12:59:35 2017 Import Geolocation and Vibration web-platform-tests BUG= 711032 Review-Url: https://codereview.chromium.org/2860603002 Cr-Commit-Position: refs/heads/master@{#469634} [modify] https://crrev.com/9924ab42f638a24c64ec0dc9c450bf6bbf294e3a/third_party/WebKit/LayoutTests/W3CImportExpectations
,
May 5 2017
Also, https://github.com/w3c/web-platform-tests/pull/5559 is closed thanks to the infatigable efforts of foolip@ ! \o/
,
May 6 2017
https://chromium-review.googlesource.com/c/498227/?polygerrit=1 is the roll into Chromium nd the geolocation-api tests look good (except the -manual.html, that failed).
,
Sep 22 2017
,
Sep 22 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by mcasas@chromium.org
, Apr 12 2017