15054 2011-12-04 02:53:27 +0000 New Feature Suggestion: This is a completely new and unheard problem. Today I was developing a new page with a music player on it. However, when you click on a link and another page loads, the player resets and starts the song all over again. Is it possib 2013-03-01 19:37:05 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor eoconnor annevk eoconnor ian mike philipj plh public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 public-html-bugzilla oldest_to_newest 60904 0 contributor 2011-12-04 02:53:27 +0000 Specification: http://www.w3.org/TR/2011/WD-html5-20110525/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: New Feature Suggestion: This is a completely new and unheard problem. Today I was developing a new page with a music player on it. However, when you click on a link and another page loads, the player resets and starts the song all over again. Is it possible to set some portions of my page as "fixed" - and those portions even survive page loads? There are always components that we would prefer to stay static on the page rather than disappear and reload every time. A chat box. A music player. There is currently no neat way of doing this. rowan.rishi@gmail.com Posted from: 60.52.100.82 User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 60920 1 silviapfeiffer1 2011-12-04 23:51:40 +0000 You can use a cookie or even local storage to store such state. I've previously considered that media fragment URIs [1] could be used in browsers for storing page history for pages that contain media content. However, it's just as easy to store these URIs in a cookie or local storage. [1] http://www.w3.org/TR/media-frags/ 60933 2 philipj 2011-12-05 10:24:49 +0000 If we're talking about history navigation, Opera already saves the state of media elements and tries to bring them back to that exact state when you go back in history. (This is necessary because the script environment state is also kept, which would otherwise be out of sync with the media element state.) 60934 3 annevk 2011-12-05 10:30:00 +0000 I think what rowan.rishi@gmail.com meant is that a site has a widget embedded on several pages and that as you transition between those pages the widget should not be interrupted in what it is doing. Currently the solution here is that you rewrite the way navigation works using history.pushState() and XMLHttpRequest rather than actual page loads. But maybe we can have something simpler? 61143 4 ian 2011-12-07 22:57:02 +0000 We could explore having an iframe that survive session history traversal / navigation, such that a single Document is grafted into an iframe on any subsequent page that has a slot for it, or something... 81239 5 robin 2013-01-11 13:41:51 +0000 The idea is interesting, but the security model is scary. 81734 6 robin 2013-01-21 15:59:44 +0000 Mass move to "HTML WG" 81852 7 robin 2013-01-21 16:02:29 +0000 Mass move to "HTML WG" 83879 8 eoconnor 2013-03-01 19:36:29 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change. Rationale: I doubt the security concerns are outweighed by the benefit of such a feature.