Basic usage: page functions
Suppose the page contains a function called
The user script knows this function as
The user script could simply call
unsafeWindow.pageFunc(), but this can leak the sandbox.
Instead, the user script can take advantage of
Just entering this URL into the browser's location bar does not leak a GreaseMonkey sandbox:
A user script can programmaticaly navigate to this URL, to safely call the function:
That, in a nutshell, is the location hack! Essentially, it is wrapping a bookmarklet into a user script.
It's important to add the
;void(0) to the end, which keeps the browser from actually navigating to this URL after it is run.
Modifying the page
The location hack can do anything a page script or bookmarklet can do, so it can modify content variables and such as easily as it can access them. For example:
Executing large blocks of code
Even though the function is defined in the sandbox, it is not a closure of the sandbox scope. It is converted to a string and then back to a function in page scope. It cannot access anything in the sandbox scope, which is a limitation, but is also essential to making this technique secure.
Percent encoding issue
Sometimes percent-encoding the percent symbol is required. For example,
The above code will cause error because %22 is interpreted as double quotation mark. The workaround is:
See also encodeURI().
The location hack is really handy for passing values to the content scope, or to call functions defined there.
It is not, however, capable of directly reading a variable or value returned from a function.
Furthermore, it is run asynchronously, much like
setTimeout(), so you cannot immediately rely on side effects.
(If you use the location hack to, for example, store a value in the DOM and then attempt to read it, it will only be available at some other later point in time.)