[Webkit-unassigned] [Bug 244155] disablePictureInPicture still renders the pip button

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 22 14:02:00 PDT 2022


https://bugs.webkit.org/show_bug.cgi?id=244155

--- Comment #8 from Jer Noble <jer.noble at apple.com> ---
(In reply to Adrian Florescu from comment #7)
> Also, how come this is marked as supported here:
> https://developer.mozilla.org/en-US/docs/Web/API/HTMLVideoElement/
> disablePictureInPicture and 
> 
> and here:
> https://caniuse.com/?search=disablePictureInPicture

The Picture-in-Picture specification says that User Agents "MUST reflect the content attribute of [disablePictureInPicture]", and WebKit does. It then says, when the disablePictureInPicture attribute is present, User Agents "SHOULD NOT play the video element in Picture-in-Picture".

"MUST" and "SHOULD" are defined in terms of RFC 2119 <https://www.ietf.org/rfc/rfc2119.txt>. 

WebKit supports setting the disablePictureInPicture attribute, and it reflects that attribute to a DOM property of the same name. Therefore we meet the first requirement of the specification. That's why you see that property listed as "supported" in caniuse.com and MDN.

Actually disabling picture-in-picture is not mandatory; the use of the word "SHOULD" rather than "MUST" is intentional. A User Agent does not actually need to block picture-in-picture to be compatible with the specification.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220822/d789ced1/attachment.htm>


More information about the webkit-unassigned mailing list