That is what I thought. Expected, but is it required? If so, maybe we can do something smarter here. The buildbot is one example but any page that meta-refreshes would suffer from the same problem. I can imagine than anyone with a status-monitoring page of some sort would want this. We should check the error code of course to distinguish between a temporary error and a permanent error.
- Itai On Jul 30, 2:40 pm, Eric Roman <[email protected]> wrote: > That is the expected behavior. > > To work around, one could instead wrap the buildbot page in an iframe, > and refresh the iframe's contents from a timer in the outer page. > > > > On Thu, Jul 30, 2009 at 8:57 AM, Itai<[email protected]> wrote: > > > Is it required that meta-refreshes stop when it refreshes to an error > > page? > > > The buildbot pages here suffer from this problem where once-in-a-while > > we get an error page and > > when that happens, it stops refreshing so the status does not come > > back up. > > > Could we keep refreshing if we get a temporary error page (depending > > on the status)? > > > - Itai --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
