Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Step 11 of getAvailability should not run "in parallel" #381

Copy link
Copy link
Closed
@tidoust

Description

@tidoust
Issue body actions

I failed to notice that when I reviewed the update, but I think "in parallel" is wrong in step 11 of the getAvailability algorithm which instructs the user agent to "Run the algorithm to monitor the list of available presentation displays in parallel".

In practice, if the algorithm is run in parallel, that means the first time an app calls getAvailability, it will always end up with a PresentationAvailability object whose value is false (set by step 9.1 since the list of available presentation displays is empty to start with). Is that the intent? I would rather expect the value to convey the outcome of running the monitoring algorithm.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.