サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
大そうじへの備え
wiki.greasespot.net
Greasy Fork https://greasyfork.org/ Created by the maintainer of http://userstyles.org/. HTTPS is available and enforced by default. Open source, hosted on GitHub. OpenUserJS.org https://openuserjs.org/ "The home of FOSS user scripts." Only HTTPS is available. Open source, hosted on GitHub. Gist https://gist.github.com/ Gist is GitHub's "paste" service, where any set of simple files can be pasted
The @grant Metadata Block imperative controls which special APIs (if any) your script uses. If no value is specified, none will be used by default. If any value or values are specified, only those API methods will be provided. Examples It's common for scripts not to use any special APIs at all. In that case, use @grant none. // ==UserScript== // @name Grant None Example // @include http* // @grant
User scripts can be used in other browsers than Firefox, but the scripting APIs and browser JavaScript support vary. This page documents differences in other environments as compared to Greasemonkey in Firefox. [edit] Similar Userscript Systems These are userscript systems which work similarly to Greasemonkey for other browsers. A well-written userscript can work in any of these environments. [ed
With the @require metadata imperative, one can include entire extra files into a user script. This can also be used for including entire third-party libraries like jQuery or ReactJS. Most general purpose libraries are not written to operate within the Greasemonkey sandbox and thus may not work properly, so tread carefully. jQuery For a simple example, here is a way to load and use jQuery in your u
[edit] Overview Most all objects on a target web page that a user script sees are wrapped in XPCNativeWrapper. The reason for this is so that a script can change the properties of an object (actually the wrapper) without any JavaScript on the target page being able to interfere. Mostly the wrapping is "transparent" - wrapped and unwrapped objects behave the same because the wrapping object passes
Greasemonkey 0.7.20080121.0 introduced a change to work around a potential security problem which could break some previously working scripts. Starting at this version, GM "double-checks" the call stack of all calls into potentially unsafe Greasemonkey APIs to make sure that every frame on the stack is either from a user script, or from the browser DOM. The APIs that currently have this check are:
Hello new user, and welcome to Greasemonkey! This page is shown to you only once, the first time that you install Greasemonkey. It should help you get to know what Greasemonkey is, how it works, and how you can get help if you're having a problem. There's just a few important sites you should know about that can help give you the best Greasemonkey experience: http://wiki.greasespot.net/ Support an
As of Greasemonkey 4.0, this method has been removed. You should use the console instead.
Description This method performs a similar function to the standard XMLHttpRequest object, but allows these requests to cross the same origin policy boundaries. Syntax function GM.xmlHttpRequest( details ) Compatibility: Greasemonkey 4.0+ Arguments This method only takes one argument, the details object. Described below are the properties that may be defined on that object. See #Examples for more
Description The metadata block is a section of a user script that describes the script. It usually contains the script name, namespace, description, and include and exclude rules. The metadata block appears in JavaScript line comments and may appear anywhere in the top level Greasemonkey code scope of the script, but is usually near the top of the file. If the metadata block includes a key that Gr
This section of the manual will be short and sweet. As mentioned elsewhere, Greasemonkey provides several methods in its API to enhance the power of user scripts. They are listed here, with a brief description, but each separate method has its own page with more in-depth information, please continue reading there! Headers Metadata Block Information about the script such as its name or version is e
Tips, code samples, and suggestions for writing user scripts. Subcategories This category has the following 7 subcategories, out of 7 total.
The location hack is an older technique for crossing the barrier between the user script scope and the content window scope, when it exists. The previous version of this page may be read via history. In Firefox version 39.0.3 Mozilla patched a known security vulnerability. As a side effect, this broke the location hack. Thankfully in modern versions of Firefox and Greasemonkey, the location hack i
GreaseSpot is community documentation for user scripting with Greasemonkey. For All Users For Script Authors
このページを最初にブックマークしてみませんか？
『GreaseSpot Wiki』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
