Releases: Lemonsavery/openUrlsWhenLoaded
Releases · Lemonsavery/openUrlsWhenLoaded
2.7
Changes
- Add maximum open tabs setting. It suspends opening when maximum tabs is reached for the window, and resumes when the number of tabs goes below the maximum again.
- The following is a common use case:
You want to open 300 tabs, but you need to interact with some/all of them. You don't want to have 300 open tabs while interacting with each one, so you use this feature to have only 5 or 10 open at once. As you close no-longer-needed tabs, new ones will open. - This feature will likely make the Pause Button feature less necessary, which should be less annoying for certain workflows.
- This feature interacts intuitively with the other features in the tool, especially the "Open tabs in same window as tool" feature.
- Adding this feature required rewriting several key parts of this tool. If you find a bug, please let me know. I've opened one Issue for a bug that existed prior to this release. I've taken some measures against the bug in this release, but never truly understood it, so it's possible it's still around.
- The following is a common use case:
- Add dialog popup prompting user for a Google Chrome Store review and feature suggestions.
- Occurs after every 4th successful list opening.
- Includes an option to never show the popup again.
2.6
Changes
- Make the text area autofocus.
2.5
2.4
Changes
- Add ability to change background color.
2.3
2.2
Changes
- Stop some minor UI flickering when tool page first loads.
- Add reviewer suggestion based setting: once a tab is loaded, close it. This is suggested by the same reviewer as in the 2.1 release.
2.1
Changes
- Clarify mutual exclusivity interaction between incognito setting and same-window setting. This means the incognito setting won't be disabled, but these two settings will each turn off the other when checked.
- Add reviewer suggestion based setting: once all tabs have been loaded fully, close them all.
Initial Formal Release
The extension was public before version 2.0, but did not have settings to customize extension behavior, and was missing polish. All changes made to the repository after #20 are not in production on the Chrome Web Store.
For unsupported Chromebooks
this is not yet tested
While I have not tested this, it may be possible to use this extension on old Chromebooks with old versions of Chrome.
- Download the source code from this release's assets, and unzip them to their own folder.
- Replace the
manifest.json
file in that folder with the one included separately in this release. - Go to your Chrome Menu > More Tools > Extensions, turn on Developer Mode.
- Click Load Unpacked in top left, and choose the folder you just created.
- An unpacked extension has been added to your extensions, and should be able to run just like any other extension, but is independent from the Chrome Web Store.
If this extension does not use features dependent on Manifest Version 2, then this should work 🤞. I'll update/replace this release with updated information when I have it.
02/16/22 - Extension seems disabled in Chrome v48, even when using manifest 2. Tested on Windows 10 64bit, using Windows 64bit Chrome version downloaded from here.