-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically re-enable Isolation after a delay #315
Labels
Comments
Would be nice to have indeed. |
I'll dive into it as soon as I feel more confident with the code! A lot of JS habits to (re-)discover… 😅 |
Cool! Let me know if I can be of any help :) |
stoically
changed the title
New option to automatically re-enable Isolation after a delay
Automatically re-enable Isolation after a delay
Nov 9, 2019
rkodey
added a commit
to rkodey/temporary-containers
that referenced
this issue
Jun 21, 2020
Add handler logic in isolation.ts Add a new function setIsolation, to consolidate some overlapping code Replace code in commands.ts with setIsolation function Update addIsolationInactiveBadge in browseraction.ts to accept an optional counter
rkodey
added a commit
to rkodey/temporary-containers
that referenced
this issue
Jun 28, 2020
Adds isolation helpers setActiveState and handleActiveState to consolidate isolation toggle code Consolidates pageaction.showOrHide into isolation.handleActiveState Renames members in isolation.ts with a common root autoEnable* Adds isolation local storage so the auto re-isolation can resume if Firefox closed Adds tests for isolation active, auto re-isolation, and the toggle_isolation keyboardShortcut
rkodey
added a commit
to rkodey/temporary-containers
that referenced
this issue
Jun 28, 2020
Renames autoEnable naming prefix to automaticReactivate to better associate with main "active" var Removes unneeded comments and debug code
rkodey
added a commit
to rkodey/temporary-containers
that referenced
this issue
Jun 28, 2020
Removes placeholder comments
rkodey
added a commit
to rkodey/temporary-containers
that referenced
this issue
Jun 29, 2020
Updates isolation tests to avoid internal method calls Clarifies background test descriptions
stoically
pushed a commit
that referenced
this issue
Jun 29, 2020
* feat: automatic re-isolation after n seconds (#315) Add handler logic in isolation.ts Add a new function setIsolation, to consolidate some overlapping code Replace code in commands.ts with setIsolation function Update addIsolationInactiveBadge in browseraction.ts to accept an optional counter Adds isolation helpers setActiveState and handleActiveState to consolidate isolation toggle code Consolidates pageaction.showOrHide into isolation.handleActiveState Renames members in isolation.ts with a common root autoEnable* Adds isolation local storage so the auto re-isolation can resume if Firefox closed Adds tests for isolation active, auto re-isolation, and the toggle_isolation keyboardShortcut Renames autoEnable naming prefix to automaticReactivate to better associate with main "active" var Removes unneeded comments and debug code Removes placeholder comments Updates isolation tests to avoid internal method calls Clarifies background test descriptions
rkodey
added a commit
to rkodey/temporary-containers
that referenced
this issue
Jul 5, 2020
Centralize isolation state management and storage access Add isolation helper functions getActiveState, toggleActiveState Retire unneeded helper function handleActiveState Initialize isolation before browseraction Related to stoically#315 Closes stoically#433
Published v1.9beta2 with the feature, thanks @rkodey! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you use this add-on, this is to have Isolation enabled most of the time. When one disables Isolation, this is to prevent the add-on to create a new temporary for a given action…
So it would be nice to be able to define in the options a delay after which the Isolation is enabled again.
Or maybe, a count: “Ignore the next N navigation actions” (with N=1 for most users). But I think this is less intuitive than a 5s delay (for example). Especially when there are a couple of redirections after login in to a site…
The text was updated successfully, but these errors were encountered: