Bug 257631
| Summary: | ::isFullscreen() and ::fullscreenElement() can lead to confusion | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Marcos Caceres <marcosc> |
| Component: | WebKit Misc. | Assignee: | Marcos Caceres <marcosc> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ntim, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 276855 | ||
Marcos Caceres
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).
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/110505689>
Tim Nguyen (:ntim)
*** This bug has been marked as a duplicate of bug 268232 ***