Open Bug 1456816 Opened 6 years ago Updated 2 years ago

On restart, reset pinned tabs to original URL

Categories

(Firefox :: Session Restore, enhancement, P5)

Product:
Firefox
Component:
Session Restore
Version:
59 Branch
Type:
enhancement

Tracking

()

People

(Reporter: amp68, Unassigned, NeedInfo)

References

(Blocks 2 open bugs)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180323154952

Steps to reproduce:

Pinned Gmail.com.  While in Gmail.com, switched to another website using the URL bar or bookmarks.


Actual results:

The pinned tab is now directed to the new site and if you exit the browser, your pinned tab is no longer gmail.


Expected results:

What I would like to happen, is to have a pinned tab protected from redirection.  In a perfect world, pinned tabs would:

1. Disable to URL barwhile in the tab, or changes in the URL bar would open a new tab
2. Disable bookmarks while in the tab, or picking a bookmark would open it in a new tab
3. Closing and opening the browser would "reset" the tab back to the default site when it was pinned.  For example you go to www.reddit.com and then click on a link that takes you to www.reddit.com/r/firefox.  When you exit the browser and go back in, the pinned tab should reset to www.reddit.com.

If this breaks the expected functionality of pinned tabs, perhaps a new kind of tab called an "App Tab."
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
20180424220100

(In reply to Andy Pastuszak from comment #0)
> 1. Disable to URL barwhile in the tab, or changes in the URL bar would open a new tab

Bug 607266
https://addons.mozilla.org/firefox/addon/new-tab-from-location-bar/

> 2. Disable bookmarks while in the tab, or picking a bookmark would open it in a new tab

Bug 579872. The latter has been the case since Firefox 4. I checked by opening a bookmark from the Bookmarks toolbar button and it still works.

> 3. Closing and opening the browser would "reset" the tab back to the default site when it was pinned.

As far as I can find, this request hasn't been made before. Changing summary accordingly.
Blocks: 579874
Severity: normal → enhancement
Component: Untriaged → Session Restore
OS: Unspecified → All
Hardware: Unspecified → All
Summary: PInned tabs should be protected from URL changes → On restart, reset pinned tabs to original URL
Can understand the need for this, I also tream pinned tabs as 'installed' and find it annoying when they get navigated away, I do think a PWA type install is probably the best fix for this but will put on the session restore feature backlog in case its a change UX want to make
Blocks: ss-feature
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5

+1 On this one,

(In reply to Andy Pastuszak from comment #0)

  1. Disable to URL barwhile in the tab, or changes in the URL bar would open
    a new tab
    Solved in newer versions of FF, go to about:config and modify "browser.urlbar.openintab" to true.
    However would still prefer to disable the URL-bar while in a pinned tab. Then it would feel much more like a true web-app!
  1. Closing and opening the browser would "reset" the tab back to the default
    site when it was pinned. For example you go to www.reddit.com and then
    click on a link that takes you to www.reddit.com/r/firefox. When you exit
    the browser and go back in, the pinned tab should reset to www.reddit.com.

This one is key! Sometimes pressing a link within a pinned tab makes it go astray. A new FF window should revert it back as requested.

If this breaks the expected functionality of pinned tabs, perhaps a new kind
of tab called an "App Tab."

Also agreed, if this breaks the intent of whatever was envisioned as a use case for "Pinned Tab" in the FF team, there should definitely be a App Tab. This is how we use the web today.... Especially in work-related situation where web-based email and calendar apps should be accessible allt he time.

Wondering about a status update on this one!

Flags: needinfo?(mdeboer)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.