api.Element.requestFullscreen — WKWebView support differs from Safari data
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
It's weird a WebView would provide different support than Safari proper:
What browsers does this problem apply to, if applicable?
Safari
What did you expect to see?
Maybe notes that support needs to be configured (as the native/consumer side needs to handle extra things if it declares support) — but not difference in actual platform feature support?
Did you test this? If so, how?
iPad mini 26.2 running Chrome iOS (a WKWebView consumer), using this: https://jsfiddle.net/ecy9zv8s
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
I'm having trouble finding any documentation to corroborate the current Safari vs. WebView difference in bcd data for this — hence why I'm raising this. Might have just missed something obvious, though.
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API
MDN metadata
MDN page report details
- Query:
api.Element.requestFullscreen - Report started: 2026-05-11T21:43:23.218Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the api.Element.requestFullscreen compatibility entry and the MDN Fullscreen API page, then reproduce the reported behavior using the linked JSFiddle on Safari and a WKWebView consumer. Confirm whether the Safari and WebView distinction reflects actual platform support or consumer configuration, and update the compatibility data only when reliable documentation or test results establish the correct values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100