Bug 167012

Summary: Can't fullscreen element if parent element is already fullscreen
Product: WebKit Reporter: Aloke Desai <alokedesai>
Component: PlatformAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: fred.wang, jer.noble, rwlbuis, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 10   
Hardware: Mac   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 276855    
Attachments:
Description Flags
Simple repro case
none
testcase none

Aloke Desai
Reported 2017-01-13 11:35:22 PST
Created attachment 298774 [details] Simple repro case If a document's body is fullscreen, a child iFrame can't go fullscreen (even though it has the correct allowfullscreen/webkitallowfullscreen attributes). This seems to contradict the WHATWG fullscreen API as any descendant element should be able to go fullscreen if a parent element is already fullscreen. This is works as intended in both Chrome and Firefox.
Attachments
Simple repro case (2.13 KB, application/zip)
2017-01-13 11:35 PST, Aloke Desai 		no flags
Details
testcase (728 bytes, text/html)
2026-10-12 07:38 PDT, Frédéric Wang Nélar 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2017-01-13 11:37:04 PST
<rdar://problem/30017129>
Frédéric Wang Nélar
Comment 2 2018-05-23 07:39:55 PDT
I can confirm the issue with the repro case. The parent element remains fullscreen when we try to fullscreen the child. However, I don't see any fullscreenerror message.
Frédéric Wang Nélar
Comment 3 2026-10-12 07:38:45 PDT
Created attachment 481767 [details] testcase Original repro case in a single HTML page + removing webkit prefix.
Frédéric Wang Nélar
Comment 4 2026-10-12 07:45:12 PDT
I've uploaded attachment 481767 [details] as single HTML page and also using the standard names (no webkit prefix) ; firefox/chrome allows the child to go fullscreen when the parent is fullscreen but safari does not. I'm not yet sure where it's specified and whether we have WPT tests for that.
Note You need to log in before you can comment on or make changes to this bug.