[Webkit-unassigned] [Bug 266235] New: iOS 17.2 Fullscreen API - Iframe doesn't take parent document viewport when sent fullscreen

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 11 10:35:07 PST 2023


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

            Bug ID: 266235
           Summary: iOS 17.2 Fullscreen API - Iframe doesn't take parent
                    document viewport when sent fullscreen
           Product: WebKit
           Version: Safari 17
          Hardware: iPhone / iPad
                OS: iOS 17
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: DOM
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: robert.bryer at bbc.co.uk

Created attachment 468979

  --> https://bugs.webkit.org/attachment.cgi?id=468979&action=review

Video player with tiny controls

When our player sends the iframe fullscreen, we see that the viewport is scaled very small. The parent page has a <meta name="viewport"...>, but these attributes of the parent aren't applying to the iframe. The controls of the player are therefore tiny when in fullscreen.

The parent document has:
<meta name="viewport" content="width=device-width, initial-scale=1.0">

iPhone 13 / iOS 17.2
With the Fullscreen API feature flag turned on:
1. Visit http://cookbook.tools.bbc.co.uk/news?player=smphtml5 and play.
2. In portrait, go fullscreen.
3. See the controls of the video player are scaled really tiny.



We can fix this problem by duplicating the meta tag and adding it to the iframe's document's <head>, and this will fix the scaling. However we haven't needed to do this for any other fullscreen API implementation so I think (and correct me if I'm wrong) that the iframe should instead be taking these viewport attributes from its parent.

Extra:
4. Add a meta tag to the iframe by running in the console:
> $('#smphtml5iframemp')[0].contentWindow.document.head.appendChild($('<meta name="viewport" content="width=device-width, initial-scale=1.0">')[0])

-- 
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/20231211/33e0df06/attachment.htm>


More information about the webkit-unassigned mailing list