Mark Foltz

Thanks. I am going to revert the SVG changes and submit them separately, as the SVG needs to be updated to reflect the updated PR.

If the test API is strictly about testing the `RemotePlayback` interface, it could be very simple: `.remote.test.deviceAvailable = true` to simulate a remote playback device being available for that element,...

We do need to be able to test a failure to connect to a remote playback device (step 4 of "Establishing a Connection.") As far as testing the behavior of...

We've made a change to the OSP to make it compatible with this scenario, but it would be a new feature as far as the Remote Playback API is concerned....

Sorry didn't intend to close, just defer.

See additional discussion of how remote playbacks could be reconnected in the two openscreen issues above. Any protocol updates can be proposed after we determine what the requirements are from...

- There are other spec errors for undefined terms (`browsing context`, etc.) that will prevent merging the PR. - While the change itself is fine, the following sentence doesn't apply...

Merged #154 to fix the xrefs to HTML.

At first glance, it would be reasonable for the browser to support video remote playback while in PiP, or choose to exit PiP during remote playback, depending on form factor...

I confirmed with https://googlechrome.github.io/samples/picture-in-picture/, that in Chrome 127.0.6533.122 on Windows you can successfully initiate and stop remote playback while in PiP, and successfully enter and exit PiP while in remote...