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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
---
title: Site Compatibility for Firefox 32
slug: Mozilla/Firefox/Releases/32/Site_Compatibility
translation_of: Mozilla/Firefox/Releases/32/Site_Compatibility
---
<div>{{FirefoxSidebar}}</div><p>Firefox 32 was released on <time datetime="2014-09-02">September 2, 2014</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/32.0/releasenotes/">Firefox 32 Release Notes</a></li>
<li><a href="/en-US/docs/Mozilla/Firefox/Releases/32">Firefox 32 for developers</a></li>
</ul>
<p>Follow <a href="https://twitter.com/FxSiteCompat">@FxSiteCompat</a> on Twitter for further updates.</p>
<section id="sect1">
<h2 id="DOM">DOM</h2>
<section id="sect2">
<h3 id="navigator.doNotTrack_now_returns_a_correct_value"><code>navigator.doNotTrack</code> now returns a correct value</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=887703">Bug 887703 – Do not track settings results in wrong value for navigator.doNotTrack</a></li>
</ul>
<p>Previously, the {{ domxref("navigator.doNotTrack") }} property was incorrectly returning <code>"yes"</code> even when the <a href="http://www.mozilla.org/dnt/">Do Not Track</a> option was being disabled by the user. Starting with Firefox 32, it returns <code>"0"</code> (disabled), <code>"1"</code> (enabled) or <code>"unspecified"</code> to follow the spec.</p>
</section>
<section id="sect3">
<h3 id="new_Document()_now_returns_Document_instead_of_XMLDocument"><code>new Document()</code> now returns <code>Document</code> instead of <code>XMLDocument</code></h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1017932">Bug 1017932 – Document() constructor should return Document object (not XMLDocument)</a></li>
</ul>
<p>The <code>Document</code> constructor starts returning a {{ domxref("Document") }} object instead of {{ domxref("XMLDocument") }} to follow the latest spec. They are identical except the {{ domxref("XMLDocument.load", "load") }} method which is only available on <code>XMLDocument</code>. The {{ domxref("DOMImplementation.createDocument") }} method continues returning an <code>XMLDocument</code> object.</p>
</section>
<section id="sect4">
<h3 id="HTMLCollection_no_longer_matches_an_empty_string_name"><code>HTMLCollection</code> no longer matches an empty string name</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=891952">Bug 891952 – Update empty string handling in named getters to spec changes</a></li>
</ul>
<p>Previously, the empty named property of an {{ domxref("HTMLCollection") }} object, like <code>document.forms[0][""]</code>, was returning the first unnamed child element. This behavior has been changed to return <code>undefined</code> to match the updated spec.</p>
</section>
<section id="sect5">
<h3 id="HTMLTableElement.insertRow_now_always_inserts_the_row_to_<tbody>"><code>HTMLTableElement.insertRow</code> now always inserts the row to <code><tbody></code></h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1003539">Bug 1003539 – HTMLTableElement.insertRow doesn't insert the row at the right place when table has a thead or tfoot, no tbody, and no rows</a></li>
</ul>
<p>The behavior of the {{ domxref("HTMLTableElement.insertRow") }} method has been changed to follow the latest HTML5 spec. When there is a {{ HTMLElement("thead") }} but no {{ HTMLElement("tbody") }} and {{ HTMLElement("tr") }}, the new <code><tr></code> will be inserted to a newly created <code><tbody></code> instead of the existing <code><thead></code>.</p>
</section>
<section id="sect6">
<h3 id="WindowUtils_has_been_removed"><code>WindowUtils</code> has been removed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1017820">Bug 1017820 – Remove the classinfo for DOMWindowUtils</a></li>
</ul>
<p>As part of the ongoing effort to standardize global objects, the non-standard <code>WindowUtils</code> interface has been removed from {{ domxref("window") }}.</p>
</section>
<section id="sect7">
<h3 id="window.openDialog_has_been_removed"><code>window.openDialog</code> has been removed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=962747">Bug 962747 – Hide Window.openDialog from content</a></li>
</ul>
<p>The non-standard {{ domxref("window.openDialog") }} method is no longer available from Web content. {{ domxref("window.open") }} should be used instead.</p>
</section>
</section>
<section id="sect9">
<h2 id="Networking">Networking</h2>
<section id="sect10">
<h3 id="Cache_backend_has_been_overhauled">Cache backend has been overhauled</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=913806">Bug 913806 – Turn HTTP cache v2 on by default on all products</a></li>
</ul>
<p>The new HTTP cache backend has been landed on Firefox 32 to improve the page load performance. See <a href="http://www.janbambas.cz/new-firefox-http-cache-enabled/">Honza Bambas' blog post</a> for details. If you encountered any regressions, please <a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Networking%3A%20Cache">report the issue</a> to Bugzilla.</p>
</section>
</section>
<section id="sect8">
<h2 id="Security">Security</h2>
<section id="sect13">
<h3 id="Several_1024-bit_root_certificates_have_been_removed">Several 1024-bit root certificates have been removed</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=881553">Bug 881553 – Remove or turn off trust bits for 1024-bit root certs after December 31, 2013</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1029561">Bug 1029561 – Update Mozilla 32 to use NSS 3.16.3 after July 1st to include root CA updates</a></li>
</ul>
<p>As part of the ongoing security improvements, several SSL and code signing trust bits for 1024-bit root certificates have been removed from <a href="/en-US/docs/Mozilla/Projects/NSS">Network Security Services (NSS)</a> used in Firefox and other products. Those include AC Raíz Certicámara, Entrust.net, GTE CyberTrust, NetLock, TDC Internet, ValiCert and VeriSign. <a href="https://wiki.mozilla.org/CA:MD5and1024">1024-bit root certificates will all be removed</a> over the next few Firefox releases, because these are no longer considered as secure.</p>
</section>
</section>
<section id="sect11">
<h2 id="WebRTC">WebRTC</h2>
<section id="sect12">
<h3 id="onconnection_and_onclosedconnection_have_been_dropped"><code>onconnection</code> and <code>onclosedconnection</code> have been dropped</h3>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1014304">Bug 1014304 – Remove onconnection and onclosedconnection from PC</a></li>
</ul>
<p>The <code>onconnection</code> and <code>onclosedconnection</code> properties have been removed from the {{ domxref("RTCPeerConnection") }} interface, currently implemented as <code>mozRTCPeerConnection</code>, since they are no longer in the spec.</p>
</section>
</section>
|
