After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735050 - Pinned Tabs like in Firefox
Pinned Tabs like in Firefox
Product: epiphany
Classification: Core
Component: Tabs
Other All
: Normal enhancement
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks: 755388
Reported: 2014-08-19 12:44 UTC by Torben Andresen
Modified: 2018-08-03 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Torben Andresen 2014-08-19 12:44:11 UTC

i have some Tabs which are always open. In Firefox you can Pin those Tabs[1]. Please add this Feature to Epiphany.

Comment 1 Yosef Or Boczko 2014-08-19 14:32:49 UTC
I wants to work on this.
Comment 2 Yosef Or Boczko 2014-08-19 15:12:24 UTC
I see only one problem with the way to implement this with the GTK+'s API:
When there is overflow tabs, and the Pin tab in the start of the tabs, when you
switch to the last tab (in the end of the tabs), the first tab will be hide because
of the overflow.

In firefox, I see the Pin tab always shown, also when there is an overflow.
Comment 3 Reinout van Schouwen 2014-08-20 06:21:22 UTC
I doubt there is a need to further complicate the tabs UI. Why not use the Save as webapp feature instead?
Comment 4 Yosef Or Boczko 2014-08-20 12:06:42 UTC
Because you can't put more than one window app in the same window...
Comment 5 Torben Andresen 2014-08-21 06:47:40 UTC
The benefit of the pinned Tabs is that i can use the tab bar like always with the nice addition that i have my everyday used sites always open in smal Tab Icons. If it is not possible to do this with GTK, then i can live with it. It's not an Killer Feature but one that i will be missing a bit.
Comment 6 Reinout van Schouwen 2014-08-22 13:39:15 UTC
(In reply to comment #4)
> Because you can't put more than one window app in the same window...

Obviously you can't! That's the whole point, to keep that specific site open at all times regardless of whatever else you're doing in your browser. You just need to flick back and forth using Gnome Shell instead of the browser tabs UI. This may not be what you're used to from Firefox but it fits quite well in the "Gnome Shell philosophy".
Comment 7 Cosimo Cecchi 2015-12-11 18:52:08 UTC
FWIW Chrome has both pinned tabs and web apps, and I use both at the same time. Pinned tabs have a different use case, e.g. I might want to keep one to a bugzilla list of issues for a project I often work on, but that is not really a web app.
Comment 8 Derek 2016-04-18 18:08:40 UTC
Pinned tabs are great. There are tabs that you want to be single instance in the web browser (think messengers). Still there are issues to decide about pinned tabs behavior:

1. What's the behavior when opening a new tab with the same address?
  - OS X's Safari goes to the pinned tab (singleton tab)
  - Chrome and Firefox opens a new tab with the same content

2. What's the behavior of multiple windows?
  - OS X's share pinned tabs (and the web view, so no double loading)
  - Chrome and Firefox opens a new window without the pinned tabs

3. What's the behavior of session restore?
  - OS X's reopens and reloads the pinned tabs on demand
  - Chrome and Firefox reopens and reloads the pinned tabs on demand

I like some of the OS X's singleton tabs, so if I mistakenly open, for example,, it jumps to the already open tab, but I don't like the idea of sharing the pinned tabs through windows (although the web view sharing thing is technically awesome).

A good UX approach to implement inside Epiphany is to merge the singleton tab (item 1) with other items. This would make Epiphany take the better of both worlds.
Comment 9 GNOME Infrastructure Team 2018-08-03 20:21:59 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: