This document describes the results in Presentation API controlling UA tests, including all detailed failure behavior that might be omitted due to break caused by its preceeding assertion failure.
- CD65: Chrome Canary 65.0.3318.0 for Desktop (Mac)
- FA59: Firefox Nightly 59.0a1 (2018-01-14) for Android
- FA59:
- Calling Presentation API on Firefox Nightly throws
SecurityErrorwhen a URL likecast:is included in the presentation URLs. The following results were obtained by removing the URL starting withcast:fromcommon.js. - Reconnecting to a presentation has not been implemented yet on Firefox for Android.
- Executing Presentation API often causes a corrupted screen
- Calling Presentation API on Firefox Nightly throws
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: TIMEOUT
- A value of presentation availability does not change from true to false even when .
- CD65: FAIL
- The presentation connection in
connectingstate cannot be closed.
- The presentation connection in
- FA59: FAIL
- Reconnecting to a presentation has not been implemented yet and stops this test.
- CD65: PASS
- However, the error "Failed to cast. Please try again." often occurs several seconds after the test ends
- FA59: PASS
- CD65: PASS
- FA59: FAIL
- Messages received from a receiving UA are often passed to a controlling UA as a concatenated single message
- Binary messages cannot be received
- CD65: FAIL
- The presentation connection in
connectingstate cannot be terminated.
- The presentation connection in
- FA59: FAIL
- The presentation connection in
connectingstate cannot be terminated. - Terminating a connection in
closedstate does not work properly. - Closing a presentation connection in a nested browsing context due to termination of the presentation cannot be tested since reconnecting to a presentation is not implemented.
- The presentation connection in
- CD65: PASS
- FA59: FAIL
- Messages sent from a controlling UA are often passed to a receiving UA as a concatenated single message
- Sending a message in
closedstate does not work properly.
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA65: FAIL
- Constructing a presentation request with a URL starting with
http:does not throw an error (but callingstartreturns a Promise rejected withSecurityError).
- Constructing a presentation request with a URL starting with
- CD65: PASS
- FA65: FAIL
- Constructing a presentation request with URLs including one or more
http:does not throw an error (but callingstartreturns a Promise rejected withSecurityError).
- Constructing a presentation request with URLs including one or more
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: FAIL
allow-presentationinsandboxattribute of an iframe element does not work.
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: (not supported)
- CD65: FAIL
- Although the Promise from a previous call of
getAvailabilityhas been settled, the next call ofgetAvailabilityreturns the same Promise.
- Although the Promise from a previous call of
- FA59: FAIL
- Although the Promise from a previous call of
getAvailabilityhas not been settled yet, the next call ofgetAvailabilitydoes not return the same Promise.
- Although the Promise from a previous call of
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
- CD65: FAIL
- When a presentation connection is in
connectingstate, a call ofPresentationRequest.reconnectreturns a Promise rejected withNotFoundError, instead of a Promise resolved with the presentation connection - A call of
PresentationConnection.terminateafter reconnecting fires acloseevent instead of aterminateevent
- When a presentation connection is in
- FA59: FAIL
- Reconnecting to a presentation has not been implemented yet.
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: FAIL
- The presentation can start without a user gesture
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: PASS
