Hello, I apologize for the delayed response to this question.

At this time, the best way to accomplish this is to create two containers - one for each google docs account - and then use the "Set Default URL" feature, which will allow you to click the container and it will immediately open the URL that you wanted to bookmark.

This method will require you to open the Containers Helper popup and then click on the container in the popup's container list. You can do this via the default keyboard shortcut alt+shift+D (cmd+shift+D on Mac) and start typing to filter on your container's name, then press the Enter key to open the top search result. This will be just as fast as clicking on a bookmark, once you get used to it.

I hope this helps. Have a great day. If you have further questions, visit https://codeberg.org/firefox-containers-helper/firefox-containers-helper and create an issue, I will respond there.

Hi Korwin,
My apologies for the lack of translation. I don't generally have much time to devote to the extension, but I can put it on the roadmap, maybe someone in the open source community is willing to help!

edit: Also I'll try and implement it myself if I have time, of course : )

Hey Davide, thanks for the review. I've encountered this as well, I've created a GitHub issue for it and will try and tackle it in the near future when I have some time. I hope you're still enjoying the extension.

Ok, your review is fair. This one is my fault. In all my time developing this extension, I never thought to type in a URL without "http://" or "https://" at the beginning, so I never ran into this problem. That's the reason this happened to you, and I feel bad that this was your experience with my addon.

I wanted to be sure the issue was resolved in a user-friendly way before responding to your review. I have published an updated version of this web extension (v0.0.19) just a moment ago. This new version will now ask if you actually want to save or open a container URL that doesn't start with http:// or https://. If URLs don't start with a recognized protocol, then Firefox will attempt to open it as a file or local resource, which is what you saw : (

If you're still interested in trying this addon, please feel free to reinstall it and try it again, you just need to add https:// to the front of your URL and it will work as expected : )


I hope you'll give the extension another try. It really will make a difference!

You're welcome! I totally understand where you're coming from. I turned off container sync because it caused a lot of headaches for me as well. I'm glad this extension helped you out so much : )

I'm glad it helped!

I have found my extension to be very useful for that Temporary Containers bug as well. Hundreds of tmp containers, now made easily removable : ) Glad to help out!

Thank you @RJHaines! Much appreciated, I'm happy to have helped with your work!

Thank you for taking the time to write a review for my addon. I hope you've been enjoying it and finding it useful in your daily browsing. It would indeed be nice if Mozilla could do a security check, for the sake of visibility - until then, a simple review of the code, which is all contained in one JS file (src/context.js), would quickly reveal that this addon is not capable of performing any malicious actions. I hope discerning users would be willing to take the extra 5-10 minutes to skim through the code if they have concerns : )