Skip to content

[remote-playback] Test prompt() fulfillment order (w3c/remote-playback#160) - #64396

Draft
markafoltz wants to merge 1 commit into
markafoltz/remote-playback-3-new-testsfrom
markafoltz/remote-playback-4-spec-pr-160
Draft

markafoltz wants to merge 1 commit into
markafoltz/remote-playback-3-new-testsfrom
markafoltz/remote-playback-4-spec-pr-160

Conversation

@markafoltz

@markafoltz markafoltz commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

Per w3c/remote-playback#160, the user agent queues tasks to fulfill the
Promise returned by prompt() before firing the connecting event (when
the user selects a device) or the disconnect event (when the user
chooses to disconnect).

  • Add prompt-resolves-before-connecting-manual.html, which verifies that
    the Promise reactions run before the connecting event is fired, and
    that the state is "connecting" at both points.
  • event-handlers-manual.html: check that the Promise returned by the
    second prompt() resolves while still connected, before the disconnect
    event is fired.
  • Reference the new test from tests that do not check this order.

Stack created with GitHub Stacks CLI • Give Feedback 💬


Part of stack https://github.com/web-platform-tests/wpt/stack/64397 (each PR shows only its own layer):

  1. [remote-playback] Use longer media and wait for metadata before prompting #64393 General test fixups (longer media, wait for metadata)
  2. [remote-playback] Fix specific manual tests #64394 Fixes for specific tests
  3. [remote-playback] Add manual test for browser or device initiated disconnect #64395 New tests that do not depend on spec changes
  4. [remote-playback] Test prompt() fulfillment order (w3c/remote-playback#160) #64396 New/updated tests that depend on Queue tasks in parallel steps of RemotePlayback.prompt() w3c/remote-playback#160

Context: Chrome failures in https://w3c.github.io/test-results/remote-playback/all.html are largely caused by the 5s test clip, which is below Chrome's 15s minimum for remote playback.

Keeping this PR as a draft until w3c/remote-playback#160 lands.

…k#160)

Per w3c/remote-playback#160, the user agent queues tasks to fulfill the
Promise returned by prompt() before firing the connecting event (when
the user selects a device) or the disconnect event (when the user
chooses to disconnect).

- Add prompt-resolves-before-connecting-manual.html, which verifies that
  the Promise reactions run before the connecting event is fired, and
  that the state is "connecting" at both points.
- event-handlers-manual.html: check that the Promise returned by the
  second prompt() resolves while still connected, before the disconnect
  event is fired.
- Reference the new test from tests that do not check this order.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant