How can the browser auto-refresh not be considered a bug?

Question

I have been browsing these forums and I have seen this issue over and over again being discussed and the answer is always "that's not a bug, that's how it works, you can't change or disable it."
Here is the problem. In ios 7, when you are using Safari (or any other browser, I have found), if you exit the browser to do almost anything: your phone rings, you open the camera and take a picture - anything at all - when you return to the browser, the current page will almost always reload itself. Anything you have done on that page, any comment written, any checkboxes checked - everything - will be lost.
This is an important issue for me, because I have written a web application that I use every single day for work. My web application is a 560k page of pure html/javascript (no third party or plugin content at all, I wrote it all by hand) with about another 80k worth of graphics (buttons). You load the page and javascript functions move you from div to div, with different sets of checkboxes in each div (there are some 87 such divs in the page). At the end of this process, you click a button to finish your checklist, which will save it to a database and you're done. Unfortunately, this process would never get to the end because of the page constantly refreshing.
So I rewrote the page to save via ajax at each major section (there are 8 major sections). Dividing it up this way meant that all of your work is never lost and that you only have to go back and redo at most one section. When I rewrote it this way and I was still using ios 6, it was only a minor annoyance. I might have to redo a section once or twice a week because of a page refresh.  Ever since the upgrade to ios 7 however, it has become a pain again, because now the page refreshes almost every single time. The problem is that while doing this checklist, I have no choice but to go to the camera to take pictures documenting what I am checking boxes about. This switch to the camera and back again almost always forces a page refresh.
It strains credibility to think that a 640k web page has to be cleared out every time you do anything. I have only this page open in the browser, nothing else going on, nothing else loaded, all apps closed - and still, the browser will be force refreshed every time I do anything. The iphone 4s has 512M of memory, so my page occupies 640k of 524288k, or .001% of the available memory. Do you really have to refresh this thing every single time I sneeze?
How can this not be considered a bug, clearing out everything that can be cleared out regardless of what impact it might have on the user experience?
And finally, can anyone at all suggest any kind of a workaround? People have been complaining about this since at least 2008. I'm at my wits end, its making my web app nearly unusable.

Answer 1

OK...after better keyword choices I did find that the 'change location' solution does work, but only if the calendar is first shared with the world, and then has its location changed:
  http://www.radbrooksolutions.co.uk/rs/Blog/Entries/2011/5/3_MobileMe_Calendar_Up date_and_PHP_iCalendar.html
Does anyone know if information in public calendars can be found in nefarious ways (like by Google)?
FWIW, I did try sharing privately to just myself, so that I could then subscribe to the calendar on the serving machine and push it out as a .ics file...but I cannot share a calendar with myself. Boooo.