Closed Bug 1595868 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 20217 - [InstalledApp] Move & update some of the web tests to wpt.

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox72 fixed)

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 20217 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/20217
Details from upstream follow.

Rayan Kanso <rayankans@chromium.org> wrote:

[InstalledApp] Move & update some of the web tests to wpt.

Also update the idl definition to the correct value.

Change-Id: Ida7936ef43733702f20c5a6efa9ef7a869de09c6
Reviewed-on: https://chromium-review.googlesource.com/1912900
WPT-Export-Revision: 7cf90710db93c840d7d89d0fbd954fe925d8fbd2

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ca968fbbc3a0 [wpt PR 20217] - [InstalledApp] Move & update some of the web tests to wpt., a=testonly https://hg.mozilla.org/integration/autoland/rev/38c98917860e [wpt PR 20217] - Update wpt metadata, a=testonly

GitHub CI Results

wpt.fyi PR Results Base Results

Ran 2 tests and 8 subtests

Firefox

OK : 2
PASS: 4
FAIL: 4

Chrome

OK : 2
PASS: 8

Safari

OK : 2
PASS: 4
FAIL: 4

New tests that's don't pass

/installedapp/idlharness.https.window.html
Navigator interface: operation getInstalledRelatedApps(): Firefox: FAIL, Chrome: PASS, Safari: FAIL
Navigator interface: navigator must inherit property "getInstalledRelatedApps()" with the proper type: Firefox: FAIL, Chrome: PASS, Safari: FAIL

/installedapp/installedapp.https.window.html
Calling getInstalledrelatedApps from an iframe fails: Firefox: FAIL, Chrome: PASS, Safari: FAIL
Check calling getInstalledRelatedApps works as expected: Firefox: FAIL, Chrome: PASS, Safari: FAIL

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.