Fixes #1634 - remove old compat site for zh-CN and zh-TW

1 files changed, 0 insertions, 240 deletions

diff --git a/files/zh-cn/mozilla/firefox/releases/68/index.html b/files/zh-cn/mozilla/firefox/releases/68/index.html
deleted file mode 100644
index 621bd205fb..0000000000
--- a/files/zh-cn/mozilla/firefox/releases/68/index.html
+++ /dev/null
@@ -1,240 +0,0 @@
----
-title: 为开发者的 Firefox 68 文档
-slug: Mozilla/Firefox/Releases/68
-translation_of: Mozilla/Firefox/Releases/68
----
-<p>{{FirefoxSidebar}}</p>
-
-<p class="summary">本篇文章将提供关于在Firefox 68版本中，会影响到开发人员的更新的信息。Firefox 68版本发布于2019年7月9日。</p>
-
-<h2 id="面向开发者的变更">面向开发者的变更</h2>
-
-<h3 id="开发者工具">开发者工具</h3>
-
-<h4 id="浏览器网页控制台">浏览器/网页控制台</h4>
-
-<ul>
- <li>现在网页控制台会展现更多关于CSS警告的信息, 其中包括使用该规则的DOM元素的节点列表 ({{bug(1093953)}})。</li>
- <li>您可以在网页控制台中使用常规的表达式来过滤内容({{bug(1441079)}})。</li>
- <li>现在浏览器控制台允许您通过设置勾选或不勾选名为“显示内容消息”的复选框来显示或隐藏来自内容进程的消息({{bug(1260877)}})。</li>
-</ul>
-
-<h4 id="JavaScript_调试器">JavaScript 调试器</h4>
-
-<ul>
- <li>您现在可以在调试器中通过点击 <kbd>Shift</kbd> + <kbd>Ctrl</kbd> + <kbd>F</kbd> (Windows or Linux) 或 <kbd>Shift</kbd> + <kbd>Cmd</kbd> + <kbd>F</kbd> (macOS)在当前项目的所有文件进行 <a href="/en-US/docs/Tools/Debugger/How_to/Search#Searching_in_all_files">搜索</a> ({{bug(1320325)}})。</li>
-</ul>
-
-<h4 id="网络监视器">网络监视器</h4>
-
-<ul>
- <li>网络监视器的 <a href="/en-US/docs/Tools/Network_Monitor/request_list#Filtering_requests">请求列表(request list)</a> 现在允许您封锁特定的URL地址 ({{bug(1151368)}})。</li>
- <li>您现在不需要通过编辑方法、URL、参数和页眉的方式，而是可以通过使用在内容目录的 <a href="/en-US/docs/Tools/Network_Monitor/request_list#Context_menu">“重新发送（Resend）”</a> 命令，来重新发送一个网络请求 ({{bug(1422014)}})。</li>
- <li>网络监视器内容目录里的 <a href="https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor/request_details#Headers">“页眉（Headers）”</a> 标签现在允许您以JSON格式，复制全部或部分页眉信息到剪切板 ({{bug(1442249)}})。</li>
-</ul>
-
-<h4 id="页面查看器">页面查看器</h4>
-
-<ul>
- <li>一个允许您切换任何打印媒体查询 (print media queries) 显示的按钮已被添加页面查看器的<a href="/en-US/docs/Tools/Page_Inspector/How_to/Examine_and_edit_CSS#Examine_CSS_rules"> “规则仪表盘（rules panel）”</a> ({{bug(1534984)}})。</li>
- <li> <a href="/en-US/docs/Tools/Page_Inspector/How_to/Edit_fonts">“字体仪表盘（fonts panel）”</a> 现在已包括一个可以调整<code>字母间距</code>的滑条 ({{bug(1536237)}}).</li>
- <li>一个警告标志会出现在包含无效值的、不被支持的CSS属性或规则, 以帮助您了解为何某个特定的风格没有被渲染 ({{bug(1306054)}})。</li>
-</ul>
-
-<h4 id="存储查看器">存储查看器</h4>
-
-<ul>
- <li>您现在可以通过选中在存储查看器的项目并点击退格键来 <a href="/en-US/docs/Tools/Storage_Inspector#Local_storage_Session_storage">删除本地和对话期存储</a> 词目 ({{bug(1522893)}})。</li>
-</ul>
-
-<h4 id="其它">其它</h4>
-
-<ul>
- <li><a href="/en-US/docs/Tools/Accessibility_inspector">访问性查看器</a> 现在包含了一个新的 “<em>检查问题（Check for issues</em>）” 的特性, 其中包括很多可以高亮显示您的网页的访问性问题的检查工具。第一个可用的检查是<em>对比 （contrast）</em>, 用于突出颜色对比问题。</li>
- <li>在 <a href="/en-US/docs/Tools/about:debugging">about:debugging</a> 页面的控制内部拓展可视性（系统附加组件和隐藏拓展）的偏好已由 <code>devtools.aboutdebugging.showSystemAddons</code> 变为 <code>devtools.aboutdebugging.showHiddenAddons</code> ({{bug(1544372)}}).</li>
- <li><a href="/en-US/docs/Tools/Responsive_Design_Mode">响应设计模式（Responsive design mode</a>）已被重新设计— <em>设备设置</em> 对话框 (device selection menu &gt; <em>Edit List...</em>) 现在使用起来更加直观简单 ({{bug(1487857)}})。</li>
-</ul>
-
-<h4 id="移除">移除</h4>
-
-<ul>
- <li>"Enable add-on debugging" 复选框已从 <a href="/en-US/docs/Tools/about:debugging">about:debugging</a> 页面移除 ({{bug(1544813)}})。</li>
-</ul>
-
-<h3 id="HTML">HTML</h3>
-
-<ul>
- <li>如果文本轨迹包含媒体元素，那么{{HTMLElement("track")}} 元素 — 由 {{domxref("HTMLTrackElement")}} 展现— 现在会收到除了{{domxref("TextTrack")}} 它本身外，{{domxref("HTMLTrackElement.cuechange_event", "cuechange")}} 事件({{bug(1548731)}})。</li>
- <li>尽管有不同的表现，{{htmlelement("link")}} 元素已重新支持 <code>disabled</code> 属性。 当 <code>disabled</code> 被设定在一个连同<code>rel="stylesheet"</code> 的 <code>&lt;link&gt;</code> 元素 , 引用的样式表不会在页面加载时被加载, 当 <code>disabled</code> 属性被改变为 <code>false</code> 或移除时，该样表会被加载 ({{bug(1281135)}})。</li>
-</ul>
-
-<h4 id="移除_2"> 移除</h4>
-
-<ul>
- <li>不再支持 <code><a href="/en-US/docs/Web/HTML/Element/meta">&lt;meta http-equiv="set-cookie"&gt;</a></code>  ({{bug(1457503)}})。</li>
-</ul>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li><a href="/en-US/docs/Web/CSS/CSS_Scroll_Snap">CSS Scroll Snapping</a> has been updated to the latest version of the specification ({{bug(1312163)}}) and ({{bug(1544136)}}), this includes:
-
-  <ul>
-   <li>The <code>scroll-padding</code> properties ({{bug(1373832)}})</li>
-   <li>The <code>scroll-margin</code> properties ({{bug(1373833)}})</li>
-   <li>{{CSSxRef("scroll-snap-align")}} ({{bug(1373835)}})</li>
-  </ul>
- </li>
- <li>The {{CSSxRef("-webkit-line-clamp")}} property has been implemented for compatibility with other browsers ({{bug(866102)}}).</li>
- <li>Support has been added for the {{CSSxRef("::marker")}} pseudo-element ({{bug(205202)}}) and animation for <code>::marker</code> pseudos ({{bug(1538618)}})</li>
- <li>We changed {{CSSxRef("currentColor")}} to be a computed value (except for the {{cssxref("color")}} property)  ({{bug(760345)}}).</li>
- <li>Support has been fixed for the <code>ch</code> length unit so it now matches the spec (fallback for no '0' glyph, vertical metrics) ({{bug(282126)}})</li>
- <li>The  {{CSSxRef("counter-set")}} property has been implemented. ({{bug(1518201)}}).</li>
- <li>We now implement list numbering using a built-in "list-item" counter; this fixes list numbering bugs ({{bug(288704)}}).</li>
- <li>Selector matching and parsing support has been implemented for <code><a href="/en-US/docs/Web/CSS/::part">::part()</a></code> ({{bug(1545430)}}) and ({{bug(1545425)}}).</li>
- <li><a href="/en-US/docs/Web/CSS/CSS_Transforms">CSS Transforms</a> are now supported in indirectly rendered things e.g.)  {{SVGElement("mask")}},  {{SVGElement("marker")}},  {{SVGElement("pattern")}},  {{SVGElement("clipPath")}} ({{bug(1323962)}}).</li>
- <li>
-  <p>While we're keeping the prefixed versions of the various gradient properties ({{cssxref("linear-gradient")}}, {{cssxref("radial-gradient")}}, and {{cssxref("repeating-radial-gradient")}} available for compatibility reasons, we have revised how they're parsed so that they're handled much more like the non-prefixed versions. This means that certain existing styles won't work correctly.</p>
-
-  <p>In particular, the complicated syntax taking both an angle and a position will no longer work, and the <code>to</code> keyword in the <code>&lt;side-or-corner&gt;</code> parameter is not required for the prefixed gradient properties. You are encouraged to use the standard, non-prefixed gradient properties instead, as they're now widely supported ({{bug(1547939)}}).</p>
- </li>
-</ul>
-
-<h4 id="Removals">Removals</h4>
-
-<ul>
- <li>{{CSSxRef("scroll-snap-coordinate")}}, {{CSSxRef("scroll-snap-destination")}}, {{CSSxRef("scroll-snap-type-x")}} and {{CSSxRef("scroll-snap-type-y")}} have been removed.</li>
- <li>The {{CSSxRef("scroll-snap-type")}} property has become a longhand, so the old shorthand syntax like <code>scroll-snap-type:mandatory</code> will stop working. See the <a href="https://www.fxsitecompat.com/en-CA/docs/2019/legacy-css-scroll-snap-syntax-support-has-been-dropped/">Firefox Site Compatability</a> note.</li>
-</ul>
-
-<h3 id="SVG">SVG</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<ul>
- <li>The new {{jsxref("BigInt")}} primitive is enabled by default ({{bug(1527902)}}).</li>
- <li>String generic methods have been removed ({{bug(1222552)}}). See the <a href="/en-US/docs/Web/JavaScript/Reference/Errors/Deprecated_String_generics">deprecation warning</a> for more information.</li>
-</ul>
-
-<h3 id="APIs">APIs</h3>
-
-<h4 id="CSS_Object_Model_CSSOM">CSS Object Model (CSSOM)</h4>
-
-<ul>
- <li>The legacy {{domxref("CSSStyleSheet.rules", "rules")}} property and {{domxref("CSSStyleSheet.addRule", "addRule()")}} and {{domxref("CSSStyleSheet.removeRule", "removeRule()")}} methods have been added to the {{domxref("CSSStyleSheet")}} interface. These were introduced by Internet Explorer 9 and have never managed to quite be stamped out, so they have been added to improve compatibility with the small percentage of sites that still use them ({{bug(1545823)}}).</li>
-</ul>
-
-<h4 id="DOM">DOM</h4>
-
-<ul>
- <li>The <a href="/en-US/docs/Web/API/Visual_Viewport_API">Visual Viewport API</a> has now been enabled by default on Android ({{bug(1512813)}}). Adding this API to desktop versions of Firefox is being tracked in {{bug(1551302)}}.</li>
- <li>The {{domxref("Window")}} feature <code><a href="/en-US/docs/Web/API/Window/open#noreferrer">noreferrer</a></code> is now supported; if specified, the new window's content is loaded without sharing the hostname, IP address, URL, or other identifying information about the host device ({{bug(1527287)}}).</li>
- <li>The {{domxref("HTMLImageElement.decode", "decode()")}} method on <code>HTMLImageElement</code> is now implemented. This can be used to trigger loading and decoding of an image prior to adding it to the DOM ({{bug(1501794)}}).</li>
- <li>{{domxref("XMLHttpRequest")}} has been updated to no longer accept the non-standard <code>moz-chunked-arraybuffer</code> value for {{domxref("XMLHttpRequest.responseType", "responseType")}}. Code still using it should be updated to <a href="/en-US/docs/Web/API/Streams_API/Using_readable_streams#Consuming_a_fetch_as_a_stream">use the Fetch API as a stream</a> ({{bug(1120171)}}).</li>
- <li><code>XMLHttpRequest</code> now outputs a warning to console if you perform a synchronous request while handling an {{domxref("Window.unload_event", "unload")}}, {{domxref("Window.beforeunload_event", "beforeunload")}}, or {{domxref("Window.pagehide_event", "pagehide")}} event ({{bug(980902)}}).</li>
- <li>The {{domxref("Document.cookie", "cookie")}} property has moved from the {{domxref("HTMLDocument")}} interface to the {{domxref("Document")}} interface, allowing documents other than {{Glossary("HTML")}} to use cookies ({{bug(144795)}}).</li>
- <li>The {{domxref("HTMLElement.focus()")}} and {{domxref("SVGElement.focus()")}} methods now accept an optional object that may contain a boolean <code>preventScroll</code> option specifying whether or not to block the browser from scrolling the newly-focused element into view ({{bug(1374045)}}).</li>
-</ul>
-
-<h4 id="DOM_events">DOM events</h4>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Firefox_for_Android">Firefox for Android</a> no longer incorrectly sends a {{domxref("Window.resize_event", "resize")}} event until after the first frame is painted; this improves web compatibility with sites that don't expect this event to occur ({{bug(1528052)}}).</li>
- <li>The dispatching of events for non-primary mouse buttons has been made to more closely follow the specification; the {{domxref("Element.click_event", "click")}} event is no longer sent when non-primary buttons are clicked, instead using {{domxref("Element.auxclick_event", "auxclick")}}. In addition, {{domxref("Element.dblclick_event", "dblclick")}} no longer fires for non-primary buttons ({{bug(1379466)}}).</li>
- <li>The proprietary {{domxref("MouseEvent.mozPressure")}} property has been deprecated, and will now trigger a warning in the console ({{bug(1165211)}}).</li>
-</ul>
-
-<h4 id="Media_Web_Audio_and_WebRTC">Media, Web Audio, and WebRTC</h4>
-
-<ul>
- <li>Due to changes in the Google Play store's policies, starting with Firefox 68 for Android, the OpenH264 codec used to handle AVC/H.264 video in WebRTC connections can no longer be downloaded and installed. Therefore, fresh installs of Firefox on Android devices no longer support AVC in WebRTC calls. If you upgrade from earlier versions of Firefox and already have the codec downloaded, it will continue to work. This does <em>not</em> affect other platforms. For more details, see <a href="https://support.mozilla.org/en-US/kb/firefox-android-openh264">this article on SUMO</a> or {{bug(1548679)}}.</li>
- <li>WebRTC has been updated to recognize that a <code>null</code> candidate passed into the {{domxref("RTCPeerConnection.icecandidate", "icecandidate")}} event handler, indicating the receipt of a candidate, instead indicates that there are no further candidates coming; when this happens the ICE gathering ({{domxref("RTCPeerConnection.iceGatheringState", "iceGatheringState")}}) state reaches <code>complete</code> ({{bug(1318167)}}).</li>
- <li>The {{domxref("RTCRtpReceiver")}} methods {{domxref("RTCRtpReceiver.getContributingSources", "getContributingSources()")}} and {{domxref("RTCRtpReceiver.getSynchronizationSources", "getSynchronizationSources()")}} now support video tracks; previously they only worked on audio ({{bug(1534466)}}).</li>
- <li>The Web Audio API {{domxref("MediaStreamTrackAudioSourceNode")}} interface is now supported, as is the method {{domxref("AudioContext.createMediaStreamTrackSource()")}} ({{bug(1324548)}}).</li>
- <li>{{domxref("RTCDataChannel.negotiated")}} is now implemented ({{bug(1529695)}}).</li>
- <li>The {{domxref("MediaStreamAudioSourceNode.MediaStreamAudioSourceNode", "MediaStreamAudioSourceNode()")}} constructor has been updated to match the current specification's definition that the "first audio track" in the stream is the track whose ID comes first in lexicographical order ({{bug(1324548)}}).</li>
- <li>
-  <p>{{domxref("MediaDevices.getUserMedia", "getUserMedia()")}} may no longer be used from a non-secure context; attempting to do so now throws a <code>NotAllowedError</code> exception. Secure contexts are those loaded using HTTPS, those located using the <code>file:///</code> scheme, and those loaded from <code>localhost</code>. For now, if you must, you can re-enable the ability to perform insecure calls to <code>getUserMedia()</code> by setting the preference <code>media.getusermedia.insecure.enabled</code> to <code>true</code> ({{bug(1335740)}}).</p>
-
-  <div class="blockIndicator note">
-  <p><strong>Note:</strong> In the future, Firefox will also remove the {{domxref("navigator.mediaDevices")}} property on insecure contexts, preventing all access to the {{domxref("MediaDevices")}} APIs. <strong>This is already the case in Nightly builds.</strong></p>
-  </div>
- </li>
-</ul>
-
-<h4 id="Removals_2">Removals</h4>
-
-<ul>
- <li>Removed the non-standard {{DOMxRef("XMLDocument.load()")}} method ({{bug(332175)}}).</li>
- <li>Removed the non-standard {{DOMxRef("XMLDocument.async")}} property ({{bug(1328138)}}).</li>
- <li>The {{domxref("RTCIceCredentialType")}} <code>token</code> value has been removed ({{bug(1529595)}}).</li>
-</ul>
-
-<h3 id="HTTP">HTTP</h3>
-
-<ul>
- <li>The <a href="/en-US/docs/Web/HTTP">HTTP</a> {{HTTPHeader("Clear-Site-Data")}} header no longer supports the <code>executionContexts</code> directive. This was removed due to problems with interactions between interconnections among different kinds of data at different points in the navigation process and the way the specification is designed. It <a href="https://github.com/w3c/webappsec-clear-site-data/issues/59">has been proposed</a> that this directive be removed from the specification for this reason, among others ({{bug(1548034)}}).</li>
-</ul>
-
-<h4 id="Removals_3">Removals</h4>
-
-<ul>
- <li>The {{HTTPHeader("Content-Security-Policy")}} directive <code>require-sri-for</code> is no longer supported due to concerns about its standardization status. It was previously available only behind a preference, which was off by default ({{bug(1386214)}}).</li>
-</ul>
-
-<h3 id="Security">Security</h3>
-
-<ul>
- <li>Due to <a href="https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730">CVE-2019-11730: Same-origin policy treats all files in a directory as having the same-origin</a>, changes have been made so that Firefox now treats files in the same directory as being from different origins. This has a number of side-effects on what will work in documents loaded via file:// URLs (see {{bug("file-fallout")}} for useful background research). For example, workers can no longer be loaded.</li>
-</ul>
-
-<h3 id="WebDriver_conformance_Marionette">WebDriver conformance (Marionette)</h3>
-
-<h4 id="Bug_fixes">Bug fixes</h4>
-
-<ul>
- <li>If <code>WebDriver:SwitchToWindow</code> changes the selection to a different window it now waits for its <code>focus</code> and <code>activate</code> events before returning ({{bug(1335085)}}).</li>
- <li>Fixed the <code>TypeError: this.tabModal is null</code> failure, which sometimes appeared when interacting with modal dialogs or user prompts ({{bug(1538782)}})</li>
-</ul>
-
-<h4 id="Other">Other</h4>
-
-<ul>
- <li>Disabled the feature to force unloading background tabs on low memory conditions, to prevent top-level browser contexts from magically disappearing ({{bug(1553748)}}).</li>
- <li>Disabled priviledged content processes that caused HTTP authentication dialogs not to appear when navigating to a website after opening a new tab ({{bug(1558763)}}).</li>
-</ul>
-
-<h3 id="Plugins">Plugins</h3>
-
-<p><em>No changes.</em></p>
-
-<h2 id="Changes_for_add-on_developers">Changes for add-on developers</h2>
-
-<h3 id="API_changes">API changes</h3>
-
-<ul>
- <li>The The <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/register">proxy.register()</a></code> and <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/unregister">proxy.unregister()</a></code> functions have been deprecated and will be removed from Firefox 71 ({{bug(1545811)}}).</li>
- <li>A <code>boolean</code> flag, <code>incognito</code>, has been added to the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/RequestDetails">proxy.RequestDetails</a>. object. When <code>true</code>, it indicates that this was a private browsing request ({{bug(1545163)}}).</li>
- <li>The <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/RequestFilter">webRequest.RequestFilter</a> parameters can include an incognito parameter. If provided, requests that do not match the incognito state (<code>true</code> or <code>false</code>) will be filtered out ({{bug(1548177)}}).</li>
- <li>A <code>string</code> value, <code>cookieStoreId</code>, representing the cookie store ID of the current context, has been added to the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/RequestDetails">proxy.RequestDetails</a>. object ({{bug(1545420)}}).</li>
- <li>When an add-on attempts to add a bookmark folder to the root folder, the resulting error message is now much more intuitive ({{bug(1512171)}}).</li>
- <li>The promise returned by <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/duplicate">browser.tabs.duplicate()</a></code> now resolves immediately, before the tabs are completely loaded ({{bug(1394376)}}).</li>
- <li>Support has been added for chrome.storage.managed, allowing web extension settings to be implemented via enterprise policy ({{bug(1230802)}}).</li>
- <li>There is now a Group Policy option to blacklist <em>all</em> extensions except the ones that have been whitelisted ({{bug(1522823)}}).</li>
-</ul>
-
-<h3 id="显著变更">显著变更</h3>
-
-<p><em>无变更。</em></p>
-
-<h2 id="还可以看看">还可以看看</h2>
-
-<ul>
- <li><a href="https://www.fxsitecompat.com/en-CA/versions/68/">Site compatibility for Firefox 68</a></li>
-</ul>
-
-<h2 id="更早的版本">更早的版本</h2>
-
-<p>{{Firefox_for_developers(67)}}</p>