We now position the arrow so it points to the toolbar button regardless
of its position.

In order to be sure that no other extension is resizing the inner window
due to merging its overlay into the chrome we resize the window (again)
via a mutation observer and a setTimeout(0) call. The mutation observer
helps us as DevTools code is modifying the DOM during start-up.

This approach minimizes the possible usability issues as well as the
window just gets larger by some pixels while being visible (if it gets
larger at all, i.e. if proper resizing did not succeed before the window
got visible). Provided it gets visible in the first place before the
final resizing gets applied.

We should clear permissions on New Identity as e.g. the web notification
permission would be able to link the old and the new session otherwise.

On some OS/desktop combinations there is a auto-maximize feature that
breaks our efforts to resize the inner window to a multiple of 200x100
on start-up. We fix that by listening to the sizemodechange event and
resizing the window again in case it got indeed maximized.

Without an update URL specified, Firefox will still ping addons.mozilla.org
for an update. If someone manages to register a fake Torbutton at our UID, it
could get pushed out to users.

Also sync up the banned ports list with TBB.

These settings shouldn't get applied in TBB normally. This is just defensive,
in case someone somehow manages to toggle Tor state still.

Use the NoScript service function directly.

Also bump version and changelog entry.

Needed on FF24. The current cache, cookie and DOM Storage APIs do not
otherwise clear private browsing mode data.

Required for cache isolation under FF24.

This time without the commit screw-up.

This reverts commit 609d5c25, which
accidentally committed some working changes.

To aid in build debugging.

Close Tor control port socket streams before closing socket.

Bug 10078: clearing crypto auth tokens; removing own handling of SSL session identifier cache as we get that for free when calling logoutAndTeardown()

Also clean up comments and whitespace.

As good a place as any for now, I guess...

Displaying the property name is better than throwing uncaught exceptions...

Clear the private browsing image cache as well as the regular one.

Use new APIs while maintaining compatibility with older versions of Firefox.

Modify torbutton_toggle_plugins() to use the new enabledState
attribute if it is available (FF23 and newer).