Don't show the view switcher until the first batch of annotations has
been received. (This first batch will be all the annotations, unless
there are more than 200 annotations of the page.)

This is an attempt to reduce "popping" caused by the annotation switcher
suddenly changing a brief time after first render, when annotations are
loaded:

https://github.com/hypothesis/product-backlog/issues/327#issuecomment-312657968

Frame destruction

Set the visibleHighlights state for multiple Guests

Convert Unicode service & tests to JS

Replace selection tabs with view switcher (feature flagged)

If the 'view-switcher' feature flat is enabled then use the new view
switcher component, otherwise uses the old selection tabs component.

The view switcher component is just a placeholder for now.

Also remove use of Angular mock/inject because it really isn't necessary
for testing this service.

Allow "oauthEnabled" setting to be overridden in client config

It makes more sense that this method is implemented in the Sidebar instead of Host

This means that sub-frames will get injected with the same set of whitelisted config values from the top level.
It’s good that there’s a whitelisting of the config before reaching this point, so there’s less of a security concern with the injection

This was done so I can have the sub-frame guests read the `config.showHighlights` option in order to set the initial highlight visibility at that level.

I want to prevent the potential chaining of config params here since I plan to pass the config object around in new places, the sub-frame guest level for example.

This will enable testing of 1st party OAuth in the client by creating a
custom bookmarklet or test page which embeds the client.

Adding waitForFrameObserver in frame manipulation tests

Multiple frame detection improvements

Improve tests for different localStorage-not-accessible situations

Run all of the existing tests to check behavior when localStorage is not
accessible, for the case where accessing `window.localStorage` throws.

The previous tests for this situation only tested the behavior of the
service constructor.

Use fallback when local storage throws

Whitelist config settings needed by multi-frame support

Better differentiation from .isLoaded

The tests are in a response to an issue found when frames get added/removed in quick succession. It was due to the timing of the debounce used in FrameObserver.
This also works to test against possible edge cases and ensures robustness of the feature by going full circle.

Reduces the footprint of CrossFrame by shifting away responsibility into this new module.

To my knowledge this is temporarily until a better flagging or set of options comes by

Use CrossFrame to show/hide the Sidebar

Enable feature flagged highlighter interface