W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2010

[Bug 11458] New: mechanism needed to control refresh url for ajax applications

From: <bugzilla@jessica.w3.org>
Date: Thu, 02 Dec 2010 21:42:01 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-11458-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11458

           Summary: mechanism needed to control refresh url for ajax
                    applications
           Product: HTML.next
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
        AssignedTo: dave.null@w3.org
        ReportedBy: dennisa@pachou.biz
         QAContact: public-html-bugzilla@w3.org
                CC: plh@w3.org, mike@w3.org


Often a web application will change states as the user works with it. If the
user were to do a "refresh" in the browser, the state is generally lost unless
the underlying javascript and/or server do a lot of work to keep track of this.
The simplest method for doing this would be to tell the browser that if a
refresh is done, it should go to a specific url other than the original.
Obviously this could have big security implications so it would be reasonable
to restrict the url to the current domain or even the current page (use '#' or
'?' to get the server and javascript to get the correct state back).

-- 
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 Thursday, 2 December 2010 21:42:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:35 UTC