- This topic has 22 replies, 5 voices, and was last updated 11 years, 1 month ago by
.
-
Posts
-
I believe the back button issue is related to use of appcache from ios7 homescreen webapps – at least I have replicated it only when using appcache. Your mileage will vary with ios7 and we can only work from our big list of issues. There are workarounds emerging but they will get you only so far. Also I’m cautious about personal inferences as they frequently are biased to a specific context which is not factored into the “my xyz app works” reports.
<rant>
I have spent so much time dick’n with ios7 safari issue over the past 6 weeks my head wants to explode – it was not ready for release. Internally I called out ios7 as at best beta-ware for html5 developers.From Sencha http://www.sencha.com/blog/the-html5-scorecard-the-good-the-bad-and-the-ugly-in-ios7/
“…Although there are some impressive performance gains in SVG and JavaScript, the sheer number of bugs and broken features, clearly mark this release as a beta. While nowhere as bad as the Android 3 browser — our all time champ of broken web releases — we recommend that organizations standardized on HTML5 development hold off upgrading until an iOS update fixes these issues..”
</rant>We have a temporary work-around: its called the GOOGLE CHROME BROWSER for iPad and iPhone, which has the back functions working perfectly.
The problem, to us anyway, is in the Safari Browser and the “swipe” thing – which we get to work now and then using that browser, but as fast as it appears to work, it fails just as fast.
Apple MUST fix that bug, among a jillion other with ios7.
They are almost getting as bad as Microsoft releasing buggy software.
Yes things work well under Chrome.
But there are 2 problems
– you cannot save the app to the homescreen (thanks Apple)
So you have to open Chrome, select bookmarks and then the app.– Google doesn’t honor the fullscreen directive in the html file
Otherwise ok.
We are noticing that if the cache is cleared before the Home Screen button for the web app is pushed, the “back” buttons seem to work, and so do the swipe gestures.
The back and gestures do work when in airplane (no wi-fi) mode.
If we could get around the need to clear the cache before viewing the app, it would be OK.
The whole basis of our app is that the user can view it without a wi-fi available, re: a power blackout in a region or something along those lines.
Of course, if the back thingy gets fixed somehow, it would be great.
QUESTION: Why does the javascript back coding not work as an over-ride for the app? It would seem that the web app would control its own actions some way be providing history-back functions.
Any “try this” suggestions would be welcome.
P.S. We could hard code the “back” button but there are some 360 screens in the app. Hate to go through all that if there is a code fix forthcoming.
Oh great! Apple’s arrogance in its shining moment.
Don’t suppose MobiONE has any kind of work around, other than “removing” the back button feature completely, yes? No?
We can hard-code a “back” button but it sure is easier this way.
FYI. If the cache is cleared, before loading a web app, the back buttons work.
But not under any other situation.
