This document describes the results in Presentation API receiving 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
With regard to FA59, see also: https://gist.github.com/tomoyukilabs/90563f4d08b54b5f278fd414fb56ecba#overall
- CD65: PASS
- FA59: PASS
- CD65: PASS
- FA59: FAIL
- A change of the number of presentation connections cannot be tested since reconnecting to a presentation has not been implemented yet.
Note that the test had a bug, and then a PR to fix it was submitted and merged: web-platform-tests/wpt#9009
- CD65: FAIL
- Even when a nested browsing context of a controlling UA that has a presentation connection is discarded, its corresponding presentation connection in a receiving UA is not closed
- FA59: FAIL
- Reconnecting to a presentation has not been implemented yet and stops this test.
- 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: 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
closed
state cannot be checked properly.
- CD65: PASS
- However, the error "Failed to cast. Please try again." often occurs several seconds after the test ends
- FA59: FAIL
- Terminating a presentation connection by a receiving UA does not work properly
- CD65: FAIL
- Navigation and closing a window at a receiving UA terminates the receiving browsing context regardless of sandboxed top-level navigation browsing context flag
- The state of each permission,
geolocation
,notifications
,push
,midi
,camera
,microphone
,speaker
andbackground-sync
is set togranted
orprompt
in the top-level and nested browsing contexts of the receiving UA navigator.presentation.receiver
is not set tonull
in the nested context of the receiving UA
- FA59: FAIL
- Navigation at a receiving UA terminates the receiving browsing context regardless of sandboxed top-level navigation browsing context flag
- Calling
window.alert
,window.confirm
, orwindow.prompt
blocks a receiving UA. - (Note that a receiving UA does not have
window.print
.) - Cookies, local storage, indexedDB, service workers, cache storages, window clients in a controlling UA are accessible to top-level and nested browsing contexts of a receiving UA.