The bitter truth

What I wasn’t able to accomplish

Due to Chrome’s very restrictive API, there are things that will not be implemented as promised. Things such as:

• Holding modifier key freezing the queue (instead, I resorted to using timeouts)
• Indication of what will be the tab switched

Not all hope is lost!

Having said the limitations of Chrome’s API, I was able to fulfill these things:

• Unlimited tab queue (or at least enough for any normal usage, I haven’t pushed the extension to the limits of RAM usage)
• Intuitive usage (timeout seems appropriate, and the extension works)
• Clean and modern development flow

What’s left to implement before moving to provisioning?

Before I start coding the Python applet that would provision this extension, I want to also solve these problems:

• Implement restoring tab order upon closing and reopening the browser
• Adding any newly added tab to the top of the queue
• Fiddle around with timings to find what’s the best for intuitive usage that doesn’t get in the way