- From: Jim Barnett <1jhbarnett@gmail.com>
- Date: Mon, 02 Jun 2014 17:14:08 -0400
- To: Martin Thomson <martin.thomson@gmail.com>
- CC: Eric Rescorla <ekr@rtfm.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
I don't follow your thought. We have said that it is possible to grant a site permanent permissions so that it is free to use a certain device whenever you visit it (HTTPS only, of course). Those permissions survive a page reload, don't they? All I'm asking for is a form of permissions that survive a page reload, but don't last forever. If permanent permissions are possible (and presumably don't involve massively disruptive architectural changes), why aren't less permanent ones also possible? Just a bit of book-keeping in the UA, I would think. On 6/2/2014 4:45 PM, Martin Thomson wrote: > On 2 June 2014 13:37, Jim Barnett <1jhbarnett@gmail.com> wrote: >> Requiring HTTPS is fine, but I don't want to grant permanent permissions to >> the site (i.e. permissions that will apply if I revisit the site in a >> month). I do want the permissions to survive a page reload. Can't we >> make this distinction? I don't think that "past the next page reload" >> should imply "until England wins the World Cup." > Harald's proposal wouldn't have survived a reload. The expectation > associated with reload is reset, which implies loss of permissions. > > I'm guessing, but I think that the sort of thing you are looking to do > requires use of the history API and some massively disruptive > architectural changes: http://html5demos.com/history -- Jim Barnett Genesys
Received on Monday, 2 June 2014 21:14:45 UTC