Hide "install extension"

What's Changed

• ASPIRE-2759: Add CSS to hide install extension banner by @rsinger in #15

Full Changelog: 0.3.10...0.3.11

Allow users to manually specify a tenancy using short-code and region.

This release corrects an issue that was introduced in 0.3.7 where users could no longer manually enter a tenant short code if their institution did not appear in the drop down list. Now when selecting "Other" users must specify both a short code and a region.

Convert activeTenant from string to Object

The 0.3.7 release saves the active tenant in local storage as an object. However, in previous releases this was a simple string that contained the tenant shortcode. This release modifies the behavior of the extension so that it detects if the activeTenant was previously stored as a string and converts it to the new object that is needed.

Switch between bookmarking endpoints based on the Tenants region.

This release ensures the extension will select the appropriate bookmarking endpoint for a customer based on their region.

Bug fixes

More reports of requiring multiple clicks to do anything.

Traced down to the executeScript, which wasn't ready to be called, but was called immediately. The 2nd time the user would click, the previous one was ready, so worked.

Changed the sendMessage to only happen once the executeScript was successful.

Bug fixes

We've had reports of the extension intermittently requiring multiple clicks to do anything. This release hopefully resolves that. The issue being that, by it being intermittent, it is not clear if it's solved, or it just hasn't happened yet.

Bugfix to prevent need for multiple icon clicks

This release is intended to address an issue where, in some circumstances, on certain web pages, multiple clicks of the bookmarking button were required before the bookmarker would activate.

We think it's due to the fact that the action was processing synchronously and getting lost in the DOM rendering of pages (both naturally and via AJAX after the original HTML renders) and this should release address that.

Restrict requested permissions for extension

In the effort to include MS Edge support, we were being too lax in the permissions we were requiring to use (effectively, <all_urls> in the format Edge understood: *://*/*), but we don't actually need that for Firefox or Chrome.

In the course of this release, it also became clear that we didn't the content_scripts part of the manifest at all, which was also causing a security warning (that was release 0.3.2 - unfortunately, we can't see what Firefox is going to report unless the extension is installed from their Addons site).

We now only request permission to read from https://talis-public.talis.com/*. which is where we get the data to populate the dropdown in the options screen.

This change should be backwards compatible with (old) MS Edge, although it has not been tested (the version in the MS App Store is unaffected). It works as expected in Chromium-based Edge.

Fix MS Edge, reconcile differences between browsers

In the run-up to releasing the extension in the Chrome and Firefox stores, MS Edge functionality was broken.

This release fixes Edge support, and also refactors Chrome, Firefox, Edge, (and Opera, Vivaldi, etc.) to all use the codebase/method of injecting the bookmarking code, via content scripts.

Initial release

First release

This release should generate working extensions for:

• Google Chrome/Chromium
• Firefox
• Microsoft Edge
• Opera
• Vivaldi