New Features in Consideration -- Feedback Welcome!

[rkodey]

Hey - if you're passionate about any of these features, leave a comment. I can't promise I'll add everything, because I really want to keep this extension simple and focused. But, discussions are welcome and can definitely influence future features!

Better visuals for Suspended tabs

In progress!

• ✅ Add icons to the tab title
• 🔳 Allow custom / any unicode characters in title prefix
• ✅ Add favicon dimming
• 🔳 Add favicon overlay, perhaps a choice from a few options

Better options for Suspended pages

In progress!

• ✅ Add option for full-page click to restore
• ✅ Add option to restore a suspended page when it's reloaded
• 🔳 Give more control for default suspend visual behavior
• 🔳 Give easy way to filter, select, and update suspend visual behavior pages in bulk

Prevent Discard / Suspend for pages with FORM data

This one scares me a little, to be honest...

• It appears existing extensions inject a content script into every page the browser visits. That's creepy from a privacy / trust point of view.
• If you have alternate ideas on how to implement this, I'm all ears!
• 🔳 I think this might require extension permission to be https://*
• 🔳 Original request, plus 2 votes in less than a day!
  • +1 +2

below "the line" ™

Session Export / Import / Backup / Restore

Not likely to be implemented.
Why: There are plenty of other extensions built of for this that have much better features.

• I use Tab Session Manager
• I've seen others using Session Buddy

Firefox port

Not likely to be implemented.
Firefox is my main browser, where I have 400+ tabs open at any time. But... it seems to not need an extension to manage memory efficiently. But still... could be interesting to look at sometime.

[ossilator]

i don't mind having a place to randomly dump ideas into, but using this to actually track deferred work (which you clearly hinted at in several requests you closed) is a horrible idea from a project management perspective.

[rkodey]

Really? Outside of public open source, I've found it quite helpful to be open about the reasons some features might not move forward. It encourages discussion of ideas that maybe I haven't considered.

All the users hung out to dry using The Marvellous Suspender want feature parity... but there's no way I can do that quickly. So, I was thinking this might be a way to collect requests and prioritize -- including those I might not work on.

You're right I don't really need these listed in both places, but my theory on listing features here is that most people wouldn't bother to read the closed issues. Better to have everything in 1 spot, I'm thinking?

[rkodey]

...just saw your comments in the closed issue. Thanks!
Updating the summary above to match.

[ossilator]

i don't mind this being kinda an index page (you clearly are already doing that to a degree). traditionally, a wiki page might be used for that, but i guess these are largely equivalent.

however, there is no need to solve that problem this way in the first place: you can add labels to the issues, and just put a query here (or maybe better in the readme, because that's much more likely to be found by users).