[Webkit-unassigned] [Bug 257631] New: ::isFullscreen() and ::fullscreenElement() can lead to confusion

[bugzilla-daemon at webkit.org]

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

            Bug ID: 257631
           Summary: ::isFullscreen() and ::fullscreenElement() can lead to
                    confusion
           Product: WebKit
           Version: Other
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: marcosc at apple.com

For legacy reasons, we had an old web expose "webkitIsFullscreen()", which got changed to `isFullscreen()` and `::fullscreenElement()`, which is the recommended/standard way of checking for the fullscreen element... however, having two methods is confusing because they are subtly different in behavior. 

We should just have a single API, preferably the one that matches the standard (i.e., use ::fullscreenElement() everywhere and get rid of the old one that we don't need anymore).

-- 
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/20230602/cae8ac21/attachment.htm>