257631 2023-06-01 20:52:38 -0700 ::isFullscreen() and ::fullscreenElement() can lead to confusion 2025-02-07 11:09:09 -0800 1 1 1 Unclassified WebKit WebKit Misc. Other Unspecified Unspecified RESOLVED DUPLICATE 268232 InRadar P2 Normal --- 276855 1 marcosc marcosc ntim webkit-bug-importer oldest_to_newest 1959475 0 marcosc 2023-06-01 20:52:38 -0700 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). 1960700 1 webkit-bug-importer 2023-06-08 20:53:16 -0700 <rdar://problem/110505689> 2092893 2 ntim 2025-02-07 11:09:09 -0800 *** This bug has been marked as a duplicate of bug 268232 ***