Last modified: 2012-02-24 02:52:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T34998, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32998 - Android back button troubles (history vs bookmarks?)
Android back button troubles (history vs bookmarks?)
Status: RESOLVED FIXED
Product: Wikipedia App
Classification: Unclassified
Generic (Other open bugs)
1.0.0 (Android)
All All
: Normal critical
: ---
Assigned To: Brion Vibber
:
Depends on:
Blocks: 31447
  Show dependency treegraph
 
Reported: 2011-12-12 19:43 UTC by Brion Vibber
Modified: 2012-02-24 02:52 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: Android
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2011-12-12 19:43:37 UTC
There are some oddities with bookmarks & history possibly interfering with the back button behavior.
Comment 1 Yuvi Panda 2011-12-13 14:38:49 UTC
Can you explain/expand a bit more?
Comment 2 Phil Chang 2011-12-14 00:25:34 UTC
If I saved a page, then hit back, the prior page would appear in skeleton form - apparently without CSS or images. The app was frozen at that point and it was hard to do anything other than search - menu and back stopped working, not sure if home was broken. Possibly home would work and the app could be re-open in the same frozen state.
Comment 3 Tomasz Finc 2011-12-15 02:18:45 UTC
I'm seeing the same thing happen when I load the app. Hit the back button (which goes back to the home screen). Then i tap the icon for the app and see just the search input box and nothing else. The menu key doesn't work and the only thing i can do is search.
Comment 4 Brion Vibber 2011-12-16 18:26:01 UTC
This should be fixed in current builds.

Skeleton form was from using plain window.history.go(-1) with the way we cached pages; just wasn't safe.

Blank-page-and-no-menu was from engaging the cached webview mode too early, causing things to not get initialized properly in PhoneGap.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links