- From: <bugzilla@jessica.w3.org>
- Date: Fri, 24 Jun 2011 20:56:27 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12775
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |Simetrical+w3cbug@gmail.com
Resolution| |NEEDSINFO
--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-06-24 20:56:27 UTC ---
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: Additional Information Needed
Change Description: no spec change
Rationale: The proposed solution only works if the parent page and the iframe
are cooperating closely. If that's the case, why don't you just have an
onbeforeunload handler on all the pages in the iframe that alters the URL bar
using pushState()? Alternatively, why don't you just not use frames at all
here, and include everything in the same page? You have to explain your
use-case better.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 24 June 2011 20:56:29 UTC