1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
---
title: Site Compatibility for Firefox 26
slug: Mozilla/Firefox/Releases/26/Site_Compatibility
translation_of: Mozilla/Firefox/Releases/26/Site_Compatibility
---
<div>{{FirefoxSidebar}}</div><p>{{ draft() }}</p>
<p>Firefox 26 <a href="http://www.mozilla.org/en-US/firefox/aurora/">Aurora</a> (pre-Beta) will be released on <time datetime="2013-09-20">September 20, 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="/en-US/docs/Mozilla/Firefox/Releases/26">Firefox 26 for developers</a></li>
</ul>
<p>This list may be updated until the release of the final version on <time datetime="2013-12-10">December 10, 2013</time>, so please check back later. Follow <a href="https://twitter.com/MozWebCompat">@MozWebCompat</a> on Twitter for further updates.</p>
<section id="sect1">
<h2 id="CSS">CSS</h2>
<section id="sect2">
<h3 id="-moz-text-blink_has_been_removed_in_favor_of_-moz-text-decoration-lineblink"><code>-moz-text-blink</code> has been removed in favor of <code>-moz-text-decoration-line:blink</code></h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=812995">Bug 812995 – add 'blink' to -moz-text-decoration-line and drop -moz-text-blink</a></li>
</ul>
<p>The non-standard {{ cssxref("-moz-text-blink") }} property has been removed. Instead, the standard, still prefixed {{ cssxref("text-decoration-line") }} property now takes <code>blink</code> as a valid value. Actually it doesn't blink any content on Firefox though, from the perspective of <a href="/en-US/docs/Accessibility">accessibility</a>. Note that the blink effect with <code>text-decoration:blink</code> has been dropped with <a href="/en-US/docs/Site_Compatibility_for_Firefox_23">Firefox 23</a>.</p>
</section>
</section>
<section id="sect3">
<h2 id="DOM">DOM</h2>
<section id="sect4">
<h3 id="type_属性不是_image_的_HTMLInputElement_元素的_width_和_height_属性会返回_0">type 属性不是 image 的 HTMLInputElement 元素的 width 和 height 属性会返回 0</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=905240">Bug 905240 – HTMLInputElement.{width,height} getter should return 0 for type!='image'</a></li>
</ul>
<p>Previously, the <code>width</code> and <code>height</code> properties of an {{ HTMLElement("input") }} returned the dimension of the element. To comply with the spec, those properties now return <code>0</code> if the <code>type</code> property is not <code>image</code>.</p>
</section>
<section id="sect5">
<h3 id="Setting_document.domain_in_a_sandboxed_iframe_is_no_longer_allowed">Setting <code>document.domain</code> in a sandboxed <code>iframe</code> is no longer allowed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=907892">Bug 907892 – Disallow setting document.domain in sandboxed iframes</a></li>
</ul>
<p>Setting the {{ domxref("document.domain") }} property on a page embedded in an {{ HTMLElement("iframe") }} with the <code>sandbox</code> attribute will throw a security error from now on.</p>
</section>
<section id="sect6">
<h3 id="元素的_id_改变后，旧_id_不再是_window_对象的属性"><code><font face="Georgia, Times, Times New Roman, serif">元素的 </font>id 改变后，旧 id 不再是 window 对象的属性</code></h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=790601">Bug 790601 – Javascript element should not exist with old id</a></li>
</ul>
<p>An element with <code>id</code> is accessible through <code>window.<var><id></var></code>. Previously, the DOM object remained on {{ domxref("window") }} even after the <code>id</code> of the element is programmatically changed. This odd behavior has been fixed with Firefox 26. The {{ domxref("document.getElementById") }} method, which is recommended to use in general, is not affected by this change.</p>
</section>
<section id="sect7">
<h3 id="MessageEvent_has_been_updated"><code>MessageEvent</code> has been updated</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=848294">Bug 848294 – Update MessageEvent to be compatible with the spec</a></li>
</ul>
<p>The {{ domxref("MessageEvent") }} interface has been updated to comply with the latest spec. The <code>initMessageEvent</code> method has been removed while the interface is now a constructor.</p>
</section>
<section id="sect8">
<h3 id="HTMLCanvasElement.mozGetAsFile_has_been_deprecated"><code>HTMLCanvasElement.mozGetAsFile</code> has been deprecated</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=803612">Bug 803612 – Add deprecation warnings for mozGetAsFile</a></li>
</ul>
<p>The non-standard <code>mozGetAsFile</code> method on the {{ domxref("HTMLCanvasElement") }} interface is now deprecated and will be removed soon. The standard <code>toBlob</code> method can be used instead.</p>
</section>
<section id="sect9">
<h3 id="UserDataHandler_has_been_removed"><code>UserDataHandler</code> has been removed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=910751">Bug 910751 – Hide UserDataHandler from content</a></li>
</ul>
<p>The deprecated {{ domxref("UserDataHandler") }} interface has been removed. The {{ domxref("Node.setUserData") }} and {{ domxref("Node.getUserData") }} methods have already been removed with <a href="/en-US/docs/Site_Compatibility_for_Firefox_22">Firefox 22</a>.</p>
</section>
<section id="sect10">
<h3 id="XBL-related_methods_have_been_removed">XBL-related methods have been removed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=912322">Bug 912322 – document.getAnonymous* should not be available to web content</a></li>
</ul>
<p>The following methods on the <a href="/en-US/docs/XBL/XBL_1.0_Reference/DOM_Interfaces">XBL DOM Interface</a> have been removed from the {{ domxref("Document") }} interface: <code>getAnonymousNodes</code>, <code>getAnonymousElementByAttribute</code>, <code>getBindingParent</code> and <code>loadBindingDocument</code>.</p>
</section>
<section id="sect11">
<h3 id="Various_non-standard_interfaces_have_been_removed">Various non-standard interfaces have been removed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=899388">Bug 899388 – Remove XUL-related interfaces and ChromeWindow from content</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=905739">Bug 905739 – Remove nsIDOMStorageIndexedDB</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=909340">Bug 909340 – Hide XULElement from content</a></li>
</ul>
<p>As part of the ongoing effort to standardize global objects, the following non-standard interfaces have been removed: <code>ChromeWindow</code>, <code>StorageIndexedDB</code>, <code>XULButtonElement</code>, <code>XULCheckboxElement</code>, <code>XULCommandDispatcher</code>, <code>XULCommandEvent</code>, <code>XULControlElement</code>, <code>XULDocument</code>, <code>XULElement</code>, <code>XULLabeledControlElement</code> and <code>XULPopupElement</code>.</p>
</section>
</section>
<section id="sect12">
<h2 id="JavaScript">JavaScript</h2>
<section id="sect13">
<h3 id="The_reserved_words_are_no_longer_allowed_as_function_names">The reserved words are no longer allowed as function names</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=907958">Bug 907958 – Restrict function names to non-keywords</a></li>
</ul>
<p>The <a href="/en-US/docs/Web/JavaScript/Reference/Reserved_Words">reserved words</a> cannot be used for function names. Starting with Firefox 26, such a usage will throw a <a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/SyntaxError"><code>SyntaxError</code></a>. For example, <code>function delete() { ... }</code> is illegal.</p>
</section>
</section>
<section id="sect14">
<h2 id="Plug-ins">Plug-ins</h2>
<section id="sect15">
<h3 id="All_plug-ins_except_Flash_are_now_defaulted_to_Click-to-Play">All plug-ins except Flash are now defaulted to Click-to-Play</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=899080">Bug 899080 – Make plugins default to click-to-play</a></li>
</ul>
<p>Starting with Firefox 26, <a href="/en-US/docs/Plugins">plug-ins</a> require user interaction to be activated. With the exception of the popular Adobe Flash Player, all plug-in content embedded in a Web page is now disabled by default and enabled by user's click. This change has been made in order to improve security and performance of the browser. See the <a href="https://blog.mozilla.org/security/2013/01/29/putting-users-in-control-of-plugins/">Mozilla Security Blog</a> for details. Web developers are encouraged to leverage modern Web technologies, including <a href="/en-US/docs/Web/Guide/HTML/HTML5">HTML5</a>, to provide richer user experience.</p>
</section>
</section>
|
