因为这与从非兼容浏览器中隐藏脚本的传统方式是相冲突的。
Because it interfered with the traditional way of hiding scripts from noncompatible browsers.
在浏览器中查看这段脚本时，可以看到类似图4的内容。
When you look at this script in the browser, you see something like Figure 4.
而脚本正在下载，但是，浏览器不会启动任何其他下载甚至上不同的主机名。
While a script is downloading, however, the browser won't start any other downloads, even on different hostnames.
这个脚本的开头显示了用户浏览器的用户代理。
The script starts by showing the user agent of the user's browser.
请记住，脚本是由浏览器执行的，而不是样式表。
Remember that the script is executed by the browser, not by the style sheet.
如果我在开发HTML5应用，为什么我们需要下载(以及缓慢地)脚本来帮助兼容旧有浏览器呢？
If I'm building HTML5 apps, why should we require the download (and slow-down) of scripts that help out older browsers?
执行脚本获取浏览器动作（这些会被回放），允许执行自动的实施。
There were execution scripts that captured browser actions, which were played back, allowing automated execution to be performed.
他们常常使用WYSIWYG编辑器、脚本编辑器和浏览器调试工具之类的工具。
They often use tools like WYSIWYG editors, scripting editors, and browser debugging tools.
使用它来查看脚本、文件或者图片是浏览器最紧张，然后修改。
Use it to find which scripts, files, or images are placing the most strain on browsers. Then fix it.
脚本在工作者池中运行，不会触发浏览器的“无响应脚本”对话框。
Scripts executing in the WorkerPool will not trigger the browser's "unresponsive script" dialog.
恼人的是，你可能在浏览器发出脚本失控警告之前，就耗尽了系统的内存，导致浏览器处于停止响应的状态。
The annoying thing is that you may reach a memory limit before the long-running script dialog pops up and leave the browser in an unusable state.
接着，浏览器装入HTML文件，并执行脚本。
Next the browser loads the HTML file and executes the script.
可以看到，浏览器立即应用CSS和脚本。
As you can see, the browser applies the CSS and script immediately.
在禁用脚本的浏览器中工作。
您还可以从Web浏览器运行这个脚本，得到的输出相同。
You can also run this script from the web browser to see the same output.
在清单3中，客户端是一个运行客户端脚本的web浏览器。
In Listing 3 the client is a web browser running client-side scripting.
通过Web浏览器运行该脚本，产生以下输出
Run this script through a Web browser to produce the following output
该脚本通过浏览器上的XMLHttpRequest调用激活。
The script is invoked by an XMLHttpRequest call on the browser.
由于同源策略(Sameorigin)，浏览器脚本只能与它所源自的那个服务器进行会话。
Due to the Same origin policy, the browser script can talk to the server only where it originates.
这时您可以使用RedditKillfile(一种greasemonkey脚本)创建希望从浏览器视图中隐藏其评论的那些Reddit用户的“killfile”。
You can use RedditKillfile, a Greasemonkey script, to create a "killfile" of Reddit users whose comments you always want hidden from your browser view.
在命令行中运行此脚本并在浏览器中查看image . swf，结果如图4所示。
When I run this script on the command line and look at image.swf in my browser, I see something like Figure 4.
Content - type头部告诉浏览器，脚本在导出一个Excel电子表格。
The Content-type header tells the browser that the script is exporting an Excel spreadsheet.
这样，由于使用了联机/脱机转换的脚本处理程序，浏览器标题立即变成 “Todotool [offline]”。
The title immediately changes to "Todo tool [offline]," thanks to the script handlers for online/offline transition.
当浏览器遇到这些脚本标记时，它就加载该脚本。
When the browser encounters these script tags, it loads that script.
同时，你还可以选择查看原始版本的源代码或者被浏览器或其他脚本修改过的代码。
Plus, you can choose to view the original source or the source that has been modified by the browser or other scripts.
对于跨站点脚本预防情况，您需要过滤掉浏览器支持的脚本语言的转义字符。
In the case of cross-site scripting prevention, you need to filter out the escape characters for the scripting languages supported by the browser.
虽然我可以使用命令行脚本，但在浏览器中查看它更有意思。
I could use command-line scripts, but it's more interesting to see it in the browser.
这样可以通过禁用浏览器脚本和IE底安全等级的设置，保护浏览器免受通过已知漏洞发起的攻击。
This should protect against all known exploits of this vulnerability by disabling scripting and disabling less secure features in IE.
跨站点脚本攻击使黑客能够将恶意脚本嵌入到访问者的浏览器中，然后执行该脚本收集数据。
Cross-site scripting attacks allow hackers to embed a malicious script on your visitor's browser and then execute the script in order to gather data.
跨站点脚本攻击使黑客能够将恶意脚本嵌入到访问者的浏览器中，然后执行该脚本收集数据。
Cross-site scripting attacks allow hackers to embed a malicious script on your visitor's browser and then execute the script in order to gather data.
应用推荐