

- FIREFOX PROFILE MANAGER ONLY OPENS ONCE PDF
- FIREFOX PROFILE MANAGER ONLY OPENS ONCE FULL
- FIREFOX PROFILE MANAGER ONLY OPENS ONCE CODE
I find that the PDF reading application, like Foxit, Acrobat or others, generally provide me much more control over how the document is presented in turn making it much easier for me to read.

Personally I hate having PDFs open within the browser. This one falls into the “surprisingly complex to answer” category.
FIREFOX PROFILE MANAGER ONLY OPENS ONCE FULL
My refactoring has mostly linearized the flow between the files but decoupling SweetAlert is still a task I'm not looking forward to.There are forums full of almost any question you can think of, easily answered or not.

I made a booboo in using SweetAlert and how I set it up.
FIREFOX PROFILE MANAGER ONLY OPENS ONCE CODE
Either of these will require more tweaking with how this code is implemented. I haven't gotten to the last suggestion you had where one could set a timer to auto save sessions or have some kind of recovery mechanism if/when Firefox crashes. I hope you've played with the selective load option to resolve your issue of loading a session causing all the tabs to load at once. Per your suggestion, I added in the number of tabs in a session to the session list item fields. I have more or less refactored my code and am relatively happy with how it's structured. When I re-write this plugin to clean things up these will likely get implemented along with the auto saving functionality.Īs for having the presence of mind to recover a crashed session, that is somewhat a challenge to implement and from a plugin standpoint probably harder yet. In the context you are thinking of I see there being an actual underlying "session" that is being maintained. Though, this can be quasi worked around by selectively opening tabs. I do like the idea of having the option to not load all the tabs at once. Thank you for the review and suggestions! As a side note, thank you for using my add-on! I hope my changes have helped make the interface more user friendly! =] I mistook the label as implying something was inherently wrong with my add-on but that is not the case. Basically, they want users to be aware that add-ons are powerful and they don't fully vet but a few that are very popular. I've come to realize that this is a non-Recommended extension because Firefox wants users to use extensions that have been fully vetted. Though, it might take time? I'm not sure but will keep looking into getting that part fixed. I believe the plugin should no longer say it's not recommended as well. I have removed SweetAlerts library and have attempted to make the UI simpler to use. There are a few design patterns used that were questionable and may be getting flagged. Basically, it has to do with SweetAlerts which is at the core of the interface. =/I think I know why but it will take some effort. Hello, thank you for your review! I'm very grateful for your feedback and would like to know how I can improve the interface? Additionally, you said it's on the "non-Recommended extensions" list? I am looking into remediating this as soon as possible and was unaware till now that this is the case. Less code, a slightly more guarded user, and a lot of misery saved all around both from coding and user usage. In addition, it REDUCES the number of clicks the user has to do when they know they really want to nuke and not ponder as I don't prompt them. This setup allows me to NOT have to write a prompt screen for that destructive action and NOT have to write settings logic to fetch or persist each time. The default choice is on average what most want (Maybe really just me. That is to say, there are no prompts about "are you sure you want to do this" because you know you do- you checked the boxes accordingly. I reduce the number of clicks for such an action at the added bonus of a user being fully cognizant of their choice. Having them reset is to insure you don't lose a session simply by forgetting that you had the "Replace Current Tabs" checked and "Selective Open" unchecked. I'm not sure I understand by "to be a part of the settings"? Do you mean that you wish the selection you chose last would persist after closing? If so, I understand your reasoning but, I disagree and wont likely implement it.
