18840 2012-09-11 22:59:14 +0000 Fullscreen changes 2012-12-05 05:27:15 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED FIXED P2 blocker Unsorted 16709 1 ian ian annevk contributor eoconnor ian mike Pat_Ladd2 contributor oldest_to_newest 73640 0 ian 2012-09-11 22:59:14 +0000 (This is forked from bug 17838 because that one was becoming a mess.) Here's my plan: 1. In "Creating a new Document object" (where I apply CSP) I'll set the "fullscreen enabled flag" on a Document if it is in a top-level browsing context or if it is nested through an <iframe> that has allowfullscreen and the <iframe>'s Document has the flag set also. 2. In the <iframe> section, I'll add the new allowfullscreen="" attribute. (Also in the index.) 3. I'll add the onfullscreenchange and onfullscreenerror event handlers. 4. As the first substep of step 4 of "traverse the history", I will invoke "fully exit fullscreen". (Note that the event fired there will be seen when you come back to the doc, e.g. fullscreen, back, autoexit fullscreen, forward, get event.) 5. I'll add the terms above (fullscreen enabled flag, fully exit fullscreen) to the dependency section, linking to http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html Did I miss anything? 73642 1 ian 2012-09-11 22:59:24 +0000 *** Bug 17838 has been marked as a duplicate of this bug. *** 73677 2 annevk 2012-09-12 06:50:58 +0000 Sounds good. 73963 3 contributor 2012-09-15 18:30:06 +0000 Checked in as WHATWG revision r7351. Check-in comment: (This should have no normative effect.) Prepare the spec for fullscreen. http://html5.org/tools/web-apps-tracker?from=7350&to=7351 73964 4 ian 2012-09-15 18:59:41 +0000 I forgot about sandboxed popups. New plan: 0. I'll create a new "sandboxed fullscreen flag" for sandboxing flag sets, which is set on sandboxed iframes when "allowfullscreen" isn't set. 1. In "Creating a new Document object" (after I apply CSP) I'll set the "fullscreen enabled flag" on a Document if it is in a top-level browsing context whose "sandboxed fullscreen flag" is not set, or if it is nested through an <iframe> that has allowfullscreen and the <iframe>'s Document has the "fullscreen enabled flag" set. 2. In the <iframe> section, I'll add the new allowfullscreen="" attribute. (Also in the index.) 3. I'll add the onfullscreenchange and onfullscreenerror event handlers. 4. As the first substep of step 4 of "traverse the history", I will invoke "fully exit fullscreen". (Note that the event fired there will be seen when you come back to the doc, e.g. fullscreen, back, autoexit fullscreen, forward, get event.) 5. I'll add the terms above (fullscreen enabled flag, fully exit fullscreen) to the dependency section, linking to http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html 78555 5 Pat_Ladd2 2012-11-20 22:06:11 +0000 Are the steps proposed in the 9/11/12 post going to be added soon? 79458 6 contributor 2012-12-05 05:16:58 +0000 Checked in as WHATWG revision r7564. Check-in comment: Fullscreen integration. http://html5.org/tools/web-apps-tracker?from=7563&to=7564