18470 2012-08-02 16:00:23 +0000 Step 4.1 shoudn't be limited to top level browsing contexts; nested browsing contexts can also change their window.name and behave in just the same way. 2012-12-30 04:33:34 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#history-traversal P3 normal Unsorted 1 contributor ian ian james mike contributor oldest_to_newest 71768 0 contributor 2012-08-02 16:00:23 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#history-traversal Complete: http://www.whatwg.org/c#history-traversal Comment: Step 4.1 shoudn't be limited to top level browsing contexts; nested browsing contexts can also change their window.name and behave in just the same way. Posted from: 2001:4c28:a030:30:8d3:d182:a0e2:4a0d User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.11.310 Version/12.50 75621 1 ian 2012-10-08 20:11:30 +0000 That was added somewhere between r1000 and r2000. 75630 2 ian 2012-10-08 21:20:11 +0000 Make that r861. No explanation in the log comment as to why this excludes iframes or window.open() windows... 80706 3 ian 2012-12-30 04:32:35 +0000 It's the name clearing that has to be top-level only. Iframes don't clear their names automatically. 80707 4 contributor 2012-12-30 04:33:34 +0000 Checked in as WHATWG revision r7613. Check-in comment: Seems iframes' names must also be remebered across session history traversals. http://html5.org/tools/web-apps-tracker?from=7612&to=7613