- From: Tobie Langel <tobie@fb.com>
- Date: Wed, 10 Oct 2012 09:41:04 +0000
- To: Andrew Betts <andrew.betts@ft.com>, Michael Nordman <michaeln@google.com>
- CC: Patrick Gillespie <patorjk@gmail.com>, Jake Archibald <jaffathecake@gmail.com>, Chris Wilson <cwilso@google.com>, "public-fixing-appcache@w3.org" <public-fixing-appcache@w3.org>
On 10/10/12 10:18 AM, "Andrew Betts" <andrew.betts@ft.com> wrote: >> ... but that mechanism does not currently apply to cross-origin 3xx >>redirect responses. Cross-origin 3xx redirects should always trigger the >>fallback behavior. >> >> This was added to chrome to support a use case where an error response >>was expected while online in the context of Google Docs. An attempt to >>do something with a 'doc' that had been deleted or whose permissions had >>changed such that the current user had no access would result in an >>error response that should be shown to the user. The default fallback >>behavior was getting in the way of that. >> >> This half-measure with the extra header got us out of a bind, but it's >>not very satisfying as a general solution. > >How do you deal with this use case in browsers other than Chrome? I'm >wondering if there an adequate workaround for developers who don't have >the luxury of being able to patch the browser, or whether this should be >considered a failing of appcache for which there is currently no adequate >remedy. This need to be captured in a use case and requirements. Will be delivering a canvas in which to get this work started shortly (now that I have a bit more time on my hands). --tobie
Received on Wednesday, 10 October 2012 09:41:37 UTC