diff options
| author | Peter Bengtsson <mail@peterbe.com> | 2021-07-31 09:33:29 -0400 |
|---|---|---|
| committer | Irvin <irvinfly@gmail.com> | 2021-08-01 13:37:23 +0800 |
| commit | b9783c06657382caf2267a9a098ffa8e95a7f2ab (patch) | |
| tree | ebd0cffca6aa6fe12829ff2791f9576898ebde26 /files/zh-cn/web | |
| parent | c57404698a76f159e63c19bc8f42a3d4503d672d (diff) | |
| download | translated-content-b9783c06657382caf2267a9a098ffa8e95a7f2ab.tar.gz translated-content-b9783c06657382caf2267a9a098ffa8e95a7f2ab.tar.bz2 translated-content-b9783c06657382caf2267a9a098ffa8e95a7f2ab.zip | |
remove link 'title' attributes that's just the 'href' (zh-cn, part 5)
Diffstat (limited to 'files/zh-cn/web')
49 files changed, 98 insertions, 98 deletions
diff --git a/files/zh-cn/web/api/beforeunloadevent/index.html b/files/zh-cn/web/api/beforeunloadevent/index.html index 69626e0ec7..6063ef1282 100644 --- a/files/zh-cn/web/api/beforeunloadevent/index.html +++ b/files/zh-cn/web/api/beforeunloadevent/index.html @@ -67,5 +67,5 @@ window.addEventListener("beforeunload", function( event ) { <li>{{Event("load")}}</li> <li>{{Event("beforeunload")}}</li> <li>{{Event("unload")}}</li> - <li><a href="http://www.whatwg.org/specs/web-apps/current-work/#prompt-to-unload-a-document" title="http://www.whatwg.org/specs/web-apps/current-work/#prompt-to-unload-a-document">卸载文档 — 提示卸载文档</a></li> + <li><a href="http://www.whatwg.org/specs/web-apps/current-work/#prompt-to-unload-a-document">卸载文档 — 提示卸载文档</a></li> </ul> diff --git a/files/zh-cn/web/api/blobbuilder/index.html b/files/zh-cn/web/api/blobbuilder/index.html index 03248ac1e5..1750cc61c1 100644 --- a/files/zh-cn/web/api/blobbuilder/index.html +++ b/files/zh-cn/web/api/blobbuilder/index.html @@ -162,7 +162,7 @@ void append( <ul> <li>从Firefox 14开始,使用<code>MozBlobBuilder</code>会在Web控制台显示一条警告消息: <code>MozBlobBuilder</code>已被废弃,请使用{{ domxref("Blob") }}来代替.</li> <li>从Firefox 18开始,<code>MozBlobBuilder</code>已被删除.</li> - <li>WebKit has deprecated <code>WebKitBlobBuilder</code> and has made its support configurable. Currently Safari disables the feature in Nightly, so it will never likely to ship in the final version. On the other hand, Chrome, which has supported it since Chrome 8, still enables the feature. So Chrome might continue to support the feature. (See this <a class="external" href="http://trac.webkit.org/changeset/115666" title="http://trac.webkit.org/changeset/115666">WebKit changeset</a> for details).</li> + <li>WebKit has deprecated <code>WebKitBlobBuilder</code> and has made its support configurable. Currently Safari disables the feature in Nightly, so it will never likely to ship in the final version. On the other hand, Chrome, which has supported it since Chrome 8, still enables the feature. So Chrome might continue to support the feature. (See this <a class="external" href="http://trac.webkit.org/changeset/115666">WebKit changeset</a> for details).</li> </ul> <h2 id="相关链接">相关链接</h2> <ul> diff --git a/files/zh-cn/web/api/eventtarget/addeventlistener/index.html b/files/zh-cn/web/api/eventtarget/addeventlistener/index.html index 05b9469b91..f9e79602af 100644 --- a/files/zh-cn/web/api/eventtarget/addeventlistener/index.html +++ b/files/zh-cn/web/api/eventtarget/addeventlistener/index.html @@ -45,7 +45,7 @@ Non-standard_inline}}); // Gecko/Mozilla only </ul> </dd> <dt><code>useCapture</code> {{optional_inline}}</dt> - <dd>{{jsxref("Boolean")}}，在DOM树中，注册了listener的元素， 是否要先于它下面的EventTarget，调用该listener。 当useCapture(设为true) 时，沿着DOM树向上冒泡的事件，不会触发listener。当一个元素嵌套了另一个元素，并且两个元素都对同一事件注册了一个处理函数时，所发生的事件冒泡和事件捕获是两种不同的事件传播方式。事件传播模式决定了元素以哪个顺序接收事件。进一步的解释可以查看 <a class="external" href="http://www.w3.org/TR/DOM-Level-3-Events/#event-flow" title="http://www.w3.org/TR/DOM-Level-3-Events/#event-flow">事件流</a> 及 <a href="http://www.quirksmode.org/js/events_order.html#link4">JavaScript Event order</a> 文档。 如果没有指定， <code>useCapture</code> 默认为 false 。 </dd> + <dd>{{jsxref("Boolean")}}，在DOM树中，注册了listener的元素， 是否要先于它下面的EventTarget，调用该listener。 当useCapture(设为true) 时，沿着DOM树向上冒泡的事件，不会触发listener。当一个元素嵌套了另一个元素，并且两个元素都对同一事件注册了一个处理函数时，所发生的事件冒泡和事件捕获是两种不同的事件传播方式。事件传播模式决定了元素以哪个顺序接收事件。进一步的解释可以查看 <a class="external" href="http://www.w3.org/TR/DOM-Level-3-Events/#event-flow">事件流</a> 及 <a href="http://www.quirksmode.org/js/events_order.html#link4">JavaScript Event order</a> 文档。 如果没有指定， <code>useCapture</code> 默认为 false 。 </dd> </dl> <div class="note"><strong>注意:</strong> 对于事件目标上的事件监听器来说，事件会处于“目标阶段”，而不是冒泡阶段或者捕获阶段。在目标阶段的事件会触发该元素（即事件目标）上的所有监听器，而不在乎这个监听器到底在注册时<code>useCapture</code> 参数值是true还是false。</div> @@ -661,7 +661,7 @@ window.addEventListener('scroll', function(event) { <ul> <li>{{domxref("EventTarget.removeEventListener()")}}</li> <li><a href="https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Creating_and_triggering_events">Creating and triggering custom events</a></li> - <li><a class="external" href="http://www.quirksmode.org/js/this.html" title="http://www.quirksmode.org/js/this.html">More details on the use of <code>this</code> in event handlers</a></li> + <li><a class="external" href="http://www.quirksmode.org/js/this.html">More details on the use of <code>this</code> in event handlers</a></li> </ul> <div class="content-27EWd_0" id="translate-man-app"> diff --git a/files/zh-cn/web/api/globaleventhandlers/onload/index.html b/files/zh-cn/web/api/globaleventhandlers/onload/index.html index a9a56d9c6b..3862a1aa88 100644 --- a/files/zh-cn/web/api/globaleventhandlers/onload/index.html +++ b/files/zh-cn/web/api/globaleventhandlers/onload/index.html @@ -66,7 +66,7 @@ translation_of: Web/API/GlobalEventHandlers/onload <h3 id="Specification" name="Specification">规范</h3> -<p>这个事件处理程序在 <a class="external" href="http://www.whatwg.org/html/#handler-window-onload" title="http://www.whatwg.org/html/#handler-window-onload">HTML</a> 中指定。</p> +<p>这个事件处理程序在 <a class="external" href="http://www.whatwg.org/html/#handler-window-onload">HTML</a> 中指定。</p> <h3 id="参见">参见</h3> diff --git a/files/zh-cn/web/api/htmlfieldsetelement/index.html b/files/zh-cn/web/api/htmlfieldsetelement/index.html index 51b93938c5..97b7692640 100644 --- a/files/zh-cn/web/api/htmlfieldsetelement/index.html +++ b/files/zh-cn/web/api/htmlfieldsetelement/index.html @@ -5,7 +5,7 @@ translation_of: Web/API/HTMLFieldSetElement --- <p>{{ ApiRef() }}</p> <h2 id="HTML_Field_Set_Element">HTML Field Set Element</h2> -<p>DOM <code>fieldset</code> elements expose the <a class="external" href="http://dev.w3.org/html5/spec/forms.html#htmlfieldsetelement" title="http://dev.w3.org/html5/spec/forms.html#htmlfieldsetelement">HTMLFieldSetElement</a> ({{ HTMLVersionInline(4) }} <a class="external" href="http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-7365882" title="http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-7365882">HTMLFieldSetElement</a>) interface, which provides special properties and methods (beyond the regular <a href="../../../../zh-CN/DOM/element" rel="internal">element</a> object interface they also have available to them by inheritance) for manipulating the layout and presentation of field-set elements.</p> +<p>DOM <code>fieldset</code> elements expose the <a class="external" href="http://dev.w3.org/html5/spec/forms.html#htmlfieldsetelement" title="http://dev.w3.org/html5/spec/forms.html#htmlfieldsetelement">HTMLFieldSetElement</a> ({{ HTMLVersionInline(4) }} <a class="external" href="http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-7365882">HTMLFieldSetElement</a>) interface, which provides special properties and methods (beyond the regular <a href="../../../../zh-CN/DOM/element" rel="internal">element</a> object interface they also have available to them by inheritance) for manipulating the layout and presentation of field-set elements.</p> <h2 id="属性">属性</h2> <p>以下属性除了 <strong>form</strong> 都是在 {{ HTMLVersionInline(5) }} 中新添加的.</p> <table class="standard-table"> diff --git a/files/zh-cn/web/api/idbobjectstore/index.html b/files/zh-cn/web/api/idbobjectstore/index.html index 172820799e..62eb51e71f 100644 --- a/files/zh-cn/web/api/idbobjectstore/index.html +++ b/files/zh-cn/web/api/idbobjectstore/index.html @@ -342,7 +342,7 @@ translation_of: Web/API/IDBObjectStore <dl> <dt><a href="/en/IndexedDB/IDBRequest" title="en/IndexedDB/IDBRequest">IDBRequest</a></dt> - <dd>A request object on which subsequent events related to this operation are fired. As <a href="http://www.w3.org/TR/IndexedDB/#object-store-deletion-operation" title="http://www.w3.org/TR/IndexedDB/#object-store-deletion-operation">per spec</a> the result of the Object Store Deletion Operation algorithm is <code>undefined</code>, so it's not possible to know if some records were actually deleted by looking at the request result.</dd> + <dd>A request object on which subsequent events related to this operation are fired. As <a href="http://www.w3.org/TR/IndexedDB/#object-store-deletion-operation">per spec</a> the result of the Object Store Deletion Operation algorithm is <code>undefined</code>, so it's not possible to know if some records were actually deleted by looking at the request result.</dd> </dl> <h5 id="Exceptions_3">Exceptions</h5> diff --git a/files/zh-cn/web/api/navigation_timing_api/index.html b/files/zh-cn/web/api/navigation_timing_api/index.html index a0cc8c3d75..243e3f5088 100644 --- a/files/zh-cn/web/api/navigation_timing_api/index.html +++ b/files/zh-cn/web/api/navigation_timing_api/index.html @@ -137,7 +137,7 @@ var pageLoadTime = perfData.loadEventEnd - perfData.navigationStart; <h2 id="Browser_Compatibility" name="Browser_Compatibility">规范</h2> <ul> - <li><a class="external" href="http://www.w3.org/TR/navigation-timing/" title="http://www.w3.org/TR/navigation-timing/">https://w3c.github.io/navigation-timing/</a></li> + <li><a class="external" href="http://www.w3.org/TR/navigation-timing/">https://w3c.github.io/navigation-timing/</a></li> </ul> <h2 id="浏览器兼容性">浏览器兼容性</h2> diff --git a/files/zh-cn/web/api/svganimatedangle/index.html b/files/zh-cn/web/api/svganimatedangle/index.html index ff9a9edcd9..05955b7429 100644 --- a/files/zh-cn/web/api/svganimatedangle/index.html +++ b/files/zh-cn/web/api/svganimatedangle/index.html @@ -32,7 +32,7 @@ translation_of: Web/API/SVGAnimatedAngle </tr> <tr> <th scope="row">Normative document</th> - <td><a class="external" href="http://www.w3.org/TR/SVG11/types.html#InterfaceSVGAnimatedAngle" title="http://www.w3.org/TR/SVG11/types.html#InterfaceSVGAnimatedAngle">SVG 1.1 (2nd Edition)</a></td> + <td><a class="external" href="http://www.w3.org/TR/SVG11/types.html#InterfaceSVGAnimatedAngle">SVG 1.1 (2nd Edition)</a></td> </tr> </tbody> </table> diff --git a/files/zh-cn/web/api/svgcircleelement/index.html b/files/zh-cn/web/api/svgcircleelement/index.html index e087961f10..a956d4ec03 100644 --- a/files/zh-cn/web/api/svgcircleelement/index.html +++ b/files/zh-cn/web/api/svgcircleelement/index.html @@ -41,7 +41,7 @@ translation_of: Web/API/SVGCircleElement </tr> <tr> <th scope="row">规范文档</th> - <td><a class="external" href="http://www.w3.org/TR/SVG11/shapes.html#InterfaceSVGCircleElement" title="http://www.w3.org/TR/SVG11/shapes.html#InterfaceSVGCircleElement">SVG 1.1 (2nd Edition)</a></td> + <td><a class="external" href="http://www.w3.org/TR/SVG11/shapes.html#InterfaceSVGCircleElement">SVG 1.1 (2nd Edition)</a></td> </tr> </tbody> </table> diff --git a/files/zh-cn/web/api/touch/radiusy/index.html b/files/zh-cn/web/api/touch/radiusy/index.html index 2243af5c73..7e76c7b6c3 100644 --- a/files/zh-cn/web/api/touch/radiusy/index.html +++ b/files/zh-cn/web/api/touch/radiusy/index.html @@ -18,7 +18,7 @@ translation_of: Web/API/Touch/radiusY 能够包围用户和触摸平面的接触面的最小椭圆的垂直轴(Y轴)半径.</dd> </dl> <h3 id="Specification" name="Specification">标准定义</h3> -<p><a class="external" href="http://www.w3.org/TR/touch-events/" title="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> +<p><a class="external" href="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> <h3 id="相关链接">相关链接</h3> <ul> <li>{{ domxref("Touch.radiusX") }}</li> diff --git a/files/zh-cn/web/api/touch/screenx/index.html b/files/zh-cn/web/api/touch/screenx/index.html index ef9ac6d9e0..afd76c8ba7 100644 --- a/files/zh-cn/web/api/touch/screenx/index.html +++ b/files/zh-cn/web/api/touch/screenx/index.html @@ -19,7 +19,7 @@ translation_of: Web/API/Touch/screenX 触点相对于屏幕左边沿的的X坐标. 不包含页面滚动的偏移量.</dd> </dl> <h3 id="Specification" name="Specification">标准定义</h3> -<p><a class="external" href="http://www.w3.org/TR/touch-events/" title="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> +<p><a class="external" href="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> <h3 id="相关链接">相关链接</h3> <ul> <li>{{ domxref("Touch.screenY") }}</li> diff --git a/files/zh-cn/web/api/touch/screeny/index.html b/files/zh-cn/web/api/touch/screeny/index.html index e3c583c101..ce6b83b446 100644 --- a/files/zh-cn/web/api/touch/screeny/index.html +++ b/files/zh-cn/web/api/touch/screeny/index.html @@ -25,7 +25,7 @@ translation_of: Web/API/Touch/screenY <h3 id="Specification" name="Specification">标准定义</h3> -<p><a class="external" href="http://www.w3.org/TR/touch-events/" title="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> +<p><a class="external" href="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> <h3 id="相关链接">相关链接</h3> diff --git a/files/zh-cn/web/api/touchevent/changedtouches/index.html b/files/zh-cn/web/api/touchevent/changedtouches/index.html index a286e3a674..8241c82b98 100644 --- a/files/zh-cn/web/api/touchevent/changedtouches/index.html +++ b/files/zh-cn/web/api/touchevent/changedtouches/index.html @@ -31,4 +31,4 @@ translation_of: Web/API/TouchEvent/changedTouches <h3 id="Specification" name="Specification">标准定义</h3> -<p><a class="external" href="http://www.w3.org/TR/touch-events/" title="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> +<p><a class="external" href="http://www.w3.org/TR/touch-events/">Touch Events Specification</a></p> diff --git a/files/zh-cn/web/api/touchevent/index.html b/files/zh-cn/web/api/touchevent/index.html index 7ca4bb4235..abc65b37b5 100644 --- a/files/zh-cn/web/api/touchevent/index.html +++ b/files/zh-cn/web/api/touchevent/index.html @@ -34,7 +34,7 @@ translation_of: Web/API/TouchEvent <dt>{{ domxref("event.ctrlKey", "TouchEvent.ctrlKey") }} {{readonlyInline}}</dt> <dd>布尔值，指明触摸事件触发时，键盘 ctrl 键是否被按下。</dd> <dt>{{ domxref("event.metaKey", "TouchEvent.metaKey") }} {{readonlyInline}}</dt> - <dd>布尔值，指明触摸事件触发时，键盘 meta 键 （<a href="http://en.wikipedia.org/wiki/Meta_key" title="http://en.wikipedia.org/wiki/Meta_key">Wikipedia - meta Key</a>）是否被按下。</dd> + <dd>布尔值，指明触摸事件触发时，键盘 meta 键 （<a href="http://en.wikipedia.org/wiki/Meta_key">Wikipedia - meta Key</a>）是否被按下。</dd> <dt>{{ domxref("event.shiftKey", "TouchEvent.shiftKey") }} {{readonlyInline}}</dt> <dd>布尔值，指明触摸事件触发时，键盘 shift 键是否被按下。</dd> <dt>{{ domxref("TouchEvent.targetTouches") }} {{readonlyInline}}</dt> diff --git a/files/zh-cn/web/api/web_workers_api/functions_and_classes_available_to_workers/index.html b/files/zh-cn/web/api/web_workers_api/functions_and_classes_available_to_workers/index.html index f859a3d938..29d8372106 100644 --- a/files/zh-cn/web/api/web_workers_api/functions_and_classes_available_to_workers/index.html +++ b/files/zh-cn/web/api/web_workers_api/functions_and_classes_available_to_workers/index.html @@ -315,7 +315,7 @@ translation_of: Web/API/Web_Workers_API/Functions_and_classes_available_to_worke <td>Creates a new {{ domxref("Worker") }}. Yes, workers can spawn more workers.</td> <td>{{CompatGeckoDesktop("1.9.1")}}</td> <td>10.0</td> - <td>{{CompatNo}} See <a class="external" href="https://code.google.com/p/chromium/issues/detail?id=31666" rel="external" title="http://code.google.com/p/chromium/issues/detail?id=31666">crbug.com/31666</a></td> + <td>{{CompatNo}} See <a class="external" href="https://code.google.com/p/chromium/issues/detail?id=31666" rel="external">crbug.com/31666</a></td> <td>{{CompatNo}}</td> </tr> <tr> diff --git a/files/zh-cn/web/api/web_workers_api/structured_clone_algorithm/index.html b/files/zh-cn/web/api/web_workers_api/structured_clone_algorithm/index.html index 5f59c5f8a0..29bd42fc24 100644 --- a/files/zh-cn/web/api/web_workers_api/structured_clone_algorithm/index.html +++ b/files/zh-cn/web/api/web_workers_api/structured_clone_algorithm/index.html @@ -100,7 +100,7 @@ original_slug: Web/Guide/API/DOM/The_structured_clone_algorithm <h2 id="相关链接">相关链接</h2> <ul> - <li><a href="http://www.w3.org/TR/html5/infrastructure.html#safe-passing-of-structured-data" title="http://www.w3.org/TR/html5/common-dom-interfaces.html#safe-passing-of-structured-data">HTML5 Specification: Safe passing of structured data</a></li> + <li><a href="http://www.w3.org/TR/html5/infrastructure.html#safe-passing-of-structured-data">HTML5 Specification: Safe passing of structured data</a></li> <li>{{ domxref("window.history") }}</li> <li>{{ domxref("window.postMessage()") }}</li> <li><a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API">Web Workers</a></li> diff --git a/files/zh-cn/web/api/webrtc_api/session_lifetime/index.html b/files/zh-cn/web/api/webrtc_api/session_lifetime/index.html index fca4ff4be7..b79db2fd31 100644 --- a/files/zh-cn/web/api/webrtc_api/session_lifetime/index.html +++ b/files/zh-cn/web/api/webrtc_api/session_lifetime/index.html @@ -22,7 +22,7 @@ original_slug: WebRTC/介绍 <h3 id="信令">信令</h3> -<p>信令是在两个设备之间发送控制信息以确定通信协议、信道、媒体编解码器和格式以及数据传输方法以及任何所需的路由信息的过程。 关于WebRTC的信令流程最重要的一点是：<strong>信令在规范中并没有定义。</strong>所以开发者需要自己决定如何实现这个过程。开发者可以为应用程序引擎选择任意的信息协议（如SIP或XMPP），任意双向通信信道（如WebSocket或XMLHttpRequest)与持久连接服务器的API（如<a href="https://developers.google.com/appengine/docs/python/channel/overview" style="line-height: 1.5; text-decoration: none;" title="https://developers.google.com/appengine/docs/python/channel/overview">Google Channel API</a><span style="line-height: 1.5;">）一起工作。</span></p> +<p>信令是在两个设备之间发送控制信息以确定通信协议、信道、媒体编解码器和格式以及数据传输方法以及任何所需的路由信息的过程。 关于WebRTC的信令流程最重要的一点是：<strong>信令在规范中并没有定义。</strong>所以开发者需要自己决定如何实现这个过程。开发者可以为应用程序引擎选择任意的信息协议（如SIP或XMPP），任意双向通信信道（如WebSocket或XMLHttpRequest)与持久连接服务器的API（如<a href="https://developers.google.com/appengine/docs/python/channel/overview" style="line-height: 1.5; text-decoration: none;">Google Channel API</a><span style="line-height: 1.5;">）一起工作。</span></p> <p><span style="line-height: 1.5;">你可能会想，为什么这么一个对于建立WebRTC连接至关重要的基本过程居然没有定义在规范里？ 答案很简单：由于两个设备无法直接相互联系，规范无法预测WebRTC的所有可能用例，因此更明智的做法就是让开发人员们自己选择合适的网络技术和消息传递协议。</span></p> diff --git a/files/zh-cn/web/api/windoweventhandlers/onbeforeunload/index.html b/files/zh-cn/web/api/windoweventhandlers/onbeforeunload/index.html index c2ac5649b6..3d2b1bd85d 100644 --- a/files/zh-cn/web/api/windoweventhandlers/onbeforeunload/index.html +++ b/files/zh-cn/web/api/windoweventhandlers/onbeforeunload/index.html @@ -17,7 +17,7 @@ original_slug: Web/API/Window/onbeforeunload <ul> <li><code>funcRef</code> 是一个函数引用</li> <li>该函数应当将一个说明字符串赋值给<code>Event</code>对象的<code>returnValue</code>属性(兼容旧版浏览器),并且返回该字符串</li> - <li>请注意,在Firefox4及其后续版本中,返回的说明字符串并不向用户显示,也就是无法自定义说明字符串.查看<a class="external link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=588292" title="https://bugzilla.mozilla.org/show_bug.cgi?id=588292">Bug 588292</a>.</li> + <li>请注意,在Firefox4及其后续版本中,返回的说明字符串并不向用户显示,也就是无法自定义说明字符串.查看<a class="external link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=588292">Bug 588292</a>.</li> </ul> <h2 id="Example" name="Example">示例</h2> @@ -39,7 +39,7 @@ original_slug: Web/API/Window/onbeforeunload <p>当该事件返回的字符串（事前设置好的event.returnValue的值）不为null或者undefined时，弹出确认窗口让用户自行选择是否关闭当前页面。一些浏览器将该事件返回的字符串显示在弹出窗上。从Firefox 4、 Chrome 51、Opera 38 和Safari 9.1开始，通用确认信息代替事件返回的字符串。比如，火狐上会显示“本页面要求您确认您要离开 - 您输入的数据可能不会被保存”，请查阅{{bug("588292")}}和<a href="https://www.chromestatus.com/feature/5349061406228480">Chrome Platform Status</a>。</p> -<p>从2011年5月25日起, <a class="external" href="http://www.w3.org/TR/html5-diff/#changes-2011-05-25" title="http://www.w3.org/TR/html5-diff/#changes-2011-05-25">HTML5 规范</a> 声明:在该事件的处理函数中调用下列弹窗相关的方法时,可以忽略不执行,<code><a class="new" href="https://developer.mozilla.org/zh-CN/docs/DOM/window.showModalDialog">window.showModalDialog()</a></code>, <code><a href="https://developer.mozilla.org/zh-CN/docs/DOM/window.alert">window.alert()</a></code>, <code><a class="new" href="https://developer.mozilla.org/zh-CN/docs/DOM/window.confirm">window.confirm()</a></code> <code><a href="https://developer.mozilla.org/zh-CN/docs/DOM/window.prompt">window.prompt()</a></code>.</p> +<p>从2011年5月25日起, <a class="external" href="http://www.w3.org/TR/html5-diff/#changes-2011-05-25">HTML5 规范</a> 声明:在该事件的处理函数中调用下列弹窗相关的方法时,可以忽略不执行,<code><a class="new" href="https://developer.mozilla.org/zh-CN/docs/DOM/window.showModalDialog">window.showModalDialog()</a></code>, <code><a href="https://developer.mozilla.org/zh-CN/docs/DOM/window.alert">window.alert()</a></code>, <code><a class="new" href="https://developer.mozilla.org/zh-CN/docs/DOM/window.confirm">window.confirm()</a></code> <code><a href="https://developer.mozilla.org/zh-CN/docs/DOM/window.prompt">window.prompt()</a></code>.</p> <p>需要指出的是，许多浏览器会忽略该事件并自动关闭页面无需用户的确认。火狐浏览器在配置页面<a>about:config</a>设有一个dom.disable_beforeunload的开关变量用于开启这个功能。</p> diff --git a/files/zh-cn/web/api/windoweventhandlers/onpopstate/index.html b/files/zh-cn/web/api/windoweventhandlers/onpopstate/index.html index 54efcf6cf4..3b0e037dd3 100644 --- a/files/zh-cn/web/api/windoweventhandlers/onpopstate/index.html +++ b/files/zh-cn/web/api/windoweventhandlers/onpopstate/index.html @@ -48,7 +48,7 @@ history.go(2); // 弹出 "location: http://example.com/example.html?page=3, sta <h3 id="Specification" name="Specification">规范</h3> <ul> - <li><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/#handler-window-onpopstate" title="http://www.whatwg.org/specs/web-apps/current-work/#handler-window-onpopstate">HTML5 popstate event</a></li> + <li><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/#handler-window-onpopstate">HTML5 popstate event</a></li> </ul> <h3 id="浏览器兼容性">浏览器兼容性</h3> diff --git a/files/zh-cn/web/css/background-size/index.html b/files/zh-cn/web/css/background-size/index.html index e7f34927fa..cd8e04e7e8 100644 --- a/files/zh-cn/web/css/background-size/index.html +++ b/files/zh-cn/web/css/background-size/index.html @@ -190,7 +190,7 @@ background-size: 50% 25%;</code></pre> <h2 id="备注">备注</h2> -<p>如果用渐变作为背景并且对它使用了<code>background-size</code> ，最好不要只用一个auto， 或者只指定一个宽度值 (例如 <code>background-size: 50%</code>)。对这两种情况 Firefox 8有所改变， 并且目前各浏览器表现不一致，不是全部浏览器都完全支持 <a href="http://www.w3.org/TR/css3-background/#the-background-size" title="http://www.w3.org/TR/css3-background/#the-background-size">CSS3 <code>background-size</code> 规范</a> 与 <a href="http://dev.w3.org/csswg/css3-images/#gradients">CSS3 Image Values gradient 规范</a> 。</p> +<p>如果用渐变作为背景并且对它使用了<code>background-size</code> ，最好不要只用一个auto， 或者只指定一个宽度值 (例如 <code>background-size: 50%</code>)。对这两种情况 Firefox 8有所改变， 并且目前各浏览器表现不一致，不是全部浏览器都完全支持 <a href="http://www.w3.org/TR/css3-background/#the-background-size">CSS3 <code>background-size</code> 规范</a> 与 <a href="http://dev.w3.org/csswg/css3-images/#gradients">CSS3 Image Values gradient 规范</a> 。</p> <pre class="brush: css notranslate">.bar { width: 50px; height: 100px; diff --git a/files/zh-cn/web/css/text-rendering/index.html b/files/zh-cn/web/css/text-rendering/index.html index 26730b874b..adced6404f 100644 --- a/files/zh-cn/web/css/text-rendering/index.html +++ b/files/zh-cn/web/css/text-rendering/index.html @@ -149,7 +149,7 @@ body { text-rendering: optimizeLegibility; } <tr> <td>Basic support for Windows and Linux</td> <td> - <p>4.0 but the implementation known bugs on Windows and Linux which can break <a href="http://crbug.com/114719" title="http://crbug.com/114719">font substitition</a>, <a href="http://crbug.com/51973" title="http://crbug.com/51973">small-caps</a>, <a href="http://crbug.com/55458">letter-spacing</a> or cause <a href="http://crbug.com/149548">text to overlap</a></p> + <p>4.0 but the implementation known bugs on Windows and Linux which can break <a href="http://crbug.com/114719" title="http://crbug.com/114719">font substitition</a>, <a href="http://crbug.com/51973">small-caps</a>, <a href="http://crbug.com/55458">letter-spacing</a> or cause <a href="http://crbug.com/149548">text to overlap</a></p> </td> <td><strong>3.0</strong> (1.9)</td> <td>{{ CompatNo() }}</td> diff --git a/files/zh-cn/web/css/url()/index.html b/files/zh-cn/web/css/url()/index.html index a8f6be8f41..2199ca83ed 100644 --- a/files/zh-cn/web/css/url()/index.html +++ b/files/zh-cn/web/css/url()/index.html @@ -13,7 +13,7 @@ original_slug: Web/CSS/url <div class="note"><strong>URI 和 URL?</strong><br> <br> -<a class="external" href="https://zh.wikipedia.org/wiki/%E7%BB%9F%E4%B8%80%E8%B5%84%E6%BA%90%E6%A0%87%E5%BF%97%E7%AC%A6" title="http://en.wikipedia.org/wiki/Uniform_Resource_Identifier">URI</a>（统一资源标识符） 与 <a class="external" href="https://zh.wikipedia.org/wiki/%E7%BB%9F%E4%B8%80%E8%B5%84%E6%BA%90%E5%AE%9A%E4%BD%8D%E7%AC%A6">URL</a>（统一资源定位符） 不同。URL 描述资源的位置，而 URI 描述资源的 id。URI 可以是一个资源的 URL（地址）、或 <a class="external" href="https://zh.wikipedia.org/wiki/%E7%BB%9F%E4%B8%80%E8%B5%84%E6%BA%90%E5%90%8D%E7%A7%B0">URN</a>（统一资源名称）。<br> +<a class="external" href="https://zh.wikipedia.org/wiki/%E7%BB%9F%E4%B8%80%E8%B5%84%E6%BA%90%E6%A0%87%E5%BF%97%E7%AC%A6">URI</a>（统一资源标识符） 与 <a class="external" href="https://zh.wikipedia.org/wiki/%E7%BB%9F%E4%B8%80%E8%B5%84%E6%BA%90%E5%AE%9A%E4%BD%8D%E7%AC%A6">URL</a>（统一资源定位符） 不同。URL 描述资源的位置，而 URI 描述资源的 id。URI 可以是一个资源的 URL（地址）、或 <a class="external" href="https://zh.wikipedia.org/wiki/%E7%BB%9F%E4%B8%80%E8%B5%84%E6%BA%90%E5%90%8D%E7%A7%B0">URN</a>（统一资源名称）。<br> <br> 在 CSS Level 1 中，<code>url()</code> 函数被引入并用于描述 URL，即地址（虽然没有明确定义，但指一个 CSS 数据类型 <code><url></code>）<br> <br> diff --git a/files/zh-cn/web/demos_of_open_web_technologies/index.html b/files/zh-cn/web/demos_of_open_web_technologies/index.html index f330fd6634..29978d4ed2 100644 --- a/files/zh-cn/web/demos_of_open_web_technologies/index.html +++ b/files/zh-cn/web/demos_of_open_web_technologies/index.html @@ -25,7 +25,7 @@ original_slug: Web/演示说明 <li><a href="http://www.blobsallad.se/">Blob Sallad: an interactive blob using JavaScript and canvas</a>（<a href="http://blobsallad.se/article/">示例</a>）</li> <li><a href="http://arapehlivanian.com/wp-content/uploads/2007/02/canvas.html">Flying through space</a></li> <li><a href="https://developer.mozilla.org/samples/raycaster/RayCaster.html" title="https://developer.mozilla.org/editor/fckeditor/core/editor/samples/raycaster/RayCaster.html">3D RayCaster</a></li> - <li><a href="http://processingjs.org/exhibition/" title="http://dev.jquery.com/~john/processing.js/examples/basic/">processing.js</a></li> + <li><a href="http://processingjs.org/exhibition/">processing.js</a></li> <li><a href="http://gyu.que.jp/jscloth/">3D on 2D Canvas</a></li> <li><a href="http://viliusle.github.io/miniPaint/">miniPaint: Image editor</a>（<a href="https://github.com/viliusle/miniPaint">源码</a>）</li> <li><a href="http://zenphoton.com/">Zen Photon Garden</a>（<a href="https://github.com/scanlime/zenphoton">源码</a>）</li> @@ -38,7 +38,7 @@ original_slug: Web/演示说明 <li><a class="external" href="http://starkravingfinkle.org/blog/2007/07/firefox-3-svg-foreignobject/">HTML transformations</a>（使用了 <code><foreignObject></code> 元素）（视觉特效与变换）</li> <li><a class="external" href="http://svg-whiz.com/svg/linguistics/theCreepyMouth.svg">Phonetics Guide</a>（可交互）</li> <li><a class="external" href="http://www.lutanho.net/svgvml3d/platonic.html">3D objects demo</a>（可交互）</li> - <li><a class="external" href="http://www.themaninblue.com/experiment/Blobular/" title="http://www.themaninblue.com/experiment/Blobular/">Blobular</a>（可交互）</li> + <li><a class="external" href="http://www.themaninblue.com/experiment/Blobular/">Blobular</a>（可交互）</li> <li><a class="external" href="http://www.double.co.nz/video_test/video.svg">Video embedded in SVG</a>（或<a href="http://www.double.co.nz/video_test/video_svg.tar.bz2">下载到本地</a>）</li> <li><a href="http://summerstyle.github.io/summer/">Summer HTML image map creator</a>（<a href="https://github.com/summerstyle/summer">源码</a>）</li> </ul> @@ -150,6 +150,6 @@ original_slug: Web/演示说明 <li><a href="http://ondras.github.io/fractal/">Web Worker Fractals</a></li> <li><a href="http://ondras.github.io/photo/">Photo editor</a></li> <li><a href="http://ondras.github.io/coral/">Coral generator</a></li> - <li><a class="external" href="http://nerget.com/rayjs-mt/rayjs.html" title="http://nerget.com/rayjs-mt/rayjs.html">Raytracer</a></li> + <li><a class="external" href="http://nerget.com/rayjs-mt/rayjs.html">Raytracer</a></li> <li><a href="http://palerdot.github.io/hotcold/">HotCold Touch Typing</a></li> </ul> diff --git a/files/zh-cn/web/html/element/a/index.html b/files/zh-cn/web/html/element/a/index.html index f2d265ea4c..1434cbf360 100644 --- a/files/zh-cn/web/html/element/a/index.html +++ b/files/zh-cn/web/html/element/a/index.html @@ -71,7 +71,7 @@ translation_of: Web/HTML/Element/a </div> </dd> <dt>{{htmlattrdef("hreflang")}}</dt> - <dd>该属性用于指定链接文档的人类语言。其仅提供建议，并没有内置的功能。hreflang 允许的值取决于HTML5 <a class="external" href="http://www.ietf.org/rfc/bcp/bcp47.txt" title="http://www.ietf.org/rfc/bcp/bcp47.txt">BCP47</a>。</dd> + <dd>该属性用于指定链接文档的人类语言。其仅提供建议，并没有内置的功能。hreflang 允许的值取决于HTML5 <a class="external" href="http://www.ietf.org/rfc/bcp/bcp47.txt">BCP47</a>。</dd> <dt>{{htmlattrdef("ping")}}</dt> <dd>包含一个以空格分隔的url列表，当跟随超链接时，将由浏览器(在后台)发送带有正文 PING 的 POST 请求。通常用于跟踪。</dd> <dd> @@ -118,7 +118,7 @@ translation_of: Web/HTML/Element/a <h3 id="过时的">过时的</h3> </dt> <dt>{{htmlattrdef("charset")}} {{obsoleteGeneric("inline","HTML5")}}</dt> - <dd>此属性定义链接资源的字符编码。该值是一个空格- 和/或逗号分隔的<a class="external" href="http://tools.ietf.org/html/rfc2045" style="color: rgb(102, 153, 204); text-decoration: none; padding-right: 16px; background-color: rgb(255, 255, 255); font-family: 'Lucida Grande', 'Lucida Sans Unicode', 'DejaVu Sans', Lucida, Arial, Helvetica, sans-serif; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 22px; text-align: start; text-indent: 0px; text-transform: none; white-space: normal;" title="http://tool??s.ietf.org/html/rfc2045">RFC 2045</a>中定义的字符集列表。默认值是ISO-8859-1。 + <dd>此属性定义链接资源的字符编码。该值是一个空格- 和/或逗号分隔的<a class="external" href="http://tools.ietf.org/html/rfc2045" style="color: rgb(102, 153, 204); text-decoration: none; padding-right: 16px; background-color: rgb(255, 255, 255); font-family: 'Lucida Grande', 'Lucida Sans Unicode', 'DejaVu Sans', Lucida, Arial, Helvetica, sans-serif; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 22px; text-align: start; text-indent: 0px; text-transform: none; white-space: normal;">RFC 2045</a>中定义的字符集列表。默认值是ISO-8859-1。 <div class="note"> <p><strong>使用说明: </strong>在 HTML5 中该属性已作废，不应使用。 为了实现其效果，使用HTTP content - type header的链接资源。</p> </div> diff --git a/files/zh-cn/web/html/element/area/index.html b/files/zh-cn/web/html/element/area/index.html index 0afb9521e6..62fe488405 100644 --- a/files/zh-cn/web/html/element/area/index.html +++ b/files/zh-cn/web/html/element/area/index.html @@ -49,7 +49,7 @@ translation_of: Web/HTML/Element/area <dl> <dt>{{htmlattrdef("hreflang")}} {{HTMLVersionInline("5")}}</dt> - <dd>指明链接资源的语言类型, 值的范围参考<a class="external" href="http://www.ietf.org/rfc/bcp/bcp47.txt" title="http://www.ietf.org/rfc/bcp/bcp47.txt">BCP47</a>. 这个属性只能在指明href属性之后使用.</dd> + <dd>指明链接资源的语言类型, 值的范围参考<a class="external" href="http://www.ietf.org/rfc/bcp/bcp47.txt">BCP47</a>. 这个属性只能在指明href属性之后使用.</dd> </dl> <dl> diff --git a/files/zh-cn/web/html/element/col/index.html b/files/zh-cn/web/html/element/col/index.html index 317a35f680..28eb2b5fb4 100644 --- a/files/zh-cn/web/html/element/col/index.html +++ b/files/zh-cn/web/html/element/col/index.html @@ -54,7 +54,7 @@ translation_of: Web/HTML/Element/col <dl> <dt>{{htmlattrdef("bgcolor")}} {{Non-standard_inline}}</dt> - <dd>定义列中对应的每个单元格的背景色。其值是 <a class="external" href="http://www.w3.org/Graphics/Color/sRGB" title="http://www.w3.org/Graphics/Color/sRGB">sRGB</a> 定义的6位16进制代码之一，前缀为 '#'。 也可以使用以下16个预定义的颜色字符: + <dd>定义列中对应的每个单元格的背景色。其值是 <a class="external" href="http://www.w3.org/Graphics/Color/sRGB">sRGB</a> 定义的6位16进制代码之一，前缀为 '#'。 也可以使用以下16个预定义的颜色字符: <table style="width: 80%;"> <tbody> <tr> diff --git a/files/zh-cn/web/html/element/colgroup/index.html b/files/zh-cn/web/html/element/colgroup/index.html index 5ebaef5929..fc15883a37 100644 --- a/files/zh-cn/web/html/element/colgroup/index.html +++ b/files/zh-cn/web/html/element/colgroup/index.html @@ -85,7 +85,7 @@ translation_of: Web/HTML/Element/colgroup <dl> <dt>{{htmlattrdef("bgcolor")}} {{Non-standard_inline}}</dt> - <dd>这个属性用于定义列组中的每一个列成员的背景颜色。在 <a class="external" href="http://www.w3.org/Graphics/Color/sRGB" title="http://www.w3.org/Graphics/Color/sRGB">sRGB</a> 的定义中，它是一个以 '#' 开头的 6 位 16 进制值，有 16 个预定义的表示颜色的字符串可以使用，如下所示： + <dd>这个属性用于定义列组中的每一个列成员的背景颜色。在 <a class="external" href="http://www.w3.org/Graphics/Color/sRGB">sRGB</a> 的定义中，它是一个以 '#' 开头的 6 位 16 进制值，有 16 个预定义的表示颜色的字符串可以使用，如下所示： <table> <tbody> <tr> diff --git a/files/zh-cn/web/html/element/head/index.html b/files/zh-cn/web/html/element/head/index.html index 338521df1f..e2cc54a600 100644 --- a/files/zh-cn/web/html/element/head/index.html +++ b/files/zh-cn/web/html/element/head/index.html @@ -41,7 +41,7 @@ translation_of: Web/HTML/Element/head <h2 id="附注">附注</h2> -<p>如果在文档中忽略了 <code><head></code> 标签，则大部分浏览器会自动创建一个 <code><head></code> 元素。<a class="external" href="http://www.stevesouders.com/blog/2010/05/12/autohead-my-first-browserscope-user-test/" title="http://www.stevesouders.com/blog/2010/05/12/autohead-my-first-browserscope-user-test/">当然，有一些不会</a>。<br> +<p>如果在文档中忽略了 <code><head></code> 标签，则大部分浏览器会自动创建一个 <code><head></code> 元素。<a class="external" href="http://www.stevesouders.com/blog/2010/05/12/autohead-my-first-browserscope-user-test/">当然，有一些不会</a>。<br> 下面这些浏览器经测试不会自动创建一个 head 元素：Android <=1.6, iPhone <=3.1.3, Nokia 90, Opera <=9.27, and Safari <=3.2.1。</p> <h2 id="Specifications" name="Specifications">规范</h2> diff --git a/files/zh-cn/web/html/element/input/index.html b/files/zh-cn/web/html/element/input/index.html index 6747278313..2c35a8ea74 100644 --- a/files/zh-cn/web/html/element/input/index.html +++ b/files/zh-cn/web/html/element/input/index.html @@ -578,7 +578,7 @@ translation_of: Web/HTML/Element/input <p>When the form above is submitted, the input cause both the <code>name</code> / <code>value</code> pair of <code>fruit=cherry</code> and the <code>dirname</code> / direction pair of <code>fruit.dir=ltr</code> to be sent.</p> </dd> <dt>{{ htmlattrdef("disabled") }}</dt> - <dd>这个布尔属性表示此表单控件不可用。 特别是在禁用的控件中， <code>click</code> 事件 <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#enabling-and-disabling-form-controls" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#enabling-and-disabling-form-controls">将不会被分发</a> 。 并且，禁用的控件的值在提交表单时也不会被提交。如果 <strong>type</strong> 属性为 <span style="font-family: courier new;">hidden</span>，此属性将被忽略。</dd> + <dd>这个布尔属性表示此表单控件不可用。 特别是在禁用的控件中， <code>click</code> 事件 <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#enabling-and-disabling-form-controls">将不会被分发</a> 。 并且，禁用的控件的值在提交表单时也不会被提交。如果 <strong>type</strong> 属性为 <span style="font-family: courier new;">hidden</span>，此属性将被忽略。</dd> </dl> <div class="note"><strong>Note:</strong> Although not required by the specification, Firefox will by default <a href="https://stackoverflow.com/questions/5985839/bug-with-firefox-disabled-attribute-of-input-not-resetting-when-refreshing">persist the dynamic disabled state</a> of an <code><input></code> across page loads. Use the {{htmlattrxref("autocomplete","input")}} attribute to control this feature.</div> diff --git a/files/zh-cn/web/html/element/strong/index.html b/files/zh-cn/web/html/element/strong/index.html index 3c26687500..b630ce99f0 100644 --- a/files/zh-cn/web/html/element/strong/index.html +++ b/files/zh-cn/web/html/element/strong/index.html @@ -34,7 +34,7 @@ translation_of: Web/HTML/Element/strong </tr> <tr> <td>规范文档</td> - <td><a href="http://www.w3.org/TR/html5/text-level-semantics.html#the-strong-element" title="http://www.w3.org/TR/html5/text-level-semantics.html#the-strong-element">HTML5, section 4.6.3</a>; <a href="http://www.w3.org/TR/html401/struct/text.html#edef-STRONG" title="http://www.w3.org/TR/html401/struct/text.html#edef-STRONG">HTML 4.01, section 9.2.1</a></td> + <td><a href="http://www.w3.org/TR/html5/text-level-semantics.html#the-strong-element" title="http://www.w3.org/TR/html5/text-level-semantics.html#the-strong-element">HTML5, section 4.6.3</a>; <a href="http://www.w3.org/TR/html401/struct/text.html#edef-STRONG">HTML 4.01, section 9.2.1</a></td> </tr> </tbody> </table> diff --git a/files/zh-cn/web/html/element/summary/index.html b/files/zh-cn/web/html/element/summary/index.html index eb18e10ed3..c959270b5d 100644 --- a/files/zh-cn/web/html/element/summary/index.html +++ b/files/zh-cn/web/html/element/summary/index.html @@ -30,7 +30,7 @@ translation_of: Web/HTML/Element/summary </tr> <tr> <th scope="row">文档规范</th> - <td><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element" rel="external nofollow" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element">HTML5, section 4.11.2</a></td> + <td><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element" rel="external nofollow">HTML5, section 4.11.2</a></td> </tr> </tbody> </table> diff --git a/files/zh-cn/web/html/element/table/index.html b/files/zh-cn/web/html/element/table/index.html index 8511032381..ac7c7d5d12 100644 --- a/files/zh-cn/web/html/element/table/index.html +++ b/files/zh-cn/web/html/element/table/index.html @@ -91,7 +91,7 @@ translation_of: Web/HTML/Element/table <dl> <dt>{{htmlattrdef("bgcolor")}} {{Deprecated_inline}}</dt> - <dd>这个属性定义了表格的背景颜色。 它是一个6位的十六进制编码，定义于 <a class="external" href="http://www.w3.org/Graphics/Color/sRGB" title="http://www.w3.org/Graphics/Color/sRGB">sRGB</a>，需要加上'#'作为前缀。 当然也可以使用下面已经被预先定义的字符串，来表示常用的16种颜色： + <dd>这个属性定义了表格的背景颜色。 它是一个6位的十六进制编码，定义于 <a class="external" href="http://www.w3.org/Graphics/Color/sRGB">sRGB</a>，需要加上'#'作为前缀。 当然也可以使用下面已经被预先定义的字符串，来表示常用的16种颜色： <table> <tbody> <tr> diff --git a/files/zh-cn/web/html/element/time/index.html b/files/zh-cn/web/html/element/time/index.html index 3679df8d0f..0e5b97e110 100644 --- a/files/zh-cn/web/html/element/time/index.html +++ b/files/zh-cn/web/html/element/time/index.html @@ -35,7 +35,7 @@ translation_of: Web/HTML/Element/time </tr> <tr> <td>标准文档</td> - <td><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-time-element" rel="external nofollow" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-time-element">HTML5, section 4.6.10</a></td> + <td><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-time-element" rel="external nofollow">HTML5, section 4.6.10</a></td> </tr> </tbody> </table> @@ -46,7 +46,7 @@ translation_of: Web/HTML/Element/time <dl> <dt>{{ htmlattrdef("datetime") }}</dt> - <dd>该属性表示此元素的时间和日期，并且属性值必须是一个<a class="external" href="http://www.w3.org/TR/html5/common-microsyntaxes.html#valid-date-string-with-optional-time" title="http://www.w3.org/TR/html5/common-microsyntaxes.html#valid-date-string-with-optional-time">有效的日期格式，并可包含时间</a>。 如果此值不能被解析为日期，元素不会有一个关联的时间戳.</dd> + <dd>该属性表示此元素的时间和日期，并且属性值必须是一个<a class="external" href="http://www.w3.org/TR/html5/common-microsyntaxes.html#valid-date-string-with-optional-time">有效的日期格式，并可包含时间</a>。 如果此值不能被解析为日期，元素不会有一个关联的时间戳.</dd> <dt>{{ htmlattrdef("pubdate") }}</dt> <dd>(该属性仍在被WHATWG 和 W3C组织设计和讨论中.) This Boolean attribute specifies that the date and time given by the element is the publication date of a document. The document it applies to is either the nearest ancestor article element or the document as a whole (if there is no ancestor <a href="/zh-cn/HTML/Element/article" title="zh-cn/HTML/Element/Article">article</a> element). If true, the <code>time</code> element must have a corresponding date. Additionally, each <code>time</code> element indicating a publication date must be the only <code>time</code> element that does so for that document.</dd> </dl> diff --git a/files/zh-cn/web/html/element/video/index.html b/files/zh-cn/web/html/element/video/index.html index 544f902feb..dbaa58d81c 100644 --- a/files/zh-cn/web/html/element/video/index.html +++ b/files/zh-cn/web/html/element/video/index.html @@ -71,7 +71,7 @@ translation_of: Web/HTML/Element/video </tr> <tr> <td>规范文档</td> - <td><a class="external" href="http://www.w3.org/TR/html5/embedded-content-0.html#the-video-element" title="http://www.w3.org/TR/html5/video.html#video">HTML5, 4.8.6节</a></td> + <td><a class="external" href="http://www.w3.org/TR/html5/embedded-content-0.html#the-video-element">HTML5, 4.8.6节</a></td> </tr> </tbody> </table> @@ -283,7 +283,7 @@ AddType video/ogg .ogg <li><a href="/zh-CN/docs/Manipulating_video_using_canvas" title="Manipulating video using canvas">用canvas操作video</a></li> <li><a href="/zh-CN/docs/XPCOM_Interface_Reference/NsIDOMHTMLMediaElement" title="NsIDOMHTMLMediaElement"><code>nsIDOMHTMLMediaElement</code></a></li> <li><a class="external" href="http://tinyvid.tv/">TinyVid</a> - 在HTML5中使用ogg文件的例子。</li> - <li><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/#video" title="http://www.whatwg.org/specs/web-apps/current-work/#video"><code>video</code> 元素</a> (HTML5 规范)</li> + <li><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/#video"><code>video</code> 元素</a> (HTML5 规范)</li> <li><a href="/zh-CN/docs/Configuring_servers_for_Ogg_media" title="Configuring servers for Ogg media">Ogg 格式媒体文件的服务器配置</a></li> </ul> diff --git a/files/zh-cn/web/html/global_attributes/data-_star_/index.html b/files/zh-cn/web/html/global_attributes/data-_star_/index.html index ed5adaae8f..091b601686 100644 --- a/files/zh-cn/web/html/global_attributes/data-_star_/index.html +++ b/files/zh-cn/web/html/global_attributes/data-_star_/index.html @@ -12,7 +12,7 @@ translation_of: Web/HTML/Global_attributes/data-* <div>{{EmbedInteractiveExample("pages/tabbed/attribute-data.html","tabbed-standard")}}</div> -<p>所有这些自定义数据属性都可以通过所属元素的 {{domxref("HTMLElement")}} 接口来访问。 {{domxref("HTMLElement.dataset")}} 属性可以访问它们。 <code>*</code> 可以使用遵循 <a class="external" href="http://www.w3.org/TR/REC-xml/#NT-Name" title="http://www.w3.org/TR/REC-xml/#NT-Name">xml名称生产规则</a> 的任何名称来被替换，并具有以下限制：</p> +<p>所有这些自定义数据属性都可以通过所属元素的 {{domxref("HTMLElement")}} 接口来访问。 {{domxref("HTMLElement.dataset")}} 属性可以访问它们。 <code>*</code> 可以使用遵循 <a class="external" href="http://www.w3.org/TR/REC-xml/#NT-Name">xml名称生产规则</a> 的任何名称来被替换，并具有以下限制：</p> <ul> <li>该名称不能以<code>xml</code>开头，无论这些字母是大写还是小写；</li> diff --git a/files/zh-cn/web/html/quirks_mode_and_standards_mode/index.html b/files/zh-cn/web/html/quirks_mode_and_standards_mode/index.html index 6ea0826b47..c726d21f1d 100644 --- a/files/zh-cn/web/html/quirks_mode_and_standards_mode/index.html +++ b/files/zh-cn/web/html/quirks_mode_and_standards_mode/index.html @@ -31,7 +31,7 @@ translation_of: Web/HTML/Quirks_Mode_and_Standards_Mode <p>在 HTML5 中，DOCTYPE 唯一的作用是启用标准模式。更早期的 HTML 标准中，DOCTYPE 会附加其他意义，但没有任何浏览器会将 DOCTYPE 用于怪异模式和标准模式之间互换以外的用途。</p> -<p>另请参阅 <a class="external" href="http://hsivonen.iki.fi/doctype/" title="http://hsivonen.iki.fi/doctype/">when different browsers choose various modes</a> 的详细说明。</p> +<p>另请参阅 <a class="external" href="http://hsivonen.iki.fi/doctype/">when different browsers choose various modes</a> 的详细说明。</p> <h3 id="XHTML"><strong>XHTML</strong></h3> diff --git a/files/zh-cn/web/http/basics_of_http/data_uris/index.html b/files/zh-cn/web/http/basics_of_http/data_uris/index.html index 1373bc29dc..00c69d644e 100644 --- a/files/zh-cn/web/http/basics_of_http/data_uris/index.html +++ b/files/zh-cn/web/http/basics_of_http/data_uris/index.html @@ -68,7 +68,7 @@ YSBzbGlnaHRseSBsb25nZXIgdGVzdCBmb3IgdGV2ZXIK <dt>语法</dt> <dd><code>data</code> URLs 的格式很简单，但很容易会忘记把逗号加在 "data" 协议名后面，在对数据进行 base64 编码时也很容易发生错误。</dd> <dt>HTML代码格式化</dt> - <dd>一个 <code>data</code> URL 是一个文件中的文件，相对于文档来说这个文件可能就非常的长。因为 data URL 也是 URL，所以 data 会用空白符(换行符, 制表符, 空格)来对它进行格式化。但如果数据是经过 base64 编码的，就可能会<a class="external" href="http://bugzilla.mozilla.org/show_bug.cgi?id=73026#c12" title="http://bugzilla.mozilla.org/show_bug.cgi?id=73026#c12">遇到一些问题</a>。</dd> + <dd>一个 <code>data</code> URL 是一个文件中的文件，相对于文档来说这个文件可能就非常的长。因为 data URL 也是 URL，所以 data 会用空白符(换行符, 制表符, 空格)来对它进行格式化。但如果数据是经过 base64 编码的，就可能会<a class="external" href="http://bugzilla.mozilla.org/show_bug.cgi?id=73026#c12">遇到一些问题</a>。</dd> <dt>长度限制</dt> <dd>虽然 Firefox 支持无限长度的 <code>data</code> URLs，但是标准中并没有规定浏览器必须支持任意长度的 <code>data</code> URIs。比如，Opera 11浏览器限制 URLs 最长为 65535 个字符，这意味着 data URLs 最长为 65529 个字符（如果你使用纯文本 data:, 而不是指定一个 MIME 类型的话，那么 65529 字符长度是编码后的长度，而不是源文件）。</dd> <dt>缺乏错误处理</dt> diff --git a/files/zh-cn/web/http/content_negotiation/list_of_default_accept_values/index.html b/files/zh-cn/web/http/content_negotiation/list_of_default_accept_values/index.html index 0da28e9bf9..3b7288d8fc 100644 --- a/files/zh-cn/web/http/content_negotiation/list_of_default_accept_values/index.html +++ b/files/zh-cn/web/http/content_negotiation/list_of_default_accept_values/index.html @@ -42,7 +42,7 @@ original_slug: Web/HTTP/Content_negotiation/Accept_默认值 <tr> <td>Internet Explorer 8</td> <td><code>image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, application/x-shockwave-flash, application/msword, */*</code></td> - <td> 请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx" title="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a>.</td> + <td> 请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a>.</td> </tr> <tr> <td>Edge</td> @@ -87,12 +87,12 @@ original_slug: Web/HTTP/Content_negotiation/Accept_默认值 <tr> <td>Internet Explorer 8 及更早版本</td> <td><code>*/*</code></td> - <td> 请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx" title="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a></td> + <td> 请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a></td> </tr> <tr> <td>Internet Explorer 9</td> <td><code>image/png,image/svg+xml,image/*;q=0.8, */*;q=0.5</code></td> - <td>请参见 <a class="external" href="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx" title="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx">Fiddler is better with Internet Explorer 9 (IEInternals' MSDN blog)</a></td> + <td>请参见 <a class="external" href="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx">Fiddler is better with Internet Explorer 9 (IEInternals' MSDN blog)</a></td> </tr> </tbody> </table> @@ -189,12 +189,12 @@ original_slug: Web/HTTP/Content_negotiation/Accept_默认值 <tr> <td>Internet Explorer 8 及更早版本</td> <td><code>*/*</code></td> - <td>请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx" title="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a></td> + <td>请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a></td> </tr> <tr> <td>Internet Explorer 9</td> <td><code>application/javascript, */*;q=0.8</code></td> - <td>请参见 <a class="external" href="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx" title="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx">Fiddler is better with Internet Explorer 9 (IEInternals' MSDN blog)</a></td> + <td>请参见 <a class="external" href="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx">Fiddler is better with Internet Explorer 9 (IEInternals' MSDN blog)</a></td> </tr> </tbody> </table> @@ -223,12 +223,12 @@ original_slug: Web/HTTP/Content_negotiation/Accept_默认值 <tr> <td>Internet Explorer 8 及更早版本</td> <td><code>*/*</code></td> - <td>请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx" title="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a></td> + <td>请参见 <a class="external" href="http://blogs.msdn.com/b/ieinternals/archive/2009/07/01/ie-and-the-accept-header.aspx">IE and the Accept Header (IEInternals' MSDN blog)</a></td> </tr> <tr> <td>Internet Explorer 9</td> <td><code>text/css</code></td> - <td>请参见 <a class="external" href="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx" title="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx">Fiddler is better with Internet Explorer 9 (IEInternals' MSDN blog)</a></td> + <td>请参见 <a class="external" href="http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx">Fiddler is better with Internet Explorer 9 (IEInternals' MSDN blog)</a></td> </tr> <tr> <td>Chrome 12</td> diff --git a/files/zh-cn/web/http/cors/index.html b/files/zh-cn/web/http/cors/index.html index 80755243d5..cdd058c212 100644 --- a/files/zh-cn/web/http/cors/index.html +++ b/files/zh-cn/web/http/cors/index.html @@ -36,11 +36,11 @@ original_slug: Web/HTTP/Access_control_CORS <h2 id="什么情况下需要_CORS_？">什么情况下需要 CORS ？</h2> -<p>这份 <a class="external external-icon" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">cross-origin sharing standard</a> 允许在下列场景中使用跨站点 HTTP 请求：</p> +<p>这份 <a class="external external-icon" href="http://www.w3.org/TR/cors/">cross-origin sharing standard</a> 允许在下列场景中使用跨站点 HTTP 请求：</p> <ul> <li>前文提到的由 {{domxref("XMLHttpRequest")}} 或 <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API">Fetch</a> 发起的跨源 HTTP 请求。</li> - <li>Web 字体 (CSS 中通过<code> @font-face </code>使用跨源字体资源)，<a class="external external-icon" href="https://www.w3.org/TR/css-fonts-3/#font-fetching-requirements" title="https://www.w3.org/TR/css-fonts-3/#font-fetching-requirements">因此，网站就可以发布 TrueType 字体资源，并只允许已授权网站进行跨站调用</a>。</li> + <li>Web 字体 (CSS 中通过<code> @font-face </code>使用跨源字体资源)，<a class="external external-icon" href="https://www.w3.org/TR/css-fonts-3/#font-fetching-requirements">因此，网站就可以发布 TrueType 字体资源，并只允许已授权网站进行跨站调用</a>。</li> <li><a href="https://developer.mozilla.org/zh-CN/docs/Web/API/WebGL_API/Tutorial/Using_textures_in_WebGL">WebGL 贴图</a></li> <li>使用 <code><a href="https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/drawImage">drawImage</a></code> 将 Images/video 画面绘制到 canvas</li> </ul> @@ -258,7 +258,7 @@ Access-Control-Allow-Methods: POST, GET, OPTIONS Access-Control-Allow-Headers: X-PINGOTHER, Content-Type Access-Control-Max-Age: 86400</code></pre> -<p><font face="Open Sans, Arial, sans-serif">首部字段</font><code><font face="Open Sans, Arial, sans-serif"> </font>Access-Control-Allow-Methods </code>表明服务器允许客户端使用<code> </code><code>POST,</code> <code>GET </code>和 <code>OPTIONS</code> 方法发起请求。该字段与 <a class="external" href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.7" title="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.7">HTTP/1.1 Allow: response header</a> 类似，但仅限于在需要访问控制的场景中使用。</p> +<p><font face="Open Sans, Arial, sans-serif">首部字段</font><code><font face="Open Sans, Arial, sans-serif"> </font>Access-Control-Allow-Methods </code>表明服务器允许客户端使用<code> </code><code>POST,</code> <code>GET </code>和 <code>OPTIONS</code> 方法发起请求。该字段与 <a class="external" href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.7">HTTP/1.1 Allow: response header</a> 类似，但仅限于在需要访问控制的场景中使用。</p> <p>首部字段 <code>Access-Control-Allow-Headers </code>表明服务器允许请求中携带字段 <code><code>X-PINGOTHER </code></code>与<code><code> Content-Type</code></code>。<font face="Open Sans, Arial, sans-serif">与</font><code><code><font face="Open Sans, Arial, sans-serif"> </font></code></code><code>Access-Control-Allow-Methods </code>一样，<code><code>Access-Control-Allow-Headers</code></code> 的值为逗号分割的列表。</p> diff --git a/files/zh-cn/web/http/headers/index.html b/files/zh-cn/web/http/headers/index.html index 8a7cdd0e13..e23e0b0ac6 100644 --- a/files/zh-cn/web/http/headers/index.html +++ b/files/zh-cn/web/http/headers/index.html @@ -9,7 +9,7 @@ translation_of: Web/HTTP/Headers <p><strong>HTTP 消息头</strong>允许客户端和服务器通过<strong> request</strong>和<strong> response</strong>传递附加信息。一个请求头由名称（不区分大小写）后跟一个冒号“：”，冒号后跟具体的值（不带换行符）组成。该值前面的引导空白会被忽略。</p> -<p>自定专用消息头可通过'X-' 前缀来添加；但是这种用法被IETF在2012年6月发布的 <a href="https://tools.ietf.org/html/rfc6648">RFC6648</a> 中明确弃用，原因是其会在非标准字段成为标准时造成不便；其他的消息头在 <a class="external" href="http://www.iana.org/assignments/message-headers/perm-headers.html" title="http://www.iana.org/assignments/message-headers/perm-headers.html">IANA 注册表</a> 中列出, 其原始内容在 <a class="external" href="http://tools.ietf.org/html/rfc4229" title="http://tools.ietf.org/html/rfc4229">RFC 4229</a> 中定义。 此外，IANA 还维护着<a class="external" href="http://www.iana.org/assignments/message-headers/prov-headers.html" title="http://www.iana.org/assignments/message-headers/prov-headers.html">被提议的新HTTP 消息头注册表</a>.</p> +<p>自定专用消息头可通过'X-' 前缀来添加；但是这种用法被IETF在2012年6月发布的 <a href="https://tools.ietf.org/html/rfc6648">RFC6648</a> 中明确弃用，原因是其会在非标准字段成为标准时造成不便；其他的消息头在 <a class="external" href="http://www.iana.org/assignments/message-headers/perm-headers.html" title="http://www.iana.org/assignments/message-headers/perm-headers.html">IANA 注册表</a> 中列出, 其原始内容在 <a class="external" href="http://tools.ietf.org/html/rfc4229" title="http://tools.ietf.org/html/rfc4229">RFC 4229</a> 中定义。 此外，IANA 还维护着<a class="external" href="http://www.iana.org/assignments/message-headers/prov-headers.html">被提议的新HTTP 消息头注册表</a>.</p> <p>根据不同上下文，可将消息头分为：</p> @@ -88,49 +88,49 @@ translation_of: Web/HTTP/Headers <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Allow-Credentials" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Allow-Credentials">Access-Control-Allow-Credentials</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Allow-Origin" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Allow-Origin">Access-Control-Allow-Origin</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Allow-Methods" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Allow-Methods">Access-Control-Allow-Methods</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Allow-Headers" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Allow-Headers">Access-Control-Allow-Headers</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Max-Age" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Max-Age">Access-Control-Max-Age</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Expose-Header" title="en/HTTP access control#Access-Control-Expose-Header">Access-Control-Expose-Headers</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("2") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Request-Method" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Request-Method">Access-Control-Request-Method</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/HTTP_access_control#Access-Control-Request-Headers" title="https://developer.mozilla.org/En/HTTP_access_control#Access-Control-Request-Headers">Access-Control-Request-Headers</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td><a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td><a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/Web/HTTP/Headers/Age" title="en/Age">Age</a></code></td> @@ -220,7 +220,7 @@ translation_of: Web/HTTP/Headers <td><code><a href="/en-US/docs/Web/HTTP/Headers/Cookie" title="en/Cookie">Cookie</a></code></td> <td></td> <td></td> - <td><a class="external" href="http://www.ietf.org/rfc/rfc2109.txt" title="http://www.ietf.org/rfc/rfc2109.txt">RFC 2109</a></td> + <td><a class="external" href="http://www.ietf.org/rfc/rfc2109.txt">RFC 2109</a></td> </tr> <tr> <td><code>DNT</code></td> @@ -298,7 +298,7 @@ translation_of: Web/HTTP/Headers <td><code><a href="/en-US/docs/Web/HTTP/Headers/Last-Event-ID" title="en/Last-Event-ID">Last-Event-ID</a></code></td> <td>给出服务器在先前HTTP连接上接收的最后事件的ID。用于同步文本/事件流。</td> <td><a href="/en-US/docs/Server-sent_events" title="en/Server-Sent Events">Server-Sent Events</a></td> - <td><a class="external" href="http://dev.w3.org/html5/eventsource/" title="http://dev.w3.org/html5/eventsource/">Server-Sent Events spec</a></td> + <td><a class="external" href="http://dev.w3.org/html5/eventsource/">Server-Sent Events spec</a></td> </tr> <tr> <td><code><a href="/en-US/docs/Web/HTTP/Headers/Last-Modified" title="en/Last-Modified">Last-Modified</a></code></td> @@ -315,7 +315,7 @@ translation_of: Web/HTTP/Headers <p>For the <code>rel=prefetch</code> case, see <a href="/en-US/docs/Link_prefetching_FAQ" title="en/Link prefetching FAQ">Link Prefetching FAQ</a></p> </td> <td> - <p>Introduced in <a class="external" href="http://tools.ietf.org/html/rfc2068#section-19.6.2.4" title="http://tools.ietf.org/html/rfc2068#section-19.6.2.4">HTTP 1.1's RFC 2068, section 19.6.2.4</a>, it was removed in the final <a class="external" href="http://www.w3.org/Protocols/rfc2616/rfc2616.html" title="http://www.w3.org/Protocols/rfc2616/rfc2616.html">HTTP 1.1 spec</a>, then reintroduced, with some extensions, in <a class="external" href="http://greenbytes.de/tech/webdav/rfc5988.html">RFC 5988</a></p> + <p>Introduced in <a class="external" href="http://tools.ietf.org/html/rfc2068#section-19.6.2.4" title="http://tools.ietf.org/html/rfc2068#section-19.6.2.4">HTTP 1.1's RFC 2068, section 19.6.2.4</a>, it was removed in the final <a class="external" href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">HTTP 1.1 spec</a>, then reintroduced, with some extensions, in <a class="external" href="http://greenbytes.de/tech/webdav/rfc5988.html">RFC 5988</a></p> </td> </tr> <tr> @@ -340,7 +340,7 @@ translation_of: Web/HTTP/Headers <td><code><a href="/en-US/docs/HTTP_access_control#Origin" title="https://developer.mozilla.org/En/HTTP_access_control#Origin">Origin</a></code></td> <td></td> <td><a href="/en-US/docs/HTTP_access_control" title="En/HTTP access control">HTTP Access Control</a> and <a href="/en-US/docs/Server-Side_Access_Control" title="En/Server-Side Access Control">Server Side Access Control</a>{{ gecko_minversion_inline("1.9.1") }}</td> - <td>More recently defined in the <a href="https://fetch.spec.whatwg.org/#http-extensions">Fetch spec</a> (see <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a>.) Originally defined in <a class="external" href="http://www.w3.org/TR/cors/" title="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> + <td>More recently defined in the <a href="https://fetch.spec.whatwg.org/#http-extensions">Fetch spec</a> (see <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a>.) Originally defined in <a class="external" href="http://www.w3.org/TR/cors/">W3C Cross-Origin Resource Sharing</a></td> </tr> <tr> <td><code><a href="/en-US/docs/Web/HTTP/Headers/Pragma" title="en/Pragma">Pragma</a></code></td> @@ -384,31 +384,31 @@ translation_of: Web/HTTP/Headers <td><code>Sec-Websocket-Extensions</code></td> <td></td> <td></td> - <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07" title="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> + <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> </tr> <tr> <td><code>Sec-Websocket-Key</code></td> <td></td> <td></td> - <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07" title="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> + <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> </tr> <tr> <td><code>Sec-Websocket-Origin</code></td> <td></td> <td></td> - <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07" title="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> + <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> </tr> <tr> <td><code>Sec-Websocket-Protocol</code></td> <td></td> <td></td> - <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07" title="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> + <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> </tr> <tr> <td><code>Sec-Websocket-Version</code></td> <td></td> <td></td> - <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07" title="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> + <td> <a class="external" href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07">Websockets</a></td> </tr> <tr> <td><code><a href="/en-US/docs/Web/HTTP/Headers/Server" title="en/Server">Server</a></code></td> @@ -420,19 +420,19 @@ translation_of: Web/HTTP/Headers <td><code><a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie" title="en/Set-Cookie">Set-Cookie</a></code></td> <td></td> <td></td> - <td><a class="external" href="http://www.ietf.org/rfc/rfc2109.txt" title="http://www.ietf.org/rfc/rfc2109.txt">RFC 2109</a></td> + <td><a class="external" href="http://www.ietf.org/rfc/rfc2109.txt">RFC 2109</a></td> </tr> <tr> <td><code><a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie2" title="en/Set-Cookie2">Set-Cookie2</a></code></td> <td></td> <td></td> - <td><a class="external" href="http://www.ietf.org/rfc/rfc2965.txt" title="http://www.ietf.org/rfc/rfc2965.txt">RFC 2965</a></td> + <td><a class="external" href="http://www.ietf.org/rfc/rfc2965.txt">RFC 2965</a></td> </tr> <tr> <td><code>Strict-Transport-Security</code></td> <td></td> <td><a href="/en-US/docs/Security/HTTP_Strict_Transport_Security" title="en/Security/HTTP Strict Transport Security">HTTP Strict Transport Security</a></td> - <td><a class="external" href="http://tools.ietf.org/html/draft-hodges-strict-transport-sec-02" title="http://tools.ietf.org/html/draft-hodges-strict-transport-sec-02">IETF reference</a></td> + <td><a class="external" href="http://tools.ietf.org/html/draft-hodges-strict-transport-sec-02">IETF reference</a></td> </tr> <tr> <td><code>TCN</code></td> @@ -452,7 +452,7 @@ translation_of: Web/HTTP/Headers <p>列出将在消息正文之后在尾部块中传输的头。这允许服务器计算一些值，如Content-MD5：在传输数据时。请注意，Trailer：标头不得列出Content-Length :, Trailer：或Transfer-Encoding：headers。</p> </td> <td></td> - <td><a class="external" href="http://tools.ietf.org/html/rfc2616#section-14.40" title="http://tools.ietf.org/html/rfc2616#section-14.40">RFC 2616, §14.40</a></td> + <td><a class="external" href="http://tools.ietf.org/html/rfc2616#section-14.40">RFC 2616, §14.40</a></td> </tr> <tr> <td><code><a href="/en-US/docs/Web/HTTP/Headers/Transfer-Encoding" title="en/Transfer-Encoding">Transfer-Encoding</a></code></td> diff --git a/files/zh-cn/web/http/headers/user-agent/firefox/index.html b/files/zh-cn/web/http/headers/user-agent/firefox/index.html index 284ff8599a..2e70d22e31 100644 --- a/files/zh-cn/web/http/headers/user-agent/firefox/index.html +++ b/files/zh-cn/web/http/headers/user-agent/firefox/index.html @@ -344,7 +344,7 @@ Mozilla/5.0 (Android 4.4; <strong>Tablet</strong>; rv:41.0) Gecko/41.0 Firefox/4 <h2 id="参见">参见</h2> <ul> - <li><a href="http://lawrencemandel.com/2012/07/27/decision-made-firefox-os-user-agent-string/">Firefox OS User Agent</a> （参考博客文章以及 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=777710" title="https://bugzilla.mozilla.org/show_bug.cgi?id=777710">bug 777710</a>）</li> + <li><a href="http://lawrencemandel.com/2012/07/27/decision-made-firefox-os-user-agent-string/">Firefox OS User Agent</a> （参考博客文章以及 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=777710">bug 777710</a>）</li> <li><a class="external" href="https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/" title="Final User Agent string for Firefox 4">Firefox 4 的最终 User Agent</a>（博客文章）</li> <li><a href="/en/Browser_Detection_and_Cross_Browser_Support" title="en/Browser_Detection_and_Cross_Browser_Support">检测UA字符串以获得跨浏览器支持</a></li> <li><a href="../../../../en/DOM/window.navigator.userAgent" rel="internal">window.navigator.userAgent</a></li> diff --git a/files/zh-cn/web/http/headers/x-dns-prefetch-control/index.html b/files/zh-cn/web/http/headers/x-dns-prefetch-control/index.html index fa88398051..5cec7c1430 100644 --- a/files/zh-cn/web/http/headers/x-dns-prefetch-control/index.html +++ b/files/zh-cn/web/http/headers/x-dns-prefetch-control/index.html @@ -75,7 +75,7 @@ X-DNS-Prefetch-Control: off <pre class="brush: html"><link rel="dns-prefetch" href="http://www.spreadfirefox.com/"> </pre> -<p>在这个例子中，Firefox 将预解析域名"<a class="linkification-ext external" href="http://www.spreadfirefox.com" title="Linkification: http://www.spreadfirefox.com">www.spreadfirefox.com</a>"。</p> +<p>在这个例子中，Firefox 将预解析域名"<a class="linkification-ext external" href="http://www.spreadfirefox.com">www.spreadfirefox.com</a>"。</p> <p>而且，{{ HTMLElement("link") }} 元素也可以使用不完整的 URL 的主机名来标记预解析，但这些主机名前必需要有双斜线：</p> diff --git a/files/zh-cn/web/http/headers/x-frame-options/index.html b/files/zh-cn/web/http/headers/x-frame-options/index.html index cbc5c27c07..9a50a060ff 100644 --- a/files/zh-cn/web/http/headers/x-frame-options/index.html +++ b/files/zh-cn/web/http/headers/x-frame-options/index.html @@ -154,7 +154,7 @@ app.use(frameguard({ action: 'sameorigin' })) <ul> <li><a href="/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors"><code>frame-ancestors</code> (CSP)</a></li> <li><a href="https://tools.ietf.org/html/rfc7034">HTTP Header Field X-Frame-Options - RFC 7034</a></li> - <li><a class="external" href="http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-clickjacking-defenses.aspx" title="http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-clickjacking-defenses.aspx">ClickJacking Defenses - IEBlog</a></li> - <li><a href="http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx" title="http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx">Combating ClickJacking with X-Frame-Options - IEInternals</a></li> - <li><a href="https://w3c.github.io/webappsec/specs/content-security-policy/#directive-frame-ancestors" title="https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html#frame-src">CSP Level 2 frame-ancestors directive</a></li> + <li><a class="external" href="http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-clickjacking-defenses.aspx">ClickJacking Defenses - IEBlog</a></li> + <li><a href="http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx">Combating ClickJacking with X-Frame-Options - IEInternals</a></li> + <li><a href="https://w3c.github.io/webappsec/specs/content-security-policy/#directive-frame-ancestors">CSP Level 2 frame-ancestors directive</a></li> </ul> diff --git a/files/zh-cn/web/http/link_prefetching_faq/index.html b/files/zh-cn/web/http/link_prefetching_faq/index.html index d930f142f0..7d2842221f 100644 --- a/files/zh-cn/web/http/link_prefetching_faq/index.html +++ b/files/zh-cn/web/http/link_prefetching_faq/index.html @@ -33,7 +33,7 @@ translation_of: Web/HTTP/Link_prefetching_FAQ <pre class="eval"><meta http-equiv="Link" content="</images/big.jpeg>; rel=prefetch"> </pre> -<p><code>Link:</code> header 的格式在 <a class="external" href="http://tools.ietf.org/html/rfc5988" title="http://tools.ietf.org/html/rfc5988">RFC 5988</a> section 5 中有所描述。</p> +<p><code>Link:</code> header 的格式在 <a class="external" href="http://tools.ietf.org/html/rfc5988">RFC 5988</a> section 5 中有所描述。</p> <p>浏览器检查所有这些预取提示，并将每一个独立的请求排到队列之中，然后浏览器空闲时将对这些请求进行预取。每个页面都可以有多个预取提示，因为预取多个文档是合理的。例如，未来要访问的页面可能包含多张大图。</p> @@ -55,7 +55,7 @@ translation_of: Web/HTTP/Link_prefetching_FAQ <h3 id="How_is_browser_idle_time_determined.3F" name="How_is_browser_idle_time_determined.3F">浏览器的空闲时间是如何确定的？</h3> -<p>在目前(Moilla 1.2)，空闲时间的确定是通过 <code>nsIWebProgressListener</code> API 实现的。我们在顶层 <code>nsIWebProgress 对象</code> ("@<a class="linkification-ext external" href="http://mozilla.org/docloaderservice;1" title="Linkification: http://mozilla.org/docloaderservice;1">mozilla.org/docloaderservice;1</a>") 上附加了一个监听器。通过监听器，我们能够收到文档开始和停止的通知，从而将最后一个文档停止到下一个文档开始之间的间隔作为空闲时间的近似值。最后一个文档停止的通知大致会在顶层文档的 onLoad 方法即将被触发时发出。此时即是开始预取的时间点。如果一个子文档包含了预取提示，这些预取操作将会等到最顶层文档和其子文档完成加载后才会开始进行。</p> +<p>在目前(Moilla 1.2)，空闲时间的确定是通过 <code>nsIWebProgressListener</code> API 实现的。我们在顶层 <code>nsIWebProgress 对象</code> ("@<a class="linkification-ext external" href="http://mozilla.org/docloaderservice;1">mozilla.org/docloaderservice;1</a>") 上附加了一个监听器。通过监听器，我们能够收到文档开始和停止的通知，从而将最后一个文档停止到下一个文档开始之间的间隔作为空闲时间的近似值。最后一个文档停止的通知大致会在顶层文档的 onLoad 方法即将被触发时发出。此时即是开始预取的时间点。如果一个子文档包含了预取提示，这些预取操作将会等到最顶层文档和其子文档完成加载后才会开始进行。</p> <h3 id="What_happens_if_I_click_on_a_link_while_something_is_being_prefetched.3F" name="What_happens_if_I_click_on_a_link_while_something_is_being_prefetched.3F">资源正在被预载时点击了某个链接会发生什么？</h3> @@ -112,7 +112,7 @@ translation_of: Web/HTTP/Link_prefetching_FAQ <h3 id="Privacy_implications" name="Privacy_implications">隐私问题</h3> -<p>除了上面已经提到的引用和URL跟随含义外，预取通常会导致访问预取站点的cookie。 （例如，如果您使用google amazon，则google结果页面将预取www.amazon.com，从而导致amazon cookie来回发送。您可以在Firefox中阻止第三方cookie，请参参阅 <a class="external" href="http://support.mozilla.com/en-US/kb/Disabling%20third%20party%20cookies" title="http://support.mozilla.com/en-US/kb/Disabling third party cookies">Disabling third party cookies</a>。）</p> +<p>除了上面已经提到的引用和URL跟随含义外，预取通常会导致访问预取站点的cookie。 （例如，如果您使用google amazon，则google结果页面将预取www.amazon.com，从而导致amazon cookie来回发送。您可以在Firefox中阻止第三方cookie，请参参阅 <a class="external" href="http://support.mozilla.com/en-US/kb/Disabling%20third%20party%20cookies">Disabling third party cookies</a>。）</p> <h3 id="What_about....3F" name="What_about....3F">关于...？</h3> diff --git a/files/zh-cn/web/mathml/authoring/index.html b/files/zh-cn/web/mathml/authoring/index.html index 96e7263797..17654f3f36 100644 --- a/files/zh-cn/web/mathml/authoring/index.html +++ b/files/zh-cn/web/mathml/authoring/index.html @@ -191,7 +191,7 @@ m|math { ... </pre> -<p><a href="https://math.etsu.edu/LaTeXMathML/" title="http://math.etsu.edu/LaTeXMathML/">LaTeXMathML</a> is a similar script that allows to parse more LaTeX commands. The installation is similar: copy <a href="https://math.etsu.edu/LaTeXMathML/LaTeXMathML.js">LaTeXMathML.js</a> and <a href="https://math.etsu.edu/LaTeXMathML/LaTeXMathML.standardarticle.css">LaTeXMathML.standardarticle.css</a>, add links in the header of your document and the LaTeX content of your Web page marked by the "LaTeX" class will be automatically parsed and converted to HTML+MathML:</p> +<p><a href="https://math.etsu.edu/LaTeXMathML/">LaTeXMathML</a> is a similar script that allows to parse more LaTeX commands. The installation is similar: copy <a href="https://math.etsu.edu/LaTeXMathML/LaTeXMathML.js">LaTeXMathML.js</a> and <a href="https://math.etsu.edu/LaTeXMathML/LaTeXMathML.standardarticle.css">LaTeXMathML.standardarticle.css</a>, add links in the header of your document and the LaTeX content of your Web page marked by the "LaTeX" class will be automatically parsed and converted to HTML+MathML:</p> <pre class="brush: html"><span><<span class="start-tag">head</span>></span> <span>... diff --git a/files/zh-cn/web/progressive_web_apps/responsive/responsive_design_building_blocks/index.html b/files/zh-cn/web/progressive_web_apps/responsive/responsive_design_building_blocks/index.html index fa8fc121d3..37d5126d13 100644 --- a/files/zh-cn/web/progressive_web_apps/responsive/responsive_design_building_blocks/index.html +++ b/files/zh-cn/web/progressive_web_apps/responsive/responsive_design_building_blocks/index.html @@ -26,7 +26,7 @@ translation_of: Web/Progressive_web_apps/Responsive/responsive_design_building_b <p>We've written a simple-but-fun prototype for an application called Snapshot, which takes a video stream from your webcam (using {{domxref("navigator.getUserMedia", "getUserMedia()")}}) then allows you to capture stills from that video stream (using HTML5 {{HTMLElement("canvas")}}), and save them to a gallery. You can then view previously-captured images and delete them. Other articles will discuss the functionality in more detail, but here we're interested in the layout.</p> <div class="note"> -<p><strong>Note:</strong> You can find the <a href="https://github.com/chrisdavidmills/snapshot" title="https://github.com/chrisdavidmills/snapshot">Snapshot app on Github</a>; check out the code and help improve it. You can also see <a href="https://chrisdavidmills.github.io/snapshot/">Snapshot running live</a>. Note that <code>getUserMedia()</code> is an experimental technology, which currently only works in Google Chrome and Firefox desktop. More functionality and a clean up of the styling of Snapshot are planned for a future date.</p> +<p><strong>Note:</strong> You can find the <a href="https://github.com/chrisdavidmills/snapshot">Snapshot app on Github</a>; check out the code and help improve it. You can also see <a href="https://chrisdavidmills.github.io/snapshot/">Snapshot running live</a>. Note that <code>getUserMedia()</code> is an experimental technology, which currently only works in Google Chrome and Firefox desktop. More functionality and a clean up of the styling of Snapshot are planned for a future date.</p> </div> <p>Our desktop layout for Snapshot is three columns, containing the camera viewer, image capture view, and gallery, respectively.</p> @@ -83,7 +83,7 @@ x-card:nth-child(3) { box-sizing: border-box; }</pre> -<p>This basically means that {{cssxref("width")}} and {{cssxref("height")}} will now set the dimensions of an element all the way up to and including the border, not just the content. So if you set <code>width: 40%</code>, the box width will always be <code>40%</code> of its parent, and any {{cssxref("padding")}} and {{cssxref("border")}} widths set on the box will be subtracted from the content width, not added to it. Very useful! Read more about this at <a href="http://www.paulirish.com/2012/box-sizing-border-box-ftw/" title="http://www.paulirish.com/2012/box-sizing-border-box-ftw/">* { Box-sizing: Border-box } FTW</a>, by Paul Irish.</p> +<p>This basically means that {{cssxref("width")}} and {{cssxref("height")}} will now set the dimensions of an element all the way up to and including the border, not just the content. So if you set <code>width: 40%</code>, the box width will always be <code>40%</code> of its parent, and any {{cssxref("padding")}} and {{cssxref("border")}} widths set on the box will be subtracted from the content width, not added to it. Very useful! Read more about this at <a href="http://www.paulirish.com/2012/box-sizing-border-box-ftw/">* { Box-sizing: Border-box } FTW</a>, by Paul Irish.</p> <h2 id="Flexible_replaced_elements">Flexible replaced elements</h2> @@ -232,7 +232,7 @@ x-card:nth-child(3) { <p>Last, we have used <code>flex: 1;</code> to make the buttons always take up the same proportion of space on the line. Let's have a look at the mobile layout, in the below image.</p> -<p><img alt="single column layout for mobile app view, with three buttons to navigate between cards, an image viewer, and a Save Picture button at the button." src="https://mdn.mozillademos.org/files/5939/mobile-layout.png" style="float: left; height: 417px; margin-right: 2rem; width: 304px;">But there are more tricks up our sleeves for this mobile app layout! As mentioned above, we used <a href="http://mozilla.github.io/brick/" title="http://mozilla.github.io/brick/">Mozilla Brick</a>, a collection of ready-rolled mobile UI components, in the making of the mobile app layout. In particular, we used the <a href="http://mozilla.github.io/brick/docs.html#deck">deck</a> component for the nice transition effect between cards when the buttons are pressed. For more on using Brick, read <a href="/en-US/docs/Web/Apps/app_layout/Mozilla_Brick_ready_made_UI_components" title="/en-US/docs/Web/Apps/app_layout/Mozilla_Brick_ready_made_UI_components">Mozilla Brick: ready made UI components</a>.</p> +<p><img alt="single column layout for mobile app view, with three buttons to navigate between cards, an image viewer, and a Save Picture button at the button." src="https://mdn.mozillademos.org/files/5939/mobile-layout.png" style="float: left; height: 417px; margin-right: 2rem; width: 304px;">But there are more tricks up our sleeves for this mobile app layout! As mentioned above, we used <a href="http://mozilla.github.io/brick/">Mozilla Brick</a>, a collection of ready-rolled mobile UI components, in the making of the mobile app layout. In particular, we used the <a href="http://mozilla.github.io/brick/docs.html#deck">deck</a> component for the nice transition effect between cards when the buttons are pressed. For more on using Brick, read <a href="/en-US/docs/Web/Apps/app_layout/Mozilla_Brick_ready_made_UI_components" title="/en-US/docs/Web/Apps/app_layout/Mozilla_Brick_ready_made_UI_components">Mozilla Brick: ready made UI components</a>.</p> <p>What's more relevant to this article is that we didn't want the Brick CSS and JavaScript files being applied to the markup unless we were looking at the mobile app view. To achieve this, we applied the Brick CSS to the page using a separate {{HTMLElement("link")}} element with a <code>media</code> attribute:</p> @@ -325,7 +325,7 @@ x-card:nth-child(3) { <p>This causes our browser to render our mobile app layout properly — <code>width=480</code> tells the browser <em>"render this markup at 480 pixels wide"</em>, hence the media queries kick in appropriately. There are many more options available in the viewport meta tag, which you can read about in <a href="/en-US/docs/Mozilla/Mobile/Viewport_meta_tag" title="/en-US/docs/Mozilla/Mobile/Viewport_meta_tag">Using the viewport meta tag to control layout on mobile browsers</a>.</p> <div class="note"> -<p><strong>Note:</strong> There is a spec called <a href="http://dev.w3.org/csswg/css-device-adapt/" title="http://dev.w3.org/csswg/css-device-adapt/">device adaptation</a>, which defines the same functionality but in CSS, using a <code>@viewport</code> at-rule. This is probably a more logical place to put such information, but the spec is not as well supported as the viewport meta tag, therefore you should stick with that for now.</p> +<p><strong>Note:</strong> There is a spec called <a href="http://dev.w3.org/csswg/css-device-adapt/">device adaptation</a>, which defines the same functionality but in CSS, using a <code>@viewport</code> at-rule. This is probably a more logical place to put such information, but the spec is not as well supported as the viewport meta tag, therefore you should stick with that for now.</p> </div> <h2 class="cleared" id="Responsive_imagesvideo">Responsive images/video</h2> @@ -364,7 +364,7 @@ x-card:nth-child(3) { }</span></code> </span><span class="pln"> </span><span class="pun">}</span></code></pre> -<p>This looks rather complicated, but really it's not — we are providing a number of media query options, as at this time different browsers support different resolution media query types and even units. Brett Jankord has a good explanation at <a href="http://www.brettjankord.com/2012/11/28/cross-browser-retina-high-resolution-media-queries/" title="http://www.brettjankord.com/2012/11/28/cross-browser-retinahigh-resolution-media-queries/">Cross Browser Retina/High Resolution Media Queries</a>.</p> +<p>This looks rather complicated, but really it's not — we are providing a number of media query options, as at this time different browsers support different resolution media query types and even units. Brett Jankord has a good explanation at <a href="http://www.brettjankord.com/2012/11/28/cross-browser-retina-high-resolution-media-queries/">Cross Browser Retina/High Resolution Media Queries</a>.</p> <h3 id="<video>"><video></h3> @@ -388,13 +388,13 @@ x-card:nth-child(3) { <h3 id="<img>"><img></h3> -<p>HTML images are a more difficult proposition. There is no mechanism inherent in HTML images for serving different image files dependent on viewport size, and, due to a number of irksome browser behavior realities, solutions are more difficult to hack together than you would imagine. There are currently some standards proposals in the works that would provide this — the W3C <a href="http://www.w3.org/community/respimg/" title="http://www.w3.org/community/respimg/">responsive images community group</a> discussed this problem for ages and arrived at the <a href="http://www.w3.org/TR/html-picture-element/" title="http://www.w3.org/TR/html-picture-element/"><picture></a> element, which provides a similar markup structure to {{HTMLElement("video")}}<a href="/en-US/docs/Web/HTML/Element/video" title="/en-US/docs/Web/HTML/Element/video">,</a> with {{HTMLElement("source")}} alternatives selectable via media query results. Another proposal, <a href="http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/" title="http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/">srcset</a>, was put forward by Apple and takes a slightly different approach, instead providing a new <code>srcset</code> attribute for {{HTMLElement("img")}} inside which image references are placed along with "hints" that the browser can use to work out which image is most suitable to display given its viewport size, resolution, etc. These are not intended to be mutually exclusive.</p> +<p>HTML images are a more difficult proposition. There is no mechanism inherent in HTML images for serving different image files dependent on viewport size, and, due to a number of irksome browser behavior realities, solutions are more difficult to hack together than you would imagine. There are currently some standards proposals in the works that would provide this — the W3C <a href="http://www.w3.org/community/respimg/" title="http://www.w3.org/community/respimg/">responsive images community group</a> discussed this problem for ages and arrived at the <a href="http://www.w3.org/TR/html-picture-element/" title="http://www.w3.org/TR/html-picture-element/"><picture></a> element, which provides a similar markup structure to {{HTMLElement("video")}}<a href="/en-US/docs/Web/HTML/Element/video" title="/en-US/docs/Web/HTML/Element/video">,</a> with {{HTMLElement("source")}} alternatives selectable via media query results. Another proposal, <a href="http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/">srcset</a>, was put forward by Apple and takes a slightly different approach, instead providing a new <code>srcset</code> attribute for {{HTMLElement("img")}} inside which image references are placed along with "hints" that the browser can use to work out which image is most suitable to display given its viewport size, resolution, etc. These are not intended to be mutually exclusive.</p> <p>This all sounds good. But those solutions are definitely not ready for production yet — both are in a very early stage of standardization, and have no support across browsers. Currently we have to rely on various polyfills and other solutions, none of which are perfect for all situations, so you need to decide which one is right for your particular situation. Some available solutions are as follows:</p> <dl> <dt><a href="https://github.com/teleject/hisrc">HiSRC</a></dt> - <dd>A <a href="http://jquery.com" title="http://jquery.com">jQuery</a> plugin that allows you to create small, medium, and large versions of an image, and then serves the appropriate one according to the browser's resolution and available network speed.</dd> + <dd>A <a href="http://jquery.com">jQuery</a> plugin that allows you to create small, medium, and large versions of an image, and then serves the appropriate one according to the browser's resolution and available network speed.</dd> <dt><a href="http://www.mobify.com/mobifyjs/v2/docs/capturing/">Mobify.js capturing</a></dt> <dd>A very clever technique from Mozilla that allows you to capture the source of the page before it's parsed. This way, you can swap out image <code>src</code> values with JavaScript depending on browser features, circumventing browser preloading issues. This is promising, but doesn't work very well across older browsers.</dd> <dt><a href="https://github.com/scottjehl/picturefill">Picturefill</a></dt> diff --git a/files/zh-cn/web/security/same-origin_policy/index.html b/files/zh-cn/web/security/same-origin_policy/index.html index 1e39d736b5..187de63a8d 100644 --- a/files/zh-cn/web/security/same-origin_policy/index.html +++ b/files/zh-cn/web/security/same-origin_policy/index.html @@ -111,7 +111,7 @@ translation_of: Web/Security/Same-origin_policy <ul> <li><code><script src="..."></script></code> 标签嵌入跨域脚本。语法错误信息只能被同源脚本中捕捉到。</li> - <li><code><link rel="stylesheet" href="..."></code> 标签嵌入CSS。由于CSS的<a href="http://scarybeastsecurity.blogspot.dk/2009/12/generic-cross-browser-cross-domain.html">松散的语法规则</a>，CSS的跨域需要一个设置正确的 HTTP 头部 <code>Content-Type</code> 。不同浏览器有不同的限制：<span> </span><a href="http://msdn.microsoft.com/zh-CN/library/ie/gg622939%28v=vs.85%29.aspx">IE</a><span>, </span><a href="http://www.mozilla.org/security/announce/2010/mfsa2010-46.html" title="http://www.mozilla.org/security/announce/2010/mfsa2010-46.html">Firefox</a><span>, </span><a href="http://code.google.com/p/chromium/issues/detail?id=9877" title="http://code.google.com/p/chromium/issues/detail?id=9877">Chrome</a><span>, </span><a href="http://support.apple.com/kb/HT4070" title="http://support.apple.com/kb/HT4070">Safari</a><span> (跳至CVE-2010-0051)部分 和 </span><a href="http://www.opera.com/support/kb/view/943/" title="http://www.opera.com/support/kb/view/943/">Opera</a>。</li> + <li><code><link rel="stylesheet" href="..."></code> 标签嵌入CSS。由于CSS的<a href="http://scarybeastsecurity.blogspot.dk/2009/12/generic-cross-browser-cross-domain.html">松散的语法规则</a>，CSS的跨域需要一个设置正确的 HTTP 头部 <code>Content-Type</code> 。不同浏览器有不同的限制：<span> </span><a href="http://msdn.microsoft.com/zh-CN/library/ie/gg622939%28v=vs.85%29.aspx">IE</a><span>, </span><a href="http://www.mozilla.org/security/announce/2010/mfsa2010-46.html" title="http://www.mozilla.org/security/announce/2010/mfsa2010-46.html">Firefox</a><span>, </span><a href="http://code.google.com/p/chromium/issues/detail?id=9877" title="http://code.google.com/p/chromium/issues/detail?id=9877">Chrome</a><span>, </span><a href="http://support.apple.com/kb/HT4070" title="http://support.apple.com/kb/HT4070">Safari</a><span> (跳至CVE-2010-0051)部分 和 </span><a href="http://www.opera.com/support/kb/view/943/">Opera</a>。</li> <li>通过 {{htmlelement("img")}} 展示的图片。支持的图片格式包括PNG,JPEG,GIF,BMP,SVG,...</li> <li>通过 {{htmlelement("video")}} 和 {{htmlelement("audio")}} 播放的多媒体资源。</li> <li>通过 <code><a href="https://developer.mozilla.org/zh-CN/docs/HTML/Element/object" title="HTML/Element/object"><object></a></code>、 <a href="https://developer.mozilla.org/zh-CN/docs/HTML/Element/embed" title="HTML/Element/embed"><code><embed></code></a> 和 <code><a href="https://developer.mozilla.org/zh-CN/docs/HTML/Element/applet" title="HTML/Element/applet"><applet></a></code> 嵌入的插件。</li> @@ -133,7 +133,7 @@ translation_of: Web/Security/Same-origin_policy <h2 id="跨源脚本API访问">跨源脚本API访问</h2> -<p>JavaScript 的 API 中，如<span> </span><code><a href="https://developer.mozilla.org/zh-CN/docs/DOM/HTMLIFrameElement" title="DOM/HTMLIFrameElement">iframe.contentWindow</a></code>、<span> {{domxref("window.parent")}}、{{domxref("window.open")}} 和 {{domxref("window.opener")}} 允许文档间直接相互引用。当两个文档的源不同时，这些引用方式将对</span><span> </span><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#security-window" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#security-window">Window</a><span> 和 </span><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#security-location" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#security-location">Location</a>对象的访问添加限制，如下两节所述。</p> +<p>JavaScript 的 API 中，如<span> </span><code><a href="https://developer.mozilla.org/zh-CN/docs/DOM/HTMLIFrameElement" title="DOM/HTMLIFrameElement">iframe.contentWindow</a></code>、<span> {{domxref("window.parent")}}、{{domxref("window.open")}} 和 {{domxref("window.opener")}} 允许文档间直接相互引用。当两个文档的源不同时，这些引用方式将对</span><span> </span><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#security-window" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#security-window">Window</a><span> 和 </span><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#security-location">Location</a>对象的访问添加限制，如下两节所述。</p> <p>为了能让不同源中文档进行交流，可以使用 {{domxref("window.postMessage")}}。</p> @@ -257,7 +257,7 @@ translation_of: Web/Security/Same-origin_policy <h2 id="参见">参见</h2> <ul> - <li><a href="http://www.w3.org/Security/wiki/Same_Origin_Policy" title="http://www.w3.org/Security/wiki/Same_Origin_Policy">Same-Origin Policy at W3C</a></li> + <li><a href="http://www.w3.org/Security/wiki/Same_Origin_Policy">Same-Origin Policy at W3C</a></li> <li><a href="http://web.dev/secure/same-origin-policy">http://web.dev/secure/same-origin-policy</a></li> </ul> diff --git a/files/zh-cn/web/svg/attribute/mask/index.html b/files/zh-cn/web/svg/attribute/mask/index.html index d357ccf8a8..ff53cdecff 100644 --- a/files/zh-cn/web/svg/attribute/mask/index.html +++ b/files/zh-cn/web/svg/attribute/mask/index.html @@ -31,7 +31,7 @@ translation_of: Web/SVG/Attribute/mask </tr> <tr> <th scope="row">规范文档</th> - <td><a class="external" href="http://www.w3.org/TR/SVG/masking.html#MaskProperty" title="hhttp://www.w3.org/TR/SVG/masking.html#MaskProperty">SVG 1.1 (2nd Edition)</a></td> + <td><a class="external" href="http://www.w3.org/TR/SVG/masking.html#MaskProperty">SVG 1.1 (2nd Edition)</a></td> </tr> </tbody> </table> diff --git a/files/zh-cn/web/svg/content_type/index.html b/files/zh-cn/web/svg/content_type/index.html index d8a28f6f80..e61998aefc 100644 --- a/files/zh-cn/web/svg/content_type/index.html +++ b/files/zh-cn/web/svg/content_type/index.html @@ -96,7 +96,7 @@ DIGIT ::= [0-9] <dd> <p>基本类型<color>是一个CSS2兼容的规范，针对sRGB颜色空间的颜色。<color>应用在SVG的属性 {{SVGAttr("color")}} 上，也是属性{{SVGAttr("fill")}}、属性{{SVGAttr("stroke")}}、属性{{SVGAttr("stop-color")}}、属性 {{SVGAttr("flood-color")}}和属性{{SVGAttr("lighting-color")}}的定义的组成部分，<color>还提供了可选的基于ICC的颜色规范。</p> - <p>SVG支持所有的定义在<a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/syndata.html#value-def-color" title="http://www.w3.org/TR/2008/REC-CSS2-20080411/syndata.html#value-def-color">CSS2句法和基本数据类型</a>中的<color>供选择的句法，而且还支持<a href="http://www.w3.org/TR/css3-color/">CSS Color Module Level 3</a>中的<color>句法（取决于编译器）。</p> + <p>SVG支持所有的定义在<a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/syndata.html#value-def-color">CSS2句法和基本数据类型</a>中的<color>供选择的句法，而且还支持<a href="http://www.w3.org/TR/css3-color/">CSS Color Module Level 3</a>中的<color>句法（取决于编译器）。</p> <p>一个<color>可以是一个关键词，或者一个数字化的RGB规范。</p> @@ -111,7 +111,7 @@ DIGIT ::= [0-9] hexdigit ::= [0-9A-Fa-f] </pre> - <p>在这里，color-keyword要于匹配列于<a href="http://www.w3.org/TR/css3-color/" title="http://www.w3.org/TR/css3-color/">CSS Color Module Level 3</a>中的颜色关键词（大小写不敏感）中的一个，要么匹配列于<a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/ui.html#system-colors">对颜色的用户参考</a>中的一个。</p> + <p>在这里，color-keyword要于匹配列于<a href="http://www.w3.org/TR/css3-color/">CSS Color Module Level 3</a>中的颜色关键词（大小写不敏感）中的一个，要么匹配列于<a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/ui.html#system-colors">对颜色的用户参考</a>中的一个。</p> <p>SVG DOM对<color>的定义，CSS中也做了同样的定义。SVG对颜色的扩展，包括指定基于ICC的颜色的能力，可以使用DOM接口{{domxref("SVGColor")}}来表现。</p> </dd> |