…ists.

Content can see resource: but not chrome: URLs.  And chrome: works fine for JSM import.

Fixes greasemonkey#1787

Fixes greasemonkey#2003.

Fixes greasemonkey#1955

JsDev is incapable of understanding it.
See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=326842

Start much smaller, allow the user to change the size, remember the size.

Fixes greasemonkey#2191

1) Store menu commmands' data in a private closure, *in the sandbox*.
2) To list registered commands:
  a) Parent/chrome passes a message to child/frame.
  b) Frame passes an event (visible to content) into the sandbox.
  c) Sandbox passes private-closure-scoped commands' data to a frame-scoped callback.
  d) Frame passes data up to parent as a message.
  e) Chrome uses this data to populate the menu, at popupshowing time.
3) To run a command:
  a) User clicks on the menu item.
  b) Chrome sends a message to the frame.
  c) Frame sends an event to the sandbox.
  d) Sandbox finds the related registered command, calls its callback.

Phew!  But no references to documents/windows/browsers are ever stored anywhere, so they can't possibly leak anymore.

Along the way, simplify frame script by moving object methods to standalone functions; less state, less binding to fix "this" references.  The ContentObserver object is now really just there for `.observe()`.

TODO: Restore "delayed execution" feature, the only other usage of the (removed) ScriptRunner structure.

Refs: greasemonkey#2200
Refs: greasemonkey#2067

Just in case, so the command object cannot be changed.

Prevent event propagation when appropriate.  Add a random suffix to the event names, so content cannot predict the event name, and thus cannot listen for it.

Fixes greasemonkey#2041

I.e. from an old Sync record which did not specify user matches.  Default to nothing.

Fixes greasemonkey#2188

It's too late.  IDs are set.  Changing them would be a giant mess.

Ad greasemonkey#2107, greasemonkey#2234
The suggestion (for example).

by default sandboxes are created in the system zone which has a lifetime
equal to that of the process and has a fairly large footprint.

Since GM sandboxes are scoped to individual content pages they should be
allocated in the same GC zone as the content. This allows them to be
discarded together and also reduces the footprint (and thus GC overhead)
for the system zone.

Framescripts get loaded for each tab, this means each tab registered a
callback with the global observer service.

Move the observer registration to a module and dispatch from a hash
table instead, that reduces the number of callbacks called per
document-element-inserted from N to 1.

Based on https://github.com/blog/1184-contributing-guidelines and links
to the current Greasemonkey style guide and contributing guide.

ReferenceError: reference to undefined property
this.scripts[existingIndex]
- config.js:139:18

Add contributing guide.

…terMenuCommand_noCommands

GM 3.3: GM_registerMenuCommand - no commands

Fixes greasemonkey#2225

Create sandboxes with sameZoneAs to reduce GC costs

The 'use strict' - after installing a script (and not exists) - throws the warning

https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible

Disables addon compatibility shims in firefox.

It should improve performance and/or catch any remaining
incompatibilities.

Something deep in Firefox internals was failing, given the way we
called `.loadOneTab()`.  Switch to `.addTab()` and tweak the
notification bar to (apparently?) cope with the different timing
that results.

Along the way: fix the is-temp-script method to actually be handled,
by listening for it via the PPMM, not global MM.

Fixes greasemonkey#2202

build the dropdown menu asynchronously after requesting the frame URLs
through the message manager.

old: strings sent via e10s message manager are duplicated and the
sandbox holds onto them as source code, this causes unnecessary memory
overhead.

new: load scripts from file:// URIs and use lazy getters for
scriptSource

fixes greasemonkey#2103

fixes greasemonkey#2070

use export helpers to avoid xray backscatter

…nTab_inBackground

GM 3.2+: GM_openInTab(url, false) - open the page in the background

Refs greasemonkey#2247

Build monkey menu contents via async messages.

Fixes greasemonkey#2246

View source not working: fix for the context menu and [e10s on]

Refs greasemonkey#2202

…elFromURI_throwsTheError

[e10s]: newChannelFromURI - it sometimes throws the error

…ce_FIX

View source - fix for Firefox 38.0.5-

Refs greasemonkey#2202

…nTab_API_backward_compatible

GM_openInTab: synchronize API with Tampermonkey (backward compatible)

Refs greasemonkey#2186

Refs greasemonkey#2186

Refs greasemonkey#2186

…e_reopenable'

# Conflicts:
#	content/browser.js

…flicts, merged fails

…ged_GM_openInTab_closable_reopenable

Merge remote-tracking branch 'GM_openInTab_closable_reopenable' - conflicts, merged fails

fixes duplicates introduced by 6b05c48

- beam down IPCScripts in advance from parent when a script changes
- do script filtering/url matching in content process
- piggyback script change detection on http observers instead by
checking document/sub-document loads

Refs greasemonkey#2274

Fixes greasemonkey#2285

Fixes greasemonkey#2195

Refs greasemonkey#1944