blocks|key|4249945|text|不是的。编写Unobtrusive+Javascript。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4249946|entityMap|0|LINK|mutability|MUTABLE|url|http://www.onlinetools.org/articles/unobtrusivejavascript/chapter1.html^0|6|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

No. Write <a href="http://www.onlinetools.org/articles/unobtrusivejavascript/chapter1.html" rel="nofollow noreferrer">Unobtrusive Javascript</a>.

blocks|key|4250000|text|如果您希望Javascript尽可能早地运行，那么包含内联Javascript可能是有意义的，因为它将在任何其他HTTP请求完成之前运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4250001|在某些情况下，您包含来自第三方提供商的Javascript，而您实际上别无选择。某些广告系统，以及谷歌分析，会浮现在脑海中。|4250002|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|$]]

If you want your Javascript to run as early as possible, it might make sense to include inline Javascript, since it will run before any other HTTP requests have necessarily completed. 

And in some cases, you're including Javascript from a 3rd party provider and you don't really have a choice. Certain ad systems, as well as Google Analytics, spring to mind.

blocks|key|4250038|text|如果脚本必须是动态生成的(比如由PHP或ASP.NET+MVC页面生成)，这是让它内联的一个原因:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4250039|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If the script must be dynamically generated (say by a PHP or ASP.NET MVC page) would be one reason to have it inline :-)

blocks|key|1032675|text|这取决于你打算写多少JS。如果您正在编写许多支持例程(大量的验证检查、文本处理、动画和特效)，那么将代码放在单独的文件中是有意义的。这允许代码重用，并从HTML页面中删除了大量垃圾。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032676|另一方面，不需要将10行代码或单个函数(想到的是刷新JS+)放在单独的文件中。它的加载速度也会稍快一些，因为浏览器不需要发出额外的HTTP请求来下载单独的JS文件。|1032677|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|$]]

Depends on how much JS do you plan to write. If you're writing many support routines (lots of validation checks, text processing, animation and effects) then it makes sense to have the code in a separate file. This allows code reuse and removes a lot of junk from your HTML page.

On the other hand, there is no need to put 10 lines of code, or a single function (a refresh JS comes to mind) in a separate file. It will also load slightly faster, since the browser does not need to make an additional HTTP request to download the separate JS file.

blocks|key|4250062|text|大多数XSS漏洞只能使用内联javascript进行攻击。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4250063|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Most XSS vulnerabilities can only be exploited using inline javascript.

blocks|key|79716|text|这不一定是一个足够的理由，但页面加载速度会更快。为此，有时，即使当您在另一个文件中编写脚本时，您也希望它在客户端显示为内联。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79717|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's not necessarily enough of a reason, but the pages will load faster. To this end, sometimes, even when you write the script in another file, you want it to show up as inline on the client side.

blocks|key|1381330|text|我有时会将javascript内联到部分重载的页面中(例如，将一些事件绑定到新添加的表单字段)和/或使用一些我不会在任何其他页面上使用的独特javascript的页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1381331|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I sometimes place javascript inline in pages that get partially reloaded (to bind some events to newly added form-fields for example) and / or pages that use some unique javascript that I will not use on any other page.

blocks|key|79811|text|拥有许多外部脚本最终会减慢页面速度，因为浏览器必须单独调用每个文件。将JavaScript合并到一个文件或页面本身有时可以缓解此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79812|另一方面，我相信浏览器在第一次调用脚本文件时可能会缓存一个脚本文件，所以如果你的站点中有很多相同的代码，那么外部是可行的。|79813|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|$]]

Having many external scripts can ultimately slow down the page as the browser must call each file separately. Combining the JavaScript into one file or into the page itself can sometimes alleviate this problem.

On the other hand, I believe the browser may cache a script file once it's been called for the first time so if you have a lot of the same code across your site, external is the way to go.

blocks|key|4250318|text|我在一种叫做Flex的东西上做了大量工作，它结合XML和ActionScript来创建最终的字节码。尽可能地将两者分开是ALWAYS的最佳实践。这样，您就可以非常清晰、轻松地将视图(在我的例子中是HTML或MXML+)与控制器(脚本)分开|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4250319|这还意味着，您不必担心为一行代码查找五个文件--所有代码都在一个地方。|4250320|entityMap^0|1O|6|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I work a good deal in something called Flex, which combines XML and ActionScript to create the final bytecode. It is ALWAYS best practice to separate the two as much as possible. That way, you can very clearly and easily separate the View (the HTML or MXML in my case) from the Controller (the script) 

It also means that you do not have to worry about looking through five files for one line of code -- all of your code is in one place.

I've been building a site. At some stage I noticed that IE display was a little broken and Chrome had all but rendered nothing but the body tag (empty), and FF all looked good.

After throwing my keyboard around the room and bashing my head against my mouse, I discovered the problem. I had left (don't ask how or why, must have been some lightning speed cut and paste error) an HTML comment unclosed in an inline script block.

<pre><code>&lt;script type="text/javascript"&gt;
 &lt;!--
 ...
 &lt;/script&gt;
</code></pre>

I'm guessing (not tested) the problem would have either not come up, or manifested itself in a far more noticeable way if the script was external. So anyways, I got to thinking, is there ever a time when you have a really good reason to write inline script??

Is there any good reason for javascript to be inline

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我一直在建一个网站。在某个阶段，我注意到IE显示有点损坏，Chrome只渲染了body标签(空)，FF看起来都很好。在我把键盘在房间里乱扔，用头撞了一下鼠标之后，我发现了问题。我在一个内联脚本块中留下了一个HTML注释(不要问是怎么回事或者为什么，一定是一些闪电般的剪切和粘贴错误)。<script type="text/javascript"> <!-- ...

问javascript是内联的有什么好的理由吗？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问javascript是内联的有什么好的理由吗？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问javascript是内联的有什么好的理由吗？
EN