242930 2022-07-19 19:56:20 -0700 Make webkit*Fullscreen properties as an alias of standard fullscreen ones 2022-10-13 11:39:14 -0700 1 1 1 Unclassified WebKit WebCore Misc. Safari Technology Preview Unspecified Unspecified RESOLVED DUPLICATE 158125 BrowserCompat, InRadar P2 Normal --- 1 karlcow webkit-unassigned han.guokai webkit-bug-importer oldest_to_newest 1885280 0 karlcow 2022-07-19 19:56:20 -0700 Currently WebKit is the only rendering engine using the prefixed property for fullScreen: window.document.webkitFullscreenElement the standard property is implemented on Gecko and Blink. See https://developer.mozilla.org/en-US/docs/Web/API/Document/fullscreenElement#browser_compatibility It is probably time to add aliases * fullscreenElement <- webkitFullscreenElement. * requestFullscreen <- webkitRequestFullscreen * exitFullscreen <- webkitExitFullscreen it is common to see code such as ``` { key: "isFullscreen", value: function() { return window.document.fullscreenElement || window.document.webkitFullscreenElement || window.document.mozFullScreenElement || window.document.msFullscreenElement } } ``` This can't be fully removed because of probable webcompat breakage. worse it encourages code like this. (if you read this, do not do that) ``` const isFullScreenCapable = document.fullscreenElement || document.webkitFullScreenElement; const isWebkit = document.webkitFullScreenElement; if (isFullScreenCapable) { if (isWebkit) { document.webkitExitFullscreen(); } else { document.exitFullscreen(); } } if (isWebkit) { canvas.webkitRequestFullscreen(); } else { canvas.requestFullscreen(); } ``` and allow for fingerprinting. 1885281 1 webkit-bug-importer 2022-07-19 19:57:23 -0700 <rdar://problem/97296290> 1885341 2 gsnedders 2022-07-20 05:34:31 -0700 *** This bug has been marked as a duplicate of bug 158125 ***