Step 7. of the select a presentation display algorithm tells the user agent to monitor the list of available presentation displays. This is meant to fill out the list of available presentation displays, which needs to be non empty for the display selection to do something.
The monitoring algorithm fills out that list based on the contents of the set of presentation availability objects. Problem is that set is only filled out by the getAvailability
algorithm.
In short, if an app calls start
without first calling getAvailability
, the monitoring algorithm will simply create an empty list of available presentation displays which would make start
end up with a NotFoundError
exception.
I guess the easiest way to fix that would be to have the selection algorithm set the presentation display availability right before current step 7, as done in getAvailability
. Something like:
Now, in theory, there should be no reason to introduce PresentationAvailability
objects in start
. Oh well...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4