Location hack: Difference between revisions

From GreaseSpot Wiki
Jump to navigationJump to search
← Older editNewer edit →
comment4,
comment1,
Line 9: Line 9:
comment4,
comment4,


== Percent encoding issue ==
comment1,
 
Sometimes percent-encoding the percent symbol is required. For example,
 
location.href = ("javascript:(" + function() {
  var n = 44;
  if(!('''n%22''')) alert('n is a multiple of 22');
} + ")()");
 
The above code will cause error because %22 is interpreted as double quotation mark. The workaround is:
 
location.href = "javascript:(" + encodeURI(
  function() {
  var n = 44;
  if(!(n%22)) alert('n is a multiple of 22');
  }) + ")()";
 
See also [http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference:Global_Functions:encodeURI encodeURI()].


== Returning values ==
== Returning values ==

Revision as of 08:53, 9 August 2011

The location hack is an ugly but useful way to interact with the content scope of the page being user scripted. It does this by indirectly evaling strings within that scope.

comment1,

comment1,

comment1,

comment4,

comment1,

Returning values

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.) For reading javascript values from the content scope inside the sandbox, see Reading Content Globals for a reliable example.

See Also

Retrieved from "https://wiki.greasespot.net/index.php?title=Location_hack&oldid=6569"