参见:http://www.chromium.org/developers/design-documents/user-scripts/Support for Greasemonkey-style @include patterns is also implemented for compatibility, but @match is preferred.
With Greasemonkey-style @include rules, it is not possible for Chrome to know for certain the domains a script will run on (because google.* can also run on google.evil.com). Because of this, Chrome just tells users that these scripts will run on all domains, which is sometimes scarier than necessary. With @match, Chrome will tell users the correct set of domains a user script will run on.
评论