881425 - The hardcoded back button misbehaves on articles

Status: RESOLVED INCOMPLETE

(support.mozilla.org :: Mobile, task)

Description

[Ibai Garcia [:ibai]]

Whenever an article is accessed from mobile, after having navigated from support.mozilla.org the back button (not the one on the browser but the one of the site) has a bug.

Actual behavior:
1- Navigate to support.mozilla.org
2- Click on a product
3- Click on a topic 
4- Click on an article
5- Click on the back button
6- This click brings you to Learn the Basics, regardless of the topic that you were before.

Expected behavior:
1- Navigate to support.mozilla.org
2- Click on a product
3- Click on a topic 
4- Click on an article
5- Click on the back button
6- You land in the topic that you selected in step 3.

This is an important thing to fix before the launch.

Comment 1

[Ricky Rosario [:rrosario, :r1cky]]

Should be easy enough to fix. Putting in next sprint.

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

We'll revisit this once we are done with the IA changes and determine what makes sense. For now we will remove the button in bug 881906.

Comment 3

[Kadir Topal [:atopal]]

The back button on the top is a common metaphor for "one level up" on iOS and Firefox OS. Since we moved to a strict hierarchy we should be able to pull this off on the topic/subtopic and articles pages, right? The current work around works on topic and subtopic pages, but is uncommon and takes precious vertical space.

Putting into next sprint, tentatively.

Comment 4

[Ibai Garcia [:ibai]]

Kadir, the metaphor works great when it's an standalone app. When viewed in the context of a web browser it looks like a duplication back button next to each other.

In addition, articles can still belong to multiple topics/subtopics...so I'm not sure if we are in a position for a good solution at the article level.

It requires some thinking.

Comment 5

[Ricky Rosario [:rrosario, :r1cky]]

(In reply to Ibai Garcia [:ibai] from comment #4)
> It requires some thinking.

Based on that, moving to backlog.

Comment 6

[Ricky Rosario [:rrosario, :r1cky]]

Q3 is over... => Q4

Comment 7

[Ricky Rosario [:rrosario, :r1cky]]

Moving 2013Q4 bugs to the Future since we didnt care enough about them in 2014Q1.

Comment 8

[Andrew Truong [:feer56] [:andrewtruong] [:atruong]]

unable to reproduce. closing.