Open Bug 1415136 Opened 7 years ago Updated 2 years ago

The 'back' button shouldn't be enabled when I opened a tab and typed a URL

Categories

(Core :: DOM: Navigation, defect, P2)

defect

Tracking

()

Tracking Status
firefox58 --- affected

People

(Reporter: florian, Unassigned)

References

Details

I think this is a recent behavior change (that I'm tempted to call a regression).

Steps to reproduce:
1. Press cmd+t
2. Type a url (with the help of the awesomebar completion)
3. press enter to load it.

Actual result:
The 'back' button is enabled, and clicking it sends me to about:newtab

Expected result:
The 'back' button should be disabled, as I've never used the about:newtab page to get there.


Note: it makes sense to enable going back to about:newtab when the user loaded the current page by clicking on a tile in about:newtab, but in the case above where I interacted only with the keyboard and the awesomebar I haven't even noticed the stuff in the about:newtab page, so having it in the history is surprising/confusing.
Blocks: 776167
Component: Tabbed Browser → Document Navigation
Product: Firefox → Core
Priority: -- → P2
Just submitted what turned out to be a duplicate:
https://bugzilla.mozilla.org/show_bug.cgi?id=1448577

and i agree it's very annoying >:(

  - delt.
Maybe a pref to about:config will satisfy those that have adjusted to this method of browsing
I don't think this needs a pref, as there's already a Home button which by default also goes to activity stream.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.