1231284 - save panorama PLEASE!

Status: RESOLVED WONTFIX

(Firefox Graveyard :: Panorama, defect)

Description

[helkav]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

used tab groups / panorama a LOT


Actual results:

it was great. please please please don't take it away. I think the bookmarks alternative suggested will be a bit of a pfaff


Expected results:

perhaps it could be left and enabled with switch in about:config ? I can't imagine it needs to be continually updated along with newer versions of FF

Comment 1

[YF (Yang)]

See the https://support.mozilla.org/en-US/kb/tab-groups-removal, I guess it solve your question.

Comment 2

[helkav]

(In reply to YF (Yang) from comment #1)
> See the https://support.mozilla.org/en-US/kb/tab-groups-removal, I guess it
> solve your question.

I've been through the alternatives suggested and they're really not the same thing
I see bookmarks as a more permanent storing of pages/sites
having an add-on instead of in the core product seems like a step backward : I really don't fancy losing tab groups, hopefully enough other people will feel the same

Comment 3

[YF (Yang)]

You've tried https://addons.mozilla.org/en-US/firefox/addon/tab-groups-panorama/? I think it is almost the same.

Although this feature is an innovative and works normally, but its prospects are not good, it is unlikely to be back.

Comment 4

[helkav]

if at all possible I would rather it not be an addon , quite often they become obsolete as FF gets updated to new versions

Comment 5

[YF (Yang)]

This is bound to happen because officials don't intend to continue to maintain it, due to higher costs and lower usage.

In short, it should be WONTFIX I think.

Comment 6

[Patrick Westerhoff]

(In reply to helkav from comment #4)
> quite often they become obsolete as FF gets updated to new versions

And that’s exactly the reason why it was removed from Firefox in the first place. Those that were responsible of keeping it updated no longer wanted to do that. It’s absolutely in their hands to decide what to continue working on and what not (since they are the ones that invest the time). Now, with the feature being in an extension (which works very well btw.), it’s just that someone else is responsible for that. In general, this should be a good sign since now there is dedicated investment on that one feature. And you’re always welcome to support the development by either contributing yourself or supporting the developer directly (see http://fasezero.com/addons/).

Comment 7

[Andreas Eibach]

to comment 6:

Great and very neutral explanation.
Just curious though why such simple and to-the-point explanation doesn't appear anywhere in the support article that YF linked in comment 1.
Mind you, by the general public, this behavior is usually called a 'stick-in-the-mud', or even, 'chicken-heartedness'.

Comment 8

[helkav]

I don't know enough about the ins and outs of this to argue strongly from a technical POV but I seem to remember reading somewhere, sometime about each FF addon increasing the resources used (which are generally considerable I think, for me averaging, 403mb)

I can possibly get rid of some existing addons I don't rxactly need

just wondering if this is something to be allowed for anytime a core piece of functionality is being converted to an addon?

I realise the ship has already sailed on this one and hopefully the addon won't be the last straw that breaks the camel's back, resource-wise!

if tab groups the addon does the trick defo donate