- From: Google <sysbot+gh@w3.org>
- Date: Mon, 15 May 2017 20:11:30 +0000
- To: public-secondscreen@w3.org
> That way if the page doesn't do anything to resize the remotely played element, it won't break because the UA suddenly changed the size of the video to say full HD. I guess while remoting the tradeoff is between: * Freezing and `videoWidth` and `videoHeight` and breaking some content (and the spec) when the intrinsic dimensions of the video don't match * Not freezing them and breaking some content when these are changed by the UA by remote playback I feel like the latter is less risky: if the media is offered in multiple resolutions, then the page should expect video dimensions to change and the layout should have constraints set to accommodate. But, I don't have concrete evidence to support that claim. > We should advise the UAs to suspend the local playback except for the parts that are needed for remote playback implementation to work If we do that, then the third bullet you propose is off the table? Or is it possible, but you'd advise against it? -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/46#issuecomment-301590477 using your GitHub account
Received on Monday, 15 May 2017 20:11:36 UTC