blocks|key|357280|text|用户脚本(即随Chrome直接安装的扩展最终会自动转换为带有内容脚本的扩展，因此它们本质上是相同的。用户脚本更快、更容易编写，而且好的用户脚本可以在其他浏览器中得到支持。然而，Chrome中的用户脚本有几个限制。它们不能直接从网页读取或写入变量(只有标准DOM是共享的)。他们不能制作跨域XHR。相反，扩展功能更强大，但更难开发。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|357281|看起来你必须要写一个Chrome扩展，因为你需要“对外部网站进行API调用”。|357282|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

User scripts (ie. Greasemonkey scripts) installed directly with Chrome are eventually automatically converted to extensions with content scripts, so they're essentially the same. 
User scripts are quick and easier to write, and a good user script can be supported in other browsers. However, there are several limitations for user scripts in Chrome. They cannot directly read or write variables from webpages (only standard DOM is shared). They cannot make cross-origin XHRs.
On the contrary, extensions are much more powerful but harder to develop. 

It seems that you'll have to write a Chrome extensions as you need to 'make API calls to an external website'.

blocks|key|3038164|text|原生Chrome扩展和用户脚本之间有一些区别。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3038165|查看this+wiki+section查看Greasemonkey脚本和Chrome用户脚本之间的差异列表。|offset|length|3038166|如果您希望利用跨浏览器用户脚本，请尽量不使用GM_*方法或unsafeWindow。|style|CODE|3038167|从开发人员的角度来看，选择用户脚本或Chrome扩展没有优势，因为任何用户脚本都可以很容易地嵌入到Chrome扩展中。|3038168|如果您从部署的角度来看待此主题，则差异是显著的：|3038169|3038170|一键安装仅在Chrome网络商店中可用。仅限本机扩展。|unordered-list-item|3038171|用户脚本和本机扩展都可以从本地文件浏览器拖到扩展页面以安装扩展。|3038172|3038173|(用户脚本转换为has+been+deprecated.扩展；警告:见下文)|3038174|原生用户脚本支持将在2013年末停止工作，因为转换后的用户脚本使用清单版本1，该版本为Chrome|3038175|3038176|结论|3038177|我建议开发本机扩展。您可以使用以下目录结构从用户脚本轻松创建Chrome扩展：|3038178|manifest.json
whatever.user.js|code-block|syntax|javascript|3038179|最小manifest.json：|3038180|{
+++++"name":+"name+of+extension",
+++++"version":+"1",
+++++"manifest_version":+2,
+++++"content_scripts":+[{
+++++++++"js":+["whatever.user.js"],
+++++++++"matches":+["http://example.com/*"]
++++++}]
}|3038181|另请参阅|3038182|3038183|http://developer.chrome.com/extensions/content_scripts.html|3038184|http://developer.chrome.com/extensions/match_patterns.html|3038185|3038186|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.greasespot.net/Cross-browser_userscripting|1|http://developer.chrome.com/extensions/manifestVersion.html|2|3^0|0|2|H|0|0|M|4|T|C|0|0|0|0|0|0|0|8|J|1|0|0|0|0|0|0|0|0|0|0|0|1N|2|0|0|1M|3|0|0^^$0|@$1|2|3|4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1X|8|@]|9|@$D|1Y|E|1Z|1|20]]|A|$]]|$1|F|3|G|5|6|7|21|8|@$D|22|E|23|H|I]|$D|24|E|25|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|26|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|27|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|28|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|29|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|2A|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|2C|8|@]|9|@$D|2D|E|2E|1|2F]]|A|$]]|$1|W|3|X|5|Q|7|2G|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2I|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2J|8|@]|9|@]|A|$]]|$1|13|3|14|5|15|7|2K|8|@]|9|@]|A|$16|17]]|$1|18|3|19|5|6|7|2L|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|15|7|2M|8|@]|9|@]|A|$16|17]]|$1|1C|3|1D|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|Q|7|2P|8|@]|9|@$D|2Q|E|2R|1|2S]]|A|$]]|$1|1H|3|1I|5|Q|7|2T|8|@]|9|@$D|2U|E|2V|1|2W]]|A|$]]|$1|1J|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]|$1|1K|3|-4|5|6|7|2Y|8|@]|9|@]|A|$]]]|1L|$1M|$5|1N|1O|1P|A|$1Q|1R]]|1S|$5|1N|1O|1P|A|$1Q|1T]]|1U|$5|1N|1O|1P|A|$1Q|1G]]|1V|$5|1N|1O|1P|A|$1Q|1I]]]]

There are a few differences between a native Chrome extension and a user script.

See <a href="http://wiki.greasespot.net/Cross-browser_userscripting" rel="noreferrer">this wiki section</a> for a list of differences between Greasemonkey scripts and Chrome userscripts.

If you want to take advantage of cross-browser user scripts, try to not use <code>GM_*</code> methods or <code>unsafeWindow</code>.

From a developer's perspective, there is no advantage of preferring either User scripts or Chrome extensions, because any user script can easily be embedded in a Chrome extension.

If you view this topic in the light of deployment, then the differences are significant:

<ul>
<li>One-click install is only available in the Chrome Web Store. Native extensions only.</li>
<li>Both user scripts and native extensions can be dragged from the local file browser to the Extensions page to install the extension. 
(User scripts are converted to Chrome extensions; warning: see below)</li>
<li>Native user script support will stop working at the end of 2013, because converted user scripts use manifest version 1, which <a href="http://developer.chrome.com/extensions/manifestVersion.html" rel="noreferrer">has been deprecated</a>.</li>
</ul>

<h3>Conclusion</h3>

I recommend to develop native extensions. You can easily create a Chrome extension from a user script by using the following directory structure:

<pre><code>manifest.json
whatever.user.js
</code></pre>

Minimal manifest.json:

<pre><code>{
 "name": "name of extension",
 "version": "1",
 "manifest_version": 2,
 "content_scripts": [{
 "js": ["whatever.user.js"],
 "matches": ["http://example.com/*"]
 }]
}
</code></pre>

<h3>See also</h3>

<ul>
<li><a href="http://developer.chrome.com/extensions/content_scripts.html" rel="noreferrer">http://developer.chrome.com/extensions/content_scripts.html</a></li>
<li><a href="http://developer.chrome.com/extensions/match_patterns.html" rel="noreferrer">http://developer.chrome.com/extensions/match_patterns.html</a></li>
</ul>

blocks|key|3038230|text|写作(和分享！)用户脚本:只要您只使用普通的浏览器DOM+API，使用其他支持用户脚本的浏览器的任何人都可以很轻松地拾取并运行您的脚本(通常只是安装它而不进行编辑)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3038231|当你使用谷歌Chrome时，对他们不利的情况是，从Chrome21开始，安装它们变得非常混乱:你需要右键单击安装链接，将其保存到磁盘上，打开扩展页面，然后将保存的脚本拖入其中(是的)，或者从Chrome+Web+Store安装TamperMonkey+(它是免费的，基本上就像Greasemonkey对火狐所做的那样:为用户脚本安装和维护提供一个可承受的用户界面)。|offset|length|3038232|虽然你只需要做你列出的事情，但你可能不需要比用户脚本本机提供的更多的特权API访问:在另一个站点上，尝试执行你将在devtools控制台中为脚本编写的XMLHttpRequest代码，你将看到它是否足以满足你的需要。如今，许多web+API都支持CORS，这可能会使您的用例不必求助于专有的浏览器原生扩展API。|3038233|entityMap|0|LINK|mutability|MUTABLE|url|https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo^0|0|35|C|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

The case for writing (and sharing!) user scripts: as long as you just use normal browser DOM APIs, your script can with minimal effort be picked up and made to run (often just installing it without edits) by anyone using another user script capable browser.

The case against them, when you use Google Chrome, is that as of Chrome 21, installing them got ridiculously messy: you need to right click the installation link, save it to disk, open the extensions page, and drag the saved script in there (yes), or install <a href="https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo" rel="nofollow">TamperMonkey</a> from the Chrome Web Store (it is free, and does for Chrome essentially what Greasemonkey does for Firefox: gives user script installation and maintenance a bearable user interface).

While you only need to do the things you list, you may not need any more privileged API access than what user scripting gives you natively: try executing the XMLHttpRequest code you would be writing for the script in the devtools console when on another site and you'll see if it's enough for your needs or not. Many web APIs these days allow CORS support, which might save your use case from needing to resort to the proprietary browser-native extension APIs.

I am developing an extension that will read HTML elements value, then make API calls to an external website, get the results and display them in newly created HTML elements.

What are the pro/cons of writing it in native chrome extensions vs. userscripts?

Userscripts vs. Chrome Extension

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在开发一个扩展，它将读取HTML元素的值，然后对外部网站进行API调用，获得结果并在新创建的HTML元素中显示它们。用原生chrome扩展和用户脚本编写的优缺点是什么？

问用户脚本与Chrome扩展
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用户脚本与Chrome扩展EN