Developers would surely appreciate some kind of developer mode. Safari makes it nearly impossible to remove an appcache. Refreshing, emptying the cache nor resetting the browser helps in this. MobileSafari behaves about the same -- something like a notice with a force refresh option its developer mode would make debugging a lot easier. I'm not exactly sure what Firefox's behaviour is, but I remember it was somewhat better than Safari.
The best way to develop using appcache seems to be by using uncachable references (e.g. timestamped) to every file in the appcache, which is quite tiresome. I'd suggest a 'force reload' option for the first implementation. A UI to show appcaches in some later stage would greatly easy debugging: appcaches are a 'black box' in current implementations. The only way to check that a browser is not reloading is by checking server logs, and even then you still can't be completely sure if it's regular browser caching or an appcache. On Wed, Jun 17, 2009 at 10:11 PM, Michael Nordman<micha...@chromium.org> wrote: > Chromium has no behavior whatsoever yet... the feature is utterly > unimplemented thus far... but it will have identical behavior to > safari, iphone, andriod by virtue of the same code base performing > those behaviors... thats the plan at least, and I'm working on the > code now. > > Gears (i'm partly guilty of that) users have similar issues with the > gears system. Developing for 'offline' butts heads ( <verb> <noun>, > not buttheads :O) with standard operating procedures for web > development (put new stuff on server, hit reload, repeat as needed). > > I can think of at least some things that may help? > > * if the user-agent had a debugging level feature (in some debug/tools > menu) to blow away the current appcache. would that help? Or perhaps a > UI to show appcaches and a option to 'remove' one? > > The former could be provided without any spec changes and agreement > amoungst browser vendors. We're not far enough along with this > feature in chrome to be too concerned with UI yet... but I'll write > this down in my design doc. > > > On Wed, Jun 17, 2009 at 5:14 AM, Mark Janssen<praseo...@gmail.com> wrote: >> Hi Michael, >> >> It's been some time (I rarely read this address), but why I was asking >> is because I'm testing a web application for iPhone/Android. Safari >> does care about appcache manifest, but does so a bit too well: it's >> nearly impossible get it to reload a new version from the server (thus >> ignoring the appcache manifest). As you can imagine this is quite >> cumbersome during development, so I was wondering of Chromium has the >> same behaviour. >> >> Regards, >> Mark >> >> On Mon, Jun 1, 2009 at 11:54 PM, Michael Nordman<micha...@google.com> wrote: >>> Hi, I'm assuming you and praseodym in #chromium IRC are one and the >>> same... if not, sorry for the spam. >>> >>> Yes, we do. >>> >>> At this point, there is no support for the feature in chromium, but >>> we're working towards that. The implementation in webcore has to be >>> refactored so that chromium can use it too... or chromium has to >>> implement this feature outside of webcore... we're pursuing the first >>> option at this time. >>> >>> https://bugs.webkit.org/show_bug.cgi?id=25436 >>> >>> Why do you ask? >>> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
