3 ms·
The back and home buttons are not overloaded with other meaning based on context. Surely you jest. The back button has seen significant overhaul in the time si
by DHowett 10y ago
The back and home buttons are not overloaded with other meaning based on context.
Surely you jest. The back button has seen significant overhaul in the time since it was introduced; it changed from activity-to-activity navigation along the single "back stack" to a confusing, circuitous path walk between applications, their "up" stacks, their "back" stacks, and everything else under the sun. It's difficult to determine when it will take you to the previous activity or to a page you haven't seen in the days since you last launched the application you just ended up on.
If you're in a browser, the back hardware key takes you back -- until it determines that you've reached a navigation root (which might not be the earliest page in the chain), and it pops you back to the previous application or the home screen. Perhaps it closes the tab?
If the keyboard is up, it dismisses it -- unless you're in an autocorrect action (* on certain phones). Maybe it opens the keyboard, too, because it took you back to a previously focused field.
It's far from "not overloaded with other meaning based on context". It is, in fact, "entirely overloaded with other meaning; much of which is based solely on context."
- galacticpony 10y agoIt may be confusing, but that confusing "back behavior" is the one behavior it has, even if it has changed over time. It is not overloaded. It doesn't start deleting characters depending on where your last tap may have (accidentally) been. Well, maybe some app does that, but I hope you get my point.
- DonHopkins 10y agoOne feature Android's back button is NOT overloaded with yet is deleting the character before the cursor, and let's keep it that way, please.