The I18N working group is doing some housekeeping and found that we didn't forward the below issue. Apologies for being late with this. Note that this may already be addressed by other threads about language.
http://w3c.github.io/presentation-api/
Section: The list of available presentation displays
This section contains the directive that:
The user agent MUST keep a list of available presentation displays. This current list of presentation displays may be used for starting new presentations, and is populated based on an implementation specific discovery mechanism. It is set to the most recent result of the algorithm to monitor the list of available presentation displays.
This list appears to be identified using URLs for each presentation display. The specification is silent about such issues as display name, sorting order, etc. These issues may affect actual implementation, even though this API doesn't really address the issue. Should it?
Reactions are currently unavailable
The I18N working group is doing some housekeeping and found that we didn't forward the below issue. Apologies for being late with this. Note that this may already be addressed by other threads about language.
http://w3c.github.io/presentation-api/
Section: The list of available presentation displays
This section contains the directive that:
The user agent MUST keep a list of available presentation displays. This current list of presentation displays may be used for starting new presentations, and is populated based on an implementation specific discovery mechanism. It is set to the most recent result of the algorithm to monitor the list of available presentation displays.
This list appears to be identified using URLs for each presentation display. The specification is silent about such issues as display name, sorting order, etc. These issues may affect actual implementation, even though this API doesn't really address the issue. Should it?