1 files changed, 0 insertions, 93 deletions
diff --git a/files/zh-cn/mozilla/firefox/releases/23/site_compatibility/index.html b/files/zh-cn/mozilla/firefox/releases/23/site_compatibility/index.html
deleted file mode 100644
index b2bb77a090..0000000000
--- a/files/zh-cn/mozilla/firefox/releases/23/site_compatibility/index.html
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Site Compatibility for Firefox 23
-slug: Mozilla/Firefox/Releases/23/Site_compatibility
-translation_of: Mozilla/Firefox/Releases/23/Site_compatibility
-original_slug: Site_Compatibility_for_Firefox_23
----
-<div>{{FirefoxSidebar}}</div><p>{{ draft() }}</p>
-<p>Firefox 23 <a href="http://www.mozilla.org/en-US/firefox/aurora/">Aurora</a> (pre-Beta) was released on <time datetime="2013-05-17">May 17, 2013</time>. While it has been developed to maintain compatibility as much as possible, the new version includes some changes affecting backward compatibility aimed at improving interoperability with the other browsers or following the latest Web standards. Here's the list of such changes — Hope this helps whenever you test your sites or applications.</p>
-<p><strong>This article only explains the changes that may affect backward compatibility for Websites</strong>. For the other new features and changes, please read the following documents:</p>
-<ul>
-  <li><a href="http://www.mozilla.org/en-US/firefox/23.0a2/auroranotes/">Firefox 23 Aurora Release Notes</a></li>
-  <li><a href="/en-US/docs/Mozilla/Firefox/Releases/23">Firefox 23 for developers</a></li>
-</ul>
-<p>This list may be updated until the release of the final version on <time datetime="2013-08-06">August 6, 2013</time>, so please check back later.</p>
-<section id="sect1">
-  <h2 id="CSS">CSS</h2>
-  <section id="sect2">
-    <h3 id="能产生文字闪烁效果的text-decorationblink属性值被删除">能产生文字闪烁效果的<code>text-decoration:blink</code>属性值被删除</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=857820">Bug 857820 – Drop only blink effect from text-decoration: blink; and completely remove &lt;blink&gt; element</a></li>
-    </ul>
-    <p>Firefox previously supported the Netscape-derived blink effect with the <code>blink</code> keyword for the CSS <a href="/en-US/docs/Web/CSS/text-decoration"><code>text-decoration</code></a> property as well as the HTML <a href="/en-US/docs/Web/HTML/Element/blink"><code>blink</code></a> element and the DOM <a href="/en-US/docs/JavaScript/Reference/Global_Objects/String/blink"><code>String.blink</code></a> method. Starting with Firefox 23, the blink effect no longer works. While <code>text-decoration:blink</code> continues to be supported by the CSS parser and the DOM APIs, the HTML parser has dropped the <code>blink</code> element support, thus the element will be treated as an unknown element. Internet Explorer, Chrome and Safari haven't supported the effect. Opera may also drop the support once it switches to the Blink rendering engine.</p>
-  </section>
-</section>
-<section id="sect7">
-  <h2 id="DOM">DOM</h2>
-  <section id="sect8">
-    <h3 id="添加到侧边栏的功能被删除">添加到侧边栏的功能被删除</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=691647">Bug 691647 – clean up nsISidebar (remove window.sidebar.addPanel/addPersistentPanel)</a></li>
-    </ul>
-    <p><code>window.sidebar.addPanel</code> and <code>window.sidebar.addPersistentPanel</code> are no longer supported. These methods were a part of a Netscape-derived API which allowed Web publishers to integrate their contents as sidebar panels of the browser. They were not standardized, rarely used, and not very well supported. No other browsers have implemented these.</p>
-    <p>There is also a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=862147">plan</a> to remove <a href="/en-US/docs/Web/API/window.sidebar"><code>window.sidebar</code></a> itself in the future.</p>
-  </section>
-  <section id="sect9">
-    <h3 id="requestAnimationFrame脱前缀"><code>requestAnimationFrame</code>脱前缀</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=704063">Bug 704063 – Add unprefixed requestAnimationFrame</a></li>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=753453">Bug 753453 – requestAnimationFrame callback should return DOMHighResTimeStamp</a></li>
-    </ul>
-    <p><a href="/en-US/docs/Web/API/window.requestAnimationFrame"><code>requestAnimationFrame</code></a>, the unprefixed version of <code>mozRequestAnimationFrame</code>, has been added. This unprefixed method passes a <a href="/en-US/docs/Web/API/DOMHighResTimeStamp"><code>DOMHighResTimeStamp</code></a> to callbacks. It has microsecond precision and can be compared to <a href="/en-US/docs/Web/API/window.performance.now"><code>performance.now()</code></a>.</p>
-    <p>On the other hand, the prefixed method, which will be removed in the future, continues to pass an epoch-based <a href="/en-US/docs/Web/API/DOMTimeStamp"><code>DOMTimeStamp</code></a> to callbacks. The passed-in value has millisecond precision and can be compared to <a href="/en-US/docs/Web/API/window.mozAnimationStartTime"><code>mozAnimationStartTime</code></a>.</p>
-  </section>
-  <section id="sect10">
-    <h3 id="跨域文档的contentDocument属性现在返回null">跨域文档的<code>contentDocument</code>属性现在返回<code>null</code></h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=829872">Bug 829872 – Consider returning null from contentDocument getters when the caller does not subsume the document</a></li>
-    </ul>
-    <p>The <code>contentDocument</code> property on frames now returns <a href="/en-US/docs/JavaScript/Reference/Global_Objects/null"><code>null</code></a> if the caller doesn't subsume the document. This change affects the <code>contentDocument</code> property on the <a href="/en-US/docs/Web/HTML/Element/frame"><code>frame</code></a>, <a href="/en-US/docs/Web/HTML/Element/iframe"><code>iframe</code></a> and <a href="/en-US/docs/Web/HTML/Element/object"><code>object</code></a> elements as well as the <code>getSVGDocument</code> method on the <a href="/en-US/docs/Web/HTML/Element/embed"><code>embed</code></a>, <code>iframe</code> and <code>object</code> elements.</p>
-  </section>
-  <section id="sect13">
-    <h3 id="window.defaultStatus被删除"><code>window.defaultStatus</code>被删除</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=862917">Bug 862917 – Remove window.defaultStatus</a></li>
-    </ul>
-    <p>The <a href="/en-US/docs/Web/API/window.defaultStatus"><code>window.defaultStatus</code></a> property is no longer available. Setting this property has had no effect in Firefox because the default preference has disallowed changes to the status text by Web pages. Recently, the Firefox UI dropped support for enabling that pref. Also, this property is not specified in the HTML5 spec. <a href="/en-US/docs/Web/API/window.status"><code>window.status</code></a> is still available.</p>
-  </section>
-  <section id="sect14">
-    <h3 id="不再允许创建AnimationEvent和TransitionEvent">不再允许创建<code>AnimationEvent</code><code>和TransitionEvent</code></h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=868751">Bug 868751 – Remove support for document.createEvent("AnimationEvent"), document.createEvent("TransitionEvent"), AnimationEvent.initAnimationEvent, and TransitionEvent.initTransitionEvent</a></li>
-    </ul>
-    <p>The support for obsolete <code>document.createEvent("AnimationEvent")</code>, <code>document.createEvent("TransitionEvent")</code>, <a href="/en-US/docs/Web/API/AnimationEvent#initAnimationEvent%28%29"><code>AnimationEvent.initAnimationEvent</code></a>, and <code>TransitionEvent.initTransitionEvent</code> has been removed.</p>
-  </section>
-</section>
-<section id="sect15">
-  <h2 id="视频和音频">视频和音频</h2>
-  <section id="sect16">
-    <h3 id="Audio_Data_API被废弃">Audio Data API被废弃</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=855570">Bug 855570 – Deprecate Audio Data API</a></li>
-    </ul>
-    <p>The non-standard, experimental <a href="/en-US/docs/Introducing_the_Audio_API_Extension">Audio Data API</a> is now considered deprecated. The standard <a href="/en-US/docs/Web_Audio_API">Web Audio API</a> can be used instead.</p>
-  </section>
-  <section id="sect17">
-    <h3 id="HTMLMediaElement.initialTime被删除"><code>HTMLMediaElement.initialTime</code>被删除</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=742537">Bug 742537 – Remove HTMLMediaElement.initialTime</a></li>
-    </ul>
-    <p>The <code>HTMLMediaElement.initialTime</code> property is no longer available, due to the removal from the spec.</p>
-  </section>
-</section>
-<section id="sect18">
-  <h2 id="安全和隐私">安全和隐私</h2>
-  <section id="sect19">
-    <h3 id="在SSL页面(HTTPS)上的非SSL活动内容会被默认阻止">在SSL页面(HTTPS)上的非SSL活动内容会被默认阻止</h3>
-    <ul>
-      <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=834836">Bug 834836 – Turn on pref to block mixed active content</a></li>
-    </ul>
-    <p><a href="/en-US/docs/Site_Compatibility_for_Firefox_18">Firefox 18</a> introduced preferences to block loading content from non-SSL (<code>http</code>) sites on SSL (<code>https</code>) pages. One of those preferences, <code>security.mixed_content.block_active_content</code> is now enabled by default in order to enhance user security. That means insecure scripts, stylesheets, plug-in contents, inline frames, <a href="/en-US/docs/Web/CSS/@font-face">Web fonts</a> and <a href="/en-US/docs/WebSockets">WebSockets</a> are blocked on secure pages, and a notification is displayed instead. It will <strong>not</strong> block "display content" like images, videos or audio. See <a href="https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/">Tanvi Vyas' blog post</a> for details.</p>
-    <p>Mozilla is tracking mixed content issues found on <a href="https://bugzilla.mozilla.org/showdependencytree.cgi?id=844556">major sites</a> as well as <a href="https://bugzilla.mozilla.org/showdependencytree.cgi?id=843977">its own properties</a>.</p>
-  </section>
-</section>