Loading Profile...
iPhone version does not handle history/back button properly
when browsing around the iPhone version of the site, you can use the buttons provided in the UI to navigate back to the parent folder.
Using the back button on Safari however does not work
Using the back button on Safari however does not work
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
The best solution from the company
-
That is a fantastic and valid point, MMcCubbing (and Mike as well!) I should have phrased my response better.
You are absolutely right the back button in Safari should take a user back to the previous page. This is exactly what anyone would expect to happen.
The reason why we added the new button was because making the "back" button work in Safari was somewhat difficult for us to make work properly. As we continue to work on improving the iPhone web application, it makes sense for us to figure out how to make "back" work as well.
As you mentioned earlier, it probably doesn't make sense for this post to be marked as "not a problem". So, I am changing it to better fit the current situation. Thank you for your comments!
I’m happy
The company says
this solves the problem
-
Inappropriate?Hello, Mike. I'm not sure exactly what the problem is. The intended use is to use the UI to navigate from a folder to a mailbox, then to a message and back again. You should not be using the back button on the browser to navigate within the iPhone web application.
-
Inappropriate?Hi
that's exactly what the problem is: if I navigate to a folder, then to a message, I would expect the back button to take me back to the folder.
It's a common issue with Ajax applications, they need to be programmed to handle the back button properly, see http://code.google.com/p/dshistory/ for example.
Using the site UI to navigate back means the user needs to learn something else rather than use the concepts he is used to (to do the exact same thing). -
Inappropriate?Thanks for sending me the link, Mike. We'll take a look at it.
Feel free to keep sending in your suggestions. I really appreciate it!
I’m happy
-
Inappropriate?Why is this marked not a problem? I haven't checked if it is still an issue or not, seeing as I can't get on the site on my iPod Touch (that is being dealt with in another thread), but breaking browser functionality and expected flow certainly is an issue. Has this been fixed?2 Comments Add a comment
This solves the problem
-
This was marked "not a problem" because by design, it was intended for users to use the buttons on the "webpage" (and not in mobile Safari) to navigate OIB on the iPhone.
In other words, if you tap a mailbox, then a message, you should tap the button to go back to the mailbox and not tap "back" in the browser.
If you think this should work another way, feel free to submit an idea post here with your suggestion. We certainly believe that the iPhone web application/website could use some enhancements, so any feedback or suggestions you may have would be greatly appreciated! -
But that design exactly is the problem, no page should override basic browser functionality. Especially without explanation or warning in the UI. People expect the browser controls to work regardless and not allowing them to do so provides a counter-intuitive experience for users.
-
Inappropriate?That is a fantastic and valid point, MMcCubbing (and Mike as well!) I should have phrased my response better.
You are absolutely right the back button in Safari should take a user back to the previous page. This is exactly what anyone would expect to happen.
The reason why we added the new button was because making the "back" button work in Safari was somewhat difficult for us to make work properly. As we continue to work on improving the iPhone web application, it makes sense for us to figure out how to make "back" work as well.
As you mentioned earlier, it probably doesn't make sense for this post to be marked as "not a problem". So, I am changing it to better fit the current situation. Thank you for your comments!
I’m happy
The company says
this solves the problem
EMPLOYEE
