Last modified: 2014-02-12 23:53:46 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 T38848, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36848 - Browser back button works poorly with expanded article sections
Browser back button works poorly with expanded article sections
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Nobody - You can work on this!
:
: 36867 36980 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-14 21:50 UTC by Tomasz Finc
Modified: 2014-02-12 23:53 UTC (History)
12 users (show)

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


Attachments

Description Tomasz Finc 2012-05-14 21:50:55 UTC
Tapping the back button after you've expanded articles sections will cycle you through expanded sections first and then to a previous article. It should go to the previous article first.
Comment 1 Jon 2012-05-15 10:40:44 UTC
I've been wrestling with what the right thing to do with the hash is.

In the current situation it actually gives a good way to jump up the article. Although we have a jump back a section link at the bottom of each section I actually use the browser back button to jump back up the article to previous sections on my Android). I agree though this becomes less useful in bigger articles

It is also useful to be able to share a page with a hash as I can share the page with a current section open (e.g. not the default closed section that needs to be toggled open).

Several solutions
1) Keep existing behaviour
2) We can use the history api to replaceState so that only the last hash is maintained. On clicking back you return to the last page.
3) We set an initial hash and then replace all further hashes. One back button press thus takes you to the top of the page. Two back button presses to the last page

Is there some way we could user test the best way to deal with this?
Comment 2 Phil Chang 2012-05-15 17:46:46 UTC
Related bug at 36867, possibly a duplicate.

I guess what happens is that with one section open, there is no movement up to a previous section. So it looks like nothing has happened. Then if the same section is opened and closed multiple times (or that is attempted), several presses of Back do nothing.

This was a problem when the section reveal was slow or buggy. 

My vote is for option 3 above, because in that case something useful and visible occurs with each Back press.
Comment 3 Jon 2012-05-15 17:48:39 UTC
This is not entirely true. On my Android clicking back does move back to the previous section. So I guess that is device specific...
Comment 4 Jon 2012-05-16 08:51:12 UTC
*** Bug 36867 has been marked as a duplicate of this bug. ***
Comment 5 Jon 2012-05-20 10:52:02 UTC
*** Bug 36980 has been marked as a duplicate of this bug. ***
Comment 6 Jon 2012-05-21 09:40:32 UTC
Resolved in https://gerrit.wikimedia.org/r/8311
It now replaces the hash
Comment 7 Jon 2012-07-11 19:44:55 UTC
Feedback from the site has suggested not everyone is happy with this.
A different opinion "Can you please fix your app so that when you are on a page and visit another page, hitting the back arrow will take you back to the previous section you were in? As it is now, hitting the back arrow takes you back to the beginning of the previous page and you lose your spot, which is really annoying if you were in the middle of a long article."

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


Navigation
Links