Bug 193078
| Summary: | WKWebView ignores Element.webkitRequestFullscreen. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ram <quadrupleslap> |
| Component: | WebKit API | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Enhancement | CC: | ajuma, beidson, bfulgham, herr.ernst, jer.noble, jespertheend, karl+webkit, quadrupleslap, simon.fraser, thorton, webkit-bug-importer |
| Priority: | P2 | Keywords: | BrowserCompat, InRadar |
| Version: | Safari 12 | ||
| Hardware: | Mac | ||
| OS: | macOS 10.14 | ||
Ram
If this actually hasn't been implemented, I like how Edge does it, where the web view has a `ContainsFullscreenElement` property and a `ContainsFullscreenElementChanged` event, and a fullscreen element doesn't do anything other than fill the web view.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jer Noble
Brady and I were talking about this earlier; the current fullscreen implementation for Safari will rip the WKWebView out of its view hierarchy. Fullscreen isn't enabled by default because that's super problematic for third party clients who may not expect such behavior. One alternative may be to require clients to implement a set of WKWebView fullscreen delegate methods, and have the client worry about getting their WKWebView into some kind of "full screen" presentation state.
karl
This creates a webcompat issue.
https://github.com/webcompat/web-bugs/issues/68762
Radar WebKit Bug Importer
<rdar://problem/122586538>