Lusito
commented
4 years ago Confirming the startup cleanup manually would mean, that I'd have to create a list of what things to clean. In the meantime new cookies, etc. might have been stored, making it confusing for the user what will actually be deleted. Not sure if this is the best approach to what you want to do. Startup cleanup works best when it happens as soon as possible.
Maybe what you want is rather a "ignore startup cleanup for the next startup" or something. But that can be achieved right now by just disabling startup and re-enabling it when done. This is of course a bit more work.
If notification actions appear, it might be possible to make an optional confirm notification popup, which just asks "do you want to perform startup cleanup?", but I highly doubt many users would use this, as it would get annoying quickly.
About the other part of this request.. to be able to select what you want to clean up. I guess this could be done with a separate action.. like click on "detailed manual cleanup" (or whatever) and getting a new browser-tab, which lists things you could clean up. This list could be huge though.
Feel free to add more thoughts. I'm not decided on this one yet. Don't expect something anytime soon though, since Version 3 is currently taking most of my time.
ghost
Currently, when FMN does an auto cleanup when starting the browser, it pops up a notification that goes away in 4 seconds, making it difficult to actually read anything more than a line or two. This makes the notification fairly useless other than to say "yup, FMN just did its thing". This short timeout is a function of FF, and is here to stay unless this bug/enhancement is resolved.
What I would really like is an option to have a confirmation dialog that pops up with a list of domains it wants to clean and you can either confirm or cancel the deletions. This allows for two things:
It is unclear to me if this can be accomplished with a window popup or if it has to be done through the notification subsystem in the Mozilla Gecko toolkit. If the only way to do this is through the notification subsystem, then this feature is blocked by [no]notification actions and this enhancement will have to wait until notification actions are baked in. Since Google Chrome supports notification actions, it is highly likely that FF will get them eventually since Chrome parity seems to be a driver on a lot of this sort of thing.