remove retired locales (#699)

24 files changed, 0 insertions, 4338 deletions

diff --git a/files/it/mozilla/add-ons/index.html b/files/it/mozilla/add-ons/index.html
deleted file mode 100644
index a9545252da..0000000000
--- a/files/it/mozilla/add-ons/index.html
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Componenti aggiuntivi
-slug: Mozilla/Add-ons
-tags:
-  - Add-ons
-  - TopicStub
-translation_of: Mozilla/Add-ons
----
-<div>{{AddonSidebar}}</div>
-
-<div class="summary">Modifica ed espandi le applicazioni Mozilla</div>
-
-<p><span class="seoSummary">I componenti aggiuntivi arricchiscono di nuove funzionalità le applicazioni basate su <a href="/it/docs/Gecko">Gecko</a> come Firefox, SeaMonkey e Thunderbird.</span><strong> </strong>Esistono due diversi tipi di componenti aggiuntivi: le <a href="#Estensioni">estensioni</a> che aggiungono nuove funzionalità all'applicazione, mentre i <a href="#Temi">temi</a> modificano l'interfaccia utente.</p>
-
-<p>Sia le estensioni che i temi vengono raccolti in un repository gestito da Mozilla su <a href="https://addons.mozilla.org/">addons.mozilla.org</a>, noto anche come AMO. Quando uno sviluppatore sceglie di <a href="/en-US/Add-ons/Submitting_an_add-on_to_AMO">caricare un componente aggiuntivo su AMO</a>, esso viene sottoposto a una revisione e, se la supera, pubblicato sul sito per essere scaricato dagli utenti. Sottoporre i propri componenti aggiuntivi ad AMO non è obbligatorio, tuttavia costituisce la garanzia per gli utenti che il componente sia stato revisionato e offre agli sviluppatori visibilità su una piattaforma riconosciuta come fonte di applicazioni utili.</p>
-
-<p>I componenti aggiuntivi possono alterare in maniera significativa il funzionamento dell'applicazione che li ospita. Mozilla ha quindi sviluppato una <a href="/en-US/docs/Mozilla/Add-ons/Add-on_guidelines">serie di linee guida</a> per assicurare che ogni componente offra all'utente un'esperienza ottimale. Queste linee guida sono valide per tutti i tipi di componente aggiuntivo, che siano ospitati sul server di <a href="https://addons.mozilla.org/">addons.mozilla.org</a> o meno.</p>
-
-<hr>
-<h2 id="Estensioni"><a name="Extensions">Estensioni</a></h2>
-
-<p>Le estensioni aggiungono nuove funzionalità alle applicazioni sviluppate da Mozilla come Firefox o Thunderbird. Possono integrare il browser con funzioni particolari, come per esempio un sistema alternativo per gestire le schede, e modificare i contenuti web per migliorare l'accessibilità o la sicurezza di un sito particolare.</p>
-
-<p>Le estensioni possono essere sviluppate con tre tecniche diverse: estensioni basate su Add-on SDK, estensioni che si avviano manualmente senza richiedere il riavvio del browser ed estensioni overlay.</p>
-
-<ul class="card-grid">
- <li><span><a href="https://developer.mozilla.org/it/docs/Mozilla/Add-ons/SDK">Estensioni con Add-on SDK</a></span><br>
-  Sviluppare estensioni con riavvio non richiesto grazie a una raccolta di API JavaScript di livello avanzato.</li>
- <li><span><a href="/en-US/Add-ons/Bootstrapped_extensions">Estensioni con riavvio non richiesto</a></span><br>
-  Sviluppare estensioni che funzionano dalla prima attivazione senza bisogno di riavviare il browser.</li>
- <li><a href="/en-US/Add-ons/Overlay_Extensions"><span>Estensioni overlay</span></a><br>
-  Sviluppare estensioni tradizionali che utilizzano un overlay XUL.</li>
-</ul>
-
-<p>Quando possibile, è consigliabile utilizzare Add-on SDK, che sfrutta lo stesso meccanismo delle estensioni con riavvio non richiesto ma semplificando alcune operazioni ed eliminando automaticamente il codice superfluo. In caso Add-on SDK non soddisfi le proprie esigenze, l'alternativa è implementare manualmente un'estensione con riavvio non richiesto. Le estensioni overlay sono attualmente obsolete, anche se ne rimane in circolazione un numero elevato.</p>
-
-<p>Per un approfondimento su quale tecnica sia più opportuno scegliere, ecco un <a href="/en-US/Add-ons/Comparing_Extension_Toolchains">articolo comparativo</a>.</p>
-
-<div class="column-container">
-<div class="column-half">
-<h3 id="Pratiche_consigliate">Pratiche consigliate</h3>
-
-<p>Indipendentemente dalle modalità con cui si sceglie di sviluppare un'estensione, esistono linee guida comuni da rispettare per garantire che il proprio componente offra la migliore esperienza utente possibile.</p>
-
-<dl>
- <dt><a href="/en-US/Add-ons/Performance_best_practices_in_extensions">Prestazioni</a></dt>
- <dd>Come rendere un'estensione veloce, reattiva e ottimizzata nel consumo della memoria.</dd>
- <dt><a href="/en-US/Add-ons/Security_best_practices_in_extensions">Sicurezza</a></dt>
- <dd>Come evitare di esporre l'utente a siti dannosi.</dd>
- <dt><a href="/en-US/Add-ons/Extension_etiquette">Etichetta</a></dt>
- <dd>Come gestire l'interazione con altre estensioni correttamente.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<h3 id="Nozioni_specifiche_per_applicazione">Nozioni specifiche per applicazione</h3>
-
-<p>La maggior parte della documentazione è scritta pensando a chi sviluppa per Firefox Desktop. Gli sviluppatori che intendono progettare per altre applicazioni basate su Gecko devono prendere atto di alcune differenze fondamentali.</p>
-
-<dl>
- <dt><a href="/en-US/Add-ons/Thunderbird">Thunderbird</a></dt>
- <dd>Sviluppare estensioni per il client di posta elettronica Thunderbird.</dd>
- <dt><a href="/en-US/Add-ons/Firefox_for_Android">Firefox per Android</a></dt>
- <dd>Sviluppare estensioni per la versione di Firefox per il sistema operativo Android.</dd>
- <dt><a href="/en-US/Add-ons/SeaMonkey_2">SeaMonkey</a></dt>
- <dd>Sviluppare estensioni per la suite di applicazioni <a href="http://www.seamonkey-project.org/">SeaMonkey</a>.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Temi"><a name="Themes">Temi</a></h2>
-
-<p>I Temi sono componenti aggiuntivi in grado di personalizzare l'interfaccia utente dell'applicazione. Esistono due tipi di tema: temi di sfondo (o semplicemente "temi") e temi completi.</p>
-
-<div class="column-container">
-<div class="column-half">
-<p>I <a href="https://addons.mozilla.org/it/developers/docs/themes">temi di sfondo</a> sono significativamente più semplici da implementare rispetto ai temi completi, ma offrono un livello di personalizzazione più limitato.</p>
-</div>
-
-<div class="column-half">
-<p>I <a href="/it/docs/Temi">temi completi</a> consentono modifiche più radicali all'interfaccia utente dell'applicazione. La documentazione sui temi completi è attualmente incompleta, ma viene qui citata in previsione di futuri aggiornamenti.</p>
-</div>
-</div>
-
-<hr>
-<h2 id="Altri_tipi_di_componente_aggiuntivo">Altri tipi di componente aggiuntivo</h2>
-
-<p>I <a href="/en-US/docs/Creating_OpenSearch_plugins_for_Firefox">plugin dei motori di ricerca</a> sono un tipo di componente aggiuntivo semplice e specifico: aggiungono nuovi motori alla barra di ricerca del browser.</p>
-
-<p>I <a href="/en-US/docs/Plugins">plugin</a> consentono all'applicazione di elaborare contenuti non supportati nativamente. Mozilla sta tentando di scoraggiare l'implementazione dei plugin, che hanno in passato causato problemi di stabilità, prestazioni e sicurezza.</p>
-
-<hr>
diff --git a/files/it/mozilla/add-ons/webextensions/anatomy_of_a_webextension/index.html b/files/it/mozilla/add-ons/webextensions/anatomy_of_a_webextension/index.html
deleted file mode 100644
index 56e7917140..0000000000
--- a/files/it/mozilla/add-ons/webextensions/anatomy_of_a_webextension/index.html
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: Anatomy of an extension
-slug: Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
-tags:
-  - WebExtensions
-translation_of: Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
----
-<div>{{AddonSidebar}}</div>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Un'estensione consiste in una raccolta di file, confezionati per la distribuzione e l'installazione.</span> <span title="">In questo articolo, esamineremo rapidamente i file che potrebbero essere presenti in un'estensione.</span></span></p>
-
-<h2 id="manifest.json">manifest.json</h2>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Questo è l'unico file che deve essere necessariamente presente in ogni estensione.</span> <span title="">Contiene metadati di base come il nome, la versione e le autorizzazioni richieste.</span> <span title="">Fornisce anche puntatori ad altri file nell'estensione.</span></span></p>
-
-<p>Il file <span class="tlid-translation translation" lang="it"><span title="">manifest può anche contenere puntatori a diversi altri tipi di file:</span></span></p>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Background_scripts">Background scripts</a>: <span class="tlid-translation translation" lang="it"><span title="">Implementare una logica a lungo termine</span></span> .</li>
- <li><span class="tlid-translation translation" lang="it"><span title="">Icone per l'estensione e per qualsiasi pulsante</span></span>.</li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Sidebars_popups_options_pages">Sidebars, popups, and options pages</a>: documenti HTML che forniscono contenuti per vari componenti dell'interfaccia utente.</li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Content_scripts">Content scripts</a>: JavaScript incluso nell'estensione, che verrà iniettato nelle pagine web.</li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Web_accessible_resources">Web-accessible resources</a>: <span class="tlid-translation translation" lang="it"><span title="">Rende i contenuti pacchettizzati accessibili a pagine Web e script di contenuto.</span></span></li>
-</ul>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/13669/webextension-anatomy.png" style="display: block; height: 581px; margin-left: auto; margin-right: auto; width: 600px;"></p>
-
-<p>Vedere la pagina di riferimento <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json">manifest.json</a> per maggiori dettagli.</p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Oltre a quelli a cui fa riferimento il manifest, un'estensione può includere</span></span> <a dir="ltr" href="https://mdn.mozillademos.org/files/11553/browser-action.png">Extension pages</a> <span class="tlid-translation translation" lang="it"><span title="">aggiuntive con file di supporto</span></span>.</p>
-
-<h2 id="Script_di_Background">Script di Background</h2>
-
-<p>Extensions often need to maintain long-term state or perform long-term operations independently of the lifetime of any particular web page or browser window. That is what background scripts are for.</p>
-
-<p>Background scripts are loaded as soon as the extension is loaded and stay loaded until the extension is disabled or uninstalled. You can use any of the <a href="/en-US/Add-ons/WebExtensions/API">WebExtension APIs</a> in the script, as long as you have requested the necessary <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions">permissions</a>.</p>
-
-<h3 id="Specifying_background_scripts">Specifying background scripts</h3>
-
-<p>You can include a background script using the <code>background</code> key in "manifest.json":</p>
-
-<pre class="brush: json">// manifest.json
-
-"background": {
-  "scripts": ["background-script.js"]
-}</pre>
-
-<p>You can specify multiple background scripts: if you do, they run in the same context, just like multiple scripts that are loaded into a single web page.</p>
-
-<p>Instead of specifying background scripts, you can specify a background page which has the added advantage of supporting ES6 modules:</p>
-
-<p style="margin-bottom: 0em;"><strong>manifest.json</strong></p>
-
-<pre class="brush: json">// manifest.json
-
-"background": {
-  "page": "background-page.html"
-}</pre>
-
-<p style="margin-bottom: 0em;"><strong>background-page.html</strong></p>
-
-<pre class="brush: html">&lt;!DOCTYPE html&gt;
-&lt;html lang="en"&gt;
-  &lt;head&gt;
-    &lt;meta charset="utf-8"&gt;
-    &lt;script type="module" src="background-script.js"&gt;&lt;/script&gt;
-  &lt;/head&gt;
-&lt;/html&gt;</pre>
-
-<h3 id="Background_script_environment">Background script environment</h3>
-
-<h4 id="DOM_APIs">DOM APIs</h4>
-
-<p>Background scripts run in the context of a special page called a background page. This gives them a <code><a href="/en-US/docs/Web/API/Window">window</a></code> global, along with all the standard DOM APIs provided by that object.</p>
-
-<h4 id="WebExtension_APIs">WebExtension APIs</h4>
-
-<p>Background scripts can use any of the <a href="/en-US/Add-ons/WebExtensions/API">WebExtension APIs</a> in the script, as long as their extension has the necessary <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions">permissions</a>.</p>
-
-<h4 id="Cross-origin_access">Cross-origin access</h4>
-
-<p>Background scripts can make XHR requests to any hosts for which they have <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions">host permissions</a>.</p>
-
-<h4 id="Web_content">Web content</h4>
-
-<p>Background scripts do not get direct access to web pages. However, they can load <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts">content scripts</a> into web pages and can <a href="/en-US/Add-ons/WebExtensions/Content_scripts#Communicating_with_background_scripts">communicate with these content scripts using a message-passing API</a>.</p>
-
-<h4 id="Content_security_policy">Content security policy</h4>
-
-<p>Background scripts are restricted from certain potentially dangerous operations, like the use of <code><a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval">eval()</a></code>, through a Content Security Policy. See <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy">Content Security Policy</a> for more details on this.</p>
-
-<h2 id="Sidebars_popups_options_pages">Sidebars, popups, options pages</h2>
-
-<p>Your extension can include various user interface components whose content is defined using an HTML document:</p>
-
-<ul>
- <li>a <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Sidebars">sidebar</a> is a pane that is displayed at the left-hand side of the browser window, next to the web page</li>
- <li>a <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Popups">popup</a> is a dialog that you can display when the user clicks on a <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Browser_action">toolbar button</a> or <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Page_actions">address bar button</a></li>
- <li>an <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Options_pages">options page</a> is a page that's shown when the user accesses your add-on's preferences in the browser's native add-ons manager.</li>
-</ul>
-
-<p>For each of these components, you create an HTML file and point to it using a specific property in <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json">manifest.json</a>. The HTML file can include CSS and JavaScript files, just like a normal web page.</p>
-
-<p>All of these are a type of <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Extension_pages">Extension pages</a>, and unlike a normal web page, your JavaScript can use all the same privileged WebExtension APIs as your background script. They can even directly access variables in the background page using {{WebExtAPIRef("runtime.getBackgroundPage()")}}.</p>
-
-<h2 id="Extension_pages">Extension pages</h2>
-
-<p>You can also include HTML documents in your extension which are not attached to some predefined user interface component. Unlike the documents you might provide for sidebars, popups, or options pages, these don't have an entry in manifest.json. However, they do also get access to all the same privileged WebExtension APIs as your background script.</p>
-
-<p>You'd typically load a page like this using {{WebExtAPIRef("windows.create()")}} or {{WebExtAPIRef("tabs.create()")}}.</p>
-
-<p>See <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Extension_pages">Extension pages</a> to learn more.</p>
-
-<h2 id="Script_di_contenuto">Script di contenuto</h2>
-
-<p>Use content scripts to access and manipulate web pages. Content scripts are loaded into web pages and run in the context of that particular page.</p>
-
-<p>Content scripts are extension-provided scripts which run in the context of a web page; this differs from scripts which are loaded by the page itself, including those which are provided in {{HTMLElement("script")}} elements within the page.</p>
-
-<p>Content scripts can see and manipulate the page's DOM, just like normal scripts loaded by the page.</p>
-
-<p>Unlike normal page scripts, they can:</p>
-
-<ul>
- <li>Make cross-domain XHR requests.</li>
- <li>Use a small subset of the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API">WebExtension APIs</a>.</li>
- <li>Exchange messages with their background scripts and can in this way indirectly access all the WebExtension APIs.</li>
-</ul>
-
-<p>Content scripts cannot directly access normal page scripts but can exchange messages with them using the standard <code><a href="/en-US/docs/Web/API/Window/postMessage">window.postMessage()</a></code> API.</p>
-
-<p>Usually, when we talk about content scripts, we are referring to JavaScript, but you can inject CSS into web pages using the same mechanism.</p>
-
-<p>See the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts">content scripts</a> article to learn more.</p>
-
-<h2 id="Web_accessible_resources">Web accessible resources</h2>
-
-<p>Web accessible resources are resources such as images, HTML, CSS, and JavaScript that you include in the extension and want to make accessible to content scripts and page scripts. Resources which are made web-accessible can be referenced by page scripts and content scripts using a special URI scheme.</p>
-
-<p>For example, if a content script wants to insert some images into web pages, you could include them in the extension and make them web accessible. Then the content script could create and append <code><a href="/en-US/docs/Web/HTML/Element/img">img</a></code> tags which reference the images via the <code>src</code> attribute.</p>
-
-<p>To learn more, see the documentation for the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/web_accessible_resources">web_accessible_resources</a> manifest.json key.</p>
-
-<p> </p>
-
-<p> </p>
diff --git a/files/it/mozilla/add-ons/webextensions/api/index.html b/files/it/mozilla/add-ons/webextensions/api/index.html
deleted file mode 100644
index 955086de10..0000000000
--- a/files/it/mozilla/add-ons/webextensions/api/index.html
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: JavaScript APIs
-slug: Mozilla/Add-ons/WebExtensions/API
-tags:
-  - NeedsTranslation
-  - TopicStub
-  - WebExtensions
-translation_of: Mozilla/Add-ons/WebExtensions/API
----
-<div>{{AddonSidebar}}</div>
-
-<div>
-<p>JavaScript APIs for WebExtensions can be used inside the extension's <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Background_scripts">background scripts</a> and in any other documents bundled with the extension, including <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_action">browser action</a> or <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Page_actions">page action</a> popups, <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Sidebars">sidebars</a>, <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Options_pages">options pages</a>, or <a href="/en-US/Add-ons/WebExtensions/manifest.json/chrome_url_overrides">new tab pages</a>. A few of these APIs can also be accessed by an extension's <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Content_scripts">content scripts</a> (see the <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#WebExtension_APIs">list in the content script guide</a>).</p>
-
-<p>To use the more powerful APIs you need to <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/permissions">request permission</a> in your extension's manifest.json.</p>
-
-<p>You can access the APIs using the <code>browser</code> namespace:</p>
-
-<pre class="brush: js line-numbers  language-js"><code class="language-js"><span class="keyword token">function</span> <span class="function token">logTabs</span><span class="punctuation token">(</span>tabs<span class="punctuation token">)</span> <span class="punctuation token">{</span>
-  console<span class="punctuation token">.</span><span class="function token">log</span><span class="punctuation token">(</span>tabs<span class="punctuation token">)</span><span class="punctuation token">;</span>
-<span class="punctuation token">}</span>
-
-browser<span class="punctuation token">.</span>tabs<span class="punctuation token">.</span><span class="function token">query</span><span class="punctuation token">(</span><span class="punctuation token">{</span>currentWindow<span class="punctuation token">:</span> <span class="keyword token">true</span><span class="punctuation token">}</span><span class="punctuation token">,</span> logTabs<span class="punctuation token">)</span><span class="punctuation token">;</span></code></pre>
-</div>
-
-<div>
-<p>Many of the APIs are asynchronous, returning a <code><a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">Promise</a></code>:</p>
-
-<pre class="brush: js line-numbers  language-js"><code class="language-js"><span class="keyword token">function</span> <span class="function token">logCookie</span><span class="punctuation token">(</span>c<span class="punctuation token">)</span> <span class="punctuation token">{</span>
-  console<span class="punctuation token">.</span><span class="function token">log</span><span class="punctuation token">(</span>c<span class="punctuation token">)</span><span class="punctuation token">;</span>
-<span class="punctuation token">}</span>
-
-<span class="keyword token">function</span> <span class="function token">logError</span><span class="punctuation token">(</span>e<span class="punctuation token">)</span> <span class="punctuation token">{</span>
-  console<span class="punctuation token">.</span><span class="function token">error</span><span class="punctuation token">(</span>e<span class="punctuation token">)</span><span class="punctuation token">;</span>
-<span class="punctuation token">}</span>
-
-<span class="keyword token">var</span> setCookie <span class="operator token">=</span> browser<span class="punctuation token">.</span>cookies<span class="punctuation token">.</span><span class="keyword token">set</span><span class="punctuation token">(</span>
-  <span class="punctuation token">{</span>url<span class="punctuation token">:</span> <span class="string token">"https://developer.mozilla.org/"</span><span class="punctuation token">}</span>
-<span class="punctuation token">)</span><span class="punctuation token">;</span>
-setCookie<span class="punctuation token">.</span><span class="function token">then</span><span class="punctuation token">(</span>logCookie<span class="punctuation token">,</span> logError<span class="punctuation token">)</span><span class="punctuation token">;</span></code></pre>
-</div>
-
-<div>
-<p>Note that this is different from Google Chrome's extension system, which uses the <code>chrome</code> namespace instead of <code>browser</code>, and which uses callbacks instead of promises for asynchronous functions. As a porting aid, the Firefox implementation of WebExtensions APIs supports <code>chrome</code> and callbacks as well as <code>browser</code> and promises. Mozilla has also written a polyfill which enables code that uses <code>browser</code> and promises to work unchanged in Chrome: <a class="external external-icon" href="https://github.com/mozilla/webextension-polyfill">https://github.com/mozilla/webextension-polyfill</a>.</p>
-
-<p>Firefox also implements these APIs under the <code>chrome</code> namespace using callbacks. This allows code written for Chrome to run largely unchanged in Firefox for the APIs documented here.</p>
-
-<p>Microsoft Edge uses the <code>browser</code> namespace, but doesn't yet support promise-based asynchronous APIs. In Edge, for the time being, asynchronous APIs must use callbacks.</p>
-
-<p>Not all browsers support all the APIs: for the details, see <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs">Browser support for JavaScript APIs</a>.</p>
-</div>
-
-<div>{{SubpagesWithSummaries}}</div>
diff --git a/files/it/mozilla/add-ons/webextensions/api/runtime/connectnative/index.html b/files/it/mozilla/add-ons/webextensions/api/runtime/connectnative/index.html
deleted file mode 100644
index 7f52576e62..0000000000
--- a/files/it/mozilla/add-ons/webextensions/api/runtime/connectnative/index.html
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: runtime.connectNative()
-slug: Mozilla/Add-ons/WebExtensions/API/runtime/connectNative
-tags:
-  - API
-  - Add-ons
-  - Estensioni
-  - Estensioni Web
-  - Non-standard
-  - Riferimenti
-  - connectNative
-  - metodo
-  - runtime
-translation_of: Mozilla/Add-ons/WebExtensions/API/runtime/connectNative
----
-<div>{{AddonSidebar()}}</div>
-
-<div>Connette l'estensione ad un'applicazione nativa presente sul computer dell'utente.</div>
-
-<div> </div>
-
-<div>Utilizza il nome di un'applicazione nativa come parametro.</div>
-
-<div>Avvia l'applicazione nativa e restituisce un oggetto {{WebExtAPIRef("runtime.Port")}} alla funzione invocante.</div>
-
-<div> </div>
-
-<div>La funzione invocante può usare la <code>Port</code> per scambiare messaggi con l'applicazione nativa utilizzando <code>Port.postMessage()</code> e <code>port.onMessage</code>.</div>
-
-<div> </div>
-
-<div>L'applicazione nativa rimane attiva a meno che non termini autonomamente, sia invocata la funzione <code>Port.disconnect()</code>, o la pagina che ha generato la <code>Port</code> venga distrutta. Un volta disconnessa la <code>Port</code> il browser rimane in attesa qualche secondo finchè il processo non termina correttamente ed in definitiva lo chiude se non fosse ancora terminato.</div>
-
-<div>Per maggiori informazioni, vedere <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging">Native messaging</a>.</div>
-
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="syntaxbox brush:js">var port = browser.runtime.connectNative(
-  application // string
-)
-</pre>
-
-<h3 id="Parameters">Parameters</h3>
-
-<dl>
- <dt><code>application</code></dt>
- <dd><code>string</code>. Il nome dell'applicazione nativa alla quale collegarsi. Questo deve combaciare con la proprietà "name" nel <a href="/en-US/Add-ons/WebExtensions/Native_messaging#App_manifest">native application's manifest file</a>.</dd>
-</dl>
-
-<h3 id="Return_value">Return value</h3>
-
-<p>Un oggetto {{WebExtAPIRef('runtime.Port')}}. La porta che la funzione invocante può usare per scambiare messaggi con l'applicazione nativa.</p>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p class="hidden">La tabella di compatibilità in questa pagina è basata sui dati disponibili. Se desiderassi contribuire a questi dati, scarica il codice da <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> ed inviaci una richiesta di allineamento.</p>
-
-<p>{{Compat("webextensions.api.runtime.connectNative")}}</p>
-
-<h2 id="Examples">Examples</h2>
-
-<p>L'esempio crea una connessione con l'applicazione nativa "ping_pong" e rimane in ascolto per i messaggi in entrata. Invia inoltre, all'applicazione nativa, un messaggio nel momento in cui l'utente clicca su un'icona specifica del browser:</p>
-
-<pre class="brush: js">/*
-On startup, connect to the "ping_pong" app.
-*/
-var port = <code class="language-js">browser</code>.runtime.connectNative("ping_pong");
-
-/*
-Listen for messages from the app.
-*/
-port.onMessage.addListener((response) =&gt; {
-  console.log("Received: " + response);
-});
-
-/*
-On a click on the browser action, send the app a message.
-*/
-<code class="language-js">browser</code>.browserAction.onClicked.addListener(() =&gt; {
-  console.log("Sending:  ping");
-  port.postMessage("ping");
-});</pre>
-
-<p>{{WebExtExamples}}</p>
-
-<div class="note"><strong>Fonti informative</strong>
-
-<p>Questa API è basata sull'API Chromium <a href="https://developer.chrome.com/extensions/runtime#method-connectNative"><code>chrome.runtime</code></a>.  Questo documento deriva dal <a href="https://chromium.googlesource.com/chromium/src/+/master/extensions/common/api/runtime.json"><code>runtime.json</code></a> del codice di Chromium.</p>
-
-<p>La compatibilità con Microsoft Edge è fornita da Microsoft ed è qui inclusa su licenza Creative Commons Attribution 3.0 United States License.</p>
-</div>
-
-<div class="hidden">
-<pre>// Copyright 2015 The Chromium Authors. All rights reserved.
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions are
-// met:
-//
-//    * Redistributions of source code must retain the above copyright
-// notice, this list of conditions and the following disclaimer.
-//    * Redistributions in binary form must reproduce the above
-// copyright notice, this list of conditions and the following disclaimer
-// in the documentation and/or other materials provided with the
-// distribution.
-//    * Neither the name of Google Inc. nor the names of its
-// contributors may be used to endorse or promote products derived from
-// this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-</pre>
-</div>
diff --git a/files/it/mozilla/add-ons/webextensions/api/runtime/index.html b/files/it/mozilla/add-ons/webextensions/api/runtime/index.html
deleted file mode 100644
index 1768642e7a..0000000000
--- a/files/it/mozilla/add-ons/webextensions/api/runtime/index.html
+++ /dev/null
@@ -1,168 +0,0 @@
----
-title: runtime
-slug: Mozilla/Add-ons/WebExtensions/API/runtime
-tags:
-  - API
-  - Add-ons
-  - Extensions
-  - Interface
-  - NeedsTranslation
-  - Reference
-  - TopicStub
-  - WebExtensions
-  - runtime
-translation_of: Mozilla/Add-ons/WebExtensions/API/runtime
----
-<div>{{AddonSidebar}}</div>
-
-<p><span class="seoSummary">This module provides information about your extension and the environment it's running in.</span></p>
-
-<p>It also provides messaging APIs enabling you to:</p>
-
-<ul>
- <li>Communicate between different parts of your extension.</li>
- <li>Communicate with other extensions.</li>
- <li>Communicate with native applications.</li>
-</ul>
-
-<h2 id="Types">Types</h2>
-
-<dl>
- <dt>{{WebExtAPIRef("runtime.Port")}}</dt>
- <dd>Represents one end of a connection between two specific contexts, which can be used to exchange messages.</dd>
- <dt>{{WebExtAPIRef("runtime.MessageSender")}}</dt>
- <dd>
- <p>Contains information about the sender of a message or connection request.</p>
- </dd>
- <dt>{{WebExtAPIRef("runtime.PlatformOs")}}</dt>
- <dd>Identifies the browser's operating system.</dd>
- <dt>{{WebExtAPIRef("runtime.PlatformArch")}}</dt>
- <dd>Identifies the browser's processor architecture.</dd>
- <dt>{{WebExtAPIRef("runtime.PlatformInfo")}}</dt>
- <dd>Contains information about the platform the browser is running on.</dd>
- <dt>{{WebExtAPIRef("runtime.RequestUpdateCheckStatus")}}</dt>
- <dd>Result of a call to {{WebExtAPIRef("runtime.requestUpdateCheck()")}}.</dd>
- <dt>{{WebExtAPIRef("runtime.OnInstalledReason")}}</dt>
- <dd>The reason that the {{WebExtAPIRef("runtime.onInstalled")}} event is being dispatched.</dd>
- <dt>{{WebExtAPIRef("runtime.OnRestartRequiredReason")}}</dt>
- <dd>The reason that the {{WebExtAPIRef("runtime.onRestartRequired")}} event is being dispatched.</dd>
-</dl>
-
-<h2 id="Properties">Properties</h2>
-
-<dl>
- <dt>{{WebExtAPIRef("runtime.lastError")}}</dt>
- <dd>This value is set when an asynchronous function has an error condition that it needs to report to its caller.</dd>
- <dt>{{WebExtAPIRef("runtime.id")}}</dt>
- <dd>The ID of the extension.</dd>
-</dl>
-
-<h2 id="Functions">Functions</h2>
-
-<dl>
- <dt>{{WebExtAPIRef("runtime.getBackgroundPage()")}}</dt>
- <dd>Retrieves the <a href="/en-US/docs/Web/API/Window">Window</a> object for the background page running inside the current extension.</dd>
- <dt>{{WebExtAPIRef("runtime.openOptionsPage()")}}</dt>
- <dd>
- <p>Opens your extension's <a href="/en-US/Add-ons/WebExtensions/user_interface/Options_pages">options page</a>.</p>
- </dd>
- <dt>{{WebExtAPIRef("runtime.getManifest()")}}</dt>
- <dd>Gets the complete <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json">manifest.json</a> file, serialized as an object.</dd>
- <dt>{{WebExtAPIRef("runtime.getURL()")}}</dt>
- <dd>Given a relative path from the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json">manifest.json</a> to a resource packaged with the extension, returns a fully-qualified URL.</dd>
- <dt>{{WebExtAPIRef("runtime.setUninstallURL()")}}</dt>
- <dd>Sets a URL to be visited when the extension is uninstalled.</dd>
- <dt>{{WebExtAPIRef("runtime.reload()")}}</dt>
- <dd>Reloads the extension.</dd>
- <dt>{{WebExtAPIRef("runtime.requestUpdateCheck()")}}</dt>
- <dd>Checks for updates to this extension.</dd>
- <dt>{{WebExtAPIRef("runtime.connect()")}}</dt>
- <dd>Establishes a connection from a content script to the main extension process, or from one extension to a different extension.</dd>
- <dt>{{WebExtAPIRef("runtime.connectNative()")}}</dt>
- <dd>
- <div>Connects the extension to a native application on the user's computer.</div>
- </dd>
- <dt>{{WebExtAPIRef("runtime.sendMessage()")}}</dt>
- <dd>Sends a single message to event listeners within your extension or a different extension. Similar to {{WebExtAPIRef('runtime.connect')}} but only sends a single message, with an optional response.</dd>
- <dt>{{WebExtAPIRef("runtime.sendNativeMessage()")}}</dt>
- <dd>Sends a single message from an extension to a native application.</dd>
- <dt>{{WebExtAPIRef("runtime.getPlatformInfo()")}}</dt>
- <dd>Returns information about the current platform.</dd>
- <dt>{{WebExtAPIRef("runtime.getBrowserInfo()")}}</dt>
- <dd>Returns information about the browser in which this extension is installed.</dd>
- <dt>{{WebExtAPIRef("runtime.getPackageDirectoryEntry()")}}</dt>
- <dd>Returns a DirectoryEntry for the package directory.</dd>
-</dl>
-
-<h2 id="Events">Events</h2>
-
-<dl>
- <dt>{{WebExtAPIRef("runtime.onStartup")}}</dt>
- <dd>Fired when a profile that has this extension installed first starts up. This event is not fired when an incognito profile is started.</dd>
- <dt>{{WebExtAPIRef("runtime.onInstalled")}}</dt>
- <dd>Fired when the extension is first installed, when the extension is updated to a new version, and when the browser is updated to a new version.</dd>
- <dt>{{WebExtAPIRef("runtime.onSuspend")}}</dt>
- <dd>Sent to the event page just before the extension is unloaded. This gives the extension an opportunity to do some cleanup.</dd>
- <dt>{{WebExtAPIRef("runtime.onSuspendCanceled")}}</dt>
- <dd>Sent after {{WebExtAPIRef("runtime.onSuspend")}} to indicate that the extension won't be unloaded after all.</dd>
- <dt>{{WebExtAPIRef("runtime.onUpdateAvailable")}}</dt>
- <dd>Fired when an update is available, but isn't installed immediately because the extension is currently running.</dd>
- <dt>{{WebExtAPIRef("runtime.onBrowserUpdateAvailable")}} {{deprecated_inline}}</dt>
- <dd>Fired when an update for the browser is available, but isn't installed immediately because a browser restart is required.</dd>
- <dt>{{WebExtAPIRef("runtime.onConnect")}}</dt>
- <dd>Fired when a connection is made with either an extension process or a content script.</dd>
- <dt>{{WebExtAPIRef("runtime.onConnectExternal")}}</dt>
- <dd>Fired when a connection is made with another extension.</dd>
- <dt>{{WebExtAPIRef("runtime.onMessage")}}</dt>
- <dd>Fired when a message is sent from either an extension process or a content script.</dd>
- <dt>{{WebExtAPIRef("runtime.onMessageExternal")}}</dt>
- <dd>Fired when a message is sent from another extension. Cannot be used in a content script.</dd>
- <dt>{{WebExtAPIRef("runtime.onRestartRequired")}}</dt>
- <dd>Fired when the device needs to be restarted.</dd>
-</dl>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-
-
-<p>{{Compat("webextensions.api.runtime")}}</p>
-
-<div>{{WebExtExamples("h2")}}</div>
-
-<div class="note"><strong>Acknowledgements</strong>
-
-<p>This API is based on Chromium's <a href="https://developer.chrome.com/extensions/runtime"><code>chrome.runtime</code></a> API. This documentation is derived from <a href="https://chromium.googlesource.com/chromium/src/+/master/extensions/common/api/runtime.json"><code>runtime.json</code></a> in the Chromium code.</p>
-
-<p>Microsoft Edge compatibility data is supplied by Microsoft Corporation and is included here under the Creative Commons Attribution 3.0 United States License.</p>
-</div>
-
-<div class="hidden">
-<pre>// Copyright 2015 The Chromium Authors. All rights reserved.
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions are
-// met:
-//
-//    * Redistributions of source code must retain the above copyright
-// notice, this list of conditions and the following disclaimer.
-//    * Redistributions in binary form must reproduce the above
-// copyright notice, this list of conditions and the following disclaimer
-// in the documentation and/or other materials provided with the
-// distribution.
-//    * Neither the name of Google Inc. nor the names of its
-// contributors may be used to endorse or promote products derived from
-// this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-</pre>
-</div>
diff --git a/files/it/mozilla/add-ons/webextensions/api/search/index.html b/files/it/mozilla/add-ons/webextensions/api/search/index.html
deleted file mode 100644
index 07f8f4d05a..0000000000
--- a/files/it/mozilla/add-ons/webextensions/api/search/index.html
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: search
-slug: Mozilla/Add-ons/WebExtensions/API/search
-translation_of: Mozilla/Add-ons/WebExtensions/API/search
----
-<div> </div>
-
-<div>{{AddonSidebar}}</div>
-
-<p>Lasciato intenzionalmente bianco fino a che l'API non sarà completata.</p>
diff --git a/files/it/mozilla/add-ons/webextensions/content_scripts/index.html b/files/it/mozilla/add-ons/webextensions/content_scripts/index.html
deleted file mode 100644
index 109482f57e..0000000000
--- a/files/it/mozilla/add-ons/webextensions/content_scripts/index.html
+++ /dev/null
@@ -1,495 +0,0 @@
----
-title: Script  di contenuto
-slug: Mozilla/Add-ons/WebExtensions/Content_scripts
-tags:
-  - WebExtensions
-translation_of: Mozilla/Add-ons/WebExtensions/Content_scripts
-original_slug: Mozilla/Add-ons/WebExtensions/Script_contenuto
----
-<div>{{AddonSidebar}}</div>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Uno </span></span> script di contenuto <span class="tlid-translation translation" lang="it"><span title=""> è una parte dell'estensione che viene eseguita nel contesto di una particolare pagina Web (al contrario degli script di sfondo che fanno parte dell'estensione o degli script che fanno parte del sito stesso, come quelli caricati utilizzando l'elemento</span></span> {{HTMLElement("script")}}).</p>
-
-<p><a href="/en-US/Add-ons/WebExtensions/Background_scripts">Gli script in Background</a> possono accedere a tutte le <a href="/en-US/Add-ons/WebExtensions/API">WebExtension JavaScript APIs</a>, <span class="tlid-translation translation" lang="it"><span title="">ma non possono accedere direttamente al contenuto delle pagine Web.</span> <span title="">Quindi, se la tua estensione ha bisogno di farlo, hai bisogno degli script di contenuto</span></span> <span class="tlid-translation translation" lang="it"><span title="">.</span></span></p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Proprio come gli script caricati da normali pagine web, gli script di contenuto possono leggere e modificare il contenuto delle loro pagine usando le API DOM standard.</span></span></p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Gli script di contenuto possono accedere solo a un piccolo sottoinsieme delle API di WebExtension, ma possono comunicare con script in background utilizzando un sistema di messaggistica e quindi accedere indirettamente alle API di WebExtension.</span></span></p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Gli script di contenuto possono accedere solo a</span></span> <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#WebExtension_APIs">un piccolo sottoinsieme delle WebExtension APIs</a>, ma possono <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#Communicating_with_background_scripts">comunicare con gli script in background</a> <span class="tlid-translation translation" lang="it"><span title="">utilizzando un sistema di messaggistica e quindi accedere indirettamente alle</span></span> WebExtension APIs.</p>
-
-<div class="note">
-<p><span class="tlid-translation translation" lang="it"><span title="">Nota che gli script di contenuto sono bloccati nei seguenti domini:</span></span></p>
-
-<ul style="display: grid;">
- <li>accounts-static.cdn.mozilla.net</li>
- <li>accounts.firefox.com</li>
- <li>addons.cdn.mozilla.net</li>
- <li>addons.mozilla.org</li>
- <li>api.accounts.firefox.com</li>
- <li>content.cdn.mozilla.net</li>
- <li>content.cdn.mozilla.net</li>
- <li>discovery.addons.mozilla.org</li>
- <li>input.mozilla.org</li>
- <li>install.mozilla.org</li>
- <li>oauth.accounts.firefox.com</li>
- <li>profile.accounts.firefox.com</li>
- <li>support.mozilla.org</li>
- <li>sync.services.mozilla.com</li>
- <li>testpilot.firefox.com</li>
-</ul>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Se provi a iniettare uno script di contenuto in una pagina in uno di questi domini, l'operazione fallirà e la pagina registrerà un errore</span></span> <a href="/en-US/docs/Web/HTTP/CSP">CSP</a>.</p>
-
-<p>Poiché queste restrizioni includono addons.mozilla.org, gli utenti possono essere tentati di utilizzare l'estensione immediatamente dopo l'installazione, solo per scoprire che non funziona! È possibile aggiungere un avviso appropriato o una <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/onboarding_upboarding_offboarding_best_practices">pagina di inserimento</a> per spostare gli utenti da addons.mozilla.org.</p>
-</div>
-
-<div class="note">
-<p><span class="tlid-translation translation" lang="it"><span title="">Valori aggiunti all'ambito globale di uno script di contenuto con</span></span> <code>var foo</code> o <code>window.foo = "bar"</code> potrebbe scomparire a causa di un bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1408996">1408996</a>.</p>
-</div>
-
-<h2 id="Caricamento_di_script_di_contenuto">Caricamento di script di contenuto</h2>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Puoi caricare uno script di contenuto in una pagina web in tre modi:</span></span></p>
-
-<p>Al momento dell'installazione, nelle pagine che corrispondono ai pattern URL: utilizzando la chiave content_scripts in manifest.json, è possibile chiedere al browser di caricare uno script di contenuto ogni volta che il browser carica una pagina il cui URL corrisponde a un determinato pattern.</p>
-
-<ol>
- <li><strong>Al momento dell'installazione, nelle pagine che corrispondono al pattern URL:</strong> utilizzando il tag <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_scripts">content_scripts</a></code> nel vostro file manifest.json, è possibile chiedere al browser di caricare uno script di contenuto ogni volta che il browser carica una pagina il cui URL <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns">corrisponde ad un determinato pattern</a></li>
- <li><strong>In fase di runtime, nelle pagine che corrispondono a un determinato pattern URL:</strong> utilizzando {{WebExtAPIRef("contentScripts")}} API, <span class="tlid-translation translation" lang="it"><span title="">potete chiedere al browser di caricare uno script di contenuto ogni volta che il browser carica una pagina il cui URL</span></span> <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns">corrisponde ad un determinato pattern</a>. Questo è un metodo possibile (1), <span class="tlid-translation translation" lang="it"><span title="">tranne che è possibile aggiungere e rimuovere script di contenuto in fase di esecuzione</span></span>.</li>
- <li><strong>In fase di runtime, in specifiche schede:</strong> utilizzando le <code><a href="/en-US/Add-ons/WebExtensions/API/Tabs/executeScript">tabs.executeScript()</a></code> API, è possibile caricare uno script di contenuto in una scheda specifica ogni volta che si desidera: ad esempio, in risposta all'utente che fa clic su <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_action">una azione del browser</a>.</li>
-</ol>
-
-<p>Esiste un solo ambito globale<em> per frame e per estensione</em>. Ciò significa che le variabili di uno script di contenuto possono essere direttamente accessibili da un altro script di contenuto, indipendentemente dal modo in cui è stato caricato.</p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Utilizzando i metodi (1) e (2), è possibile caricare gli script solo in pagine i cui URL possono essere rappresentati utilizzando un</span></span> <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Match_patterns">pattern di confronto</a>.</p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Usando il metodo (3), puoi anche caricare script in pagine contenute nella tua estensione, ma non puoi caricare script in pagine del browser privilegiate (come "about: debugging" o "about: addons").</span></span></p>
-
-<h2 id="Ambiente_degli_script_di_contenuto"><span class="tlid-translation translation" lang="it"><span title="">Ambiente degli script di contenuto</span></span></h2>
-
-<h3 id="accesso_al_DOM">accesso al DOM</h3>
-
-<p>Gli script di contenuto possono accedere e modificare il DOM della pagina, proprio come possono fare i normali script di pagina. Possono anche vedere eventuali modifiche apportate al DOM tramite script di pagina.</p>
-
-<p>Tuttavia, gli script di contenuto ottengono una "visualizzazione originale del DOM". Questo significa:</p>
-
-<ul>
- <li>Gli script di contenuto non possono vedere le variabili JavaScript definite dagli script di pagina.</li>
- <li>Se uno script di pagina ridefinisce una proprietà DOM incorporata, lo script di contenuto vedrà la versione originale della proprietà, non la versione ridefinita.</li>
-</ul>
-
-<p>In Firefox, questo comportamento è chiamato <a href="/en-US/docs/Xray_vision">Xray vision</a>.</p>
-
-<p>Consideriamo una pagina web come questa:</p>
-
-<pre class="brush: html">&lt;!DOCTYPE html&gt;
-&lt;html&gt;
-  &lt;head&gt;
-    &lt;meta http-equiv="content-type" content="text/html; charset=utf-8" /&gt;
-  &lt;/head&gt;
-
-  &lt;body&gt;
-    &lt;script src="page-scripts/page-script.js"&gt;&lt;/script&gt;
-  &lt;/body&gt;
-&lt;/html&gt;</pre>
-
-<p>Lo script "page-script.js" esegue:</p>
-
-<pre class="brush: js">// page-script.js
-
-// add a new element to the DOM
-var p = document.createElement("p");
-p.textContent = "This paragraph was added by a page script.";
-p.setAttribute("id", "page-script-para");
-document.body.appendChild(p);
-
-// define a new property on the window
-window.foo = "This global variable was added by a page script";
-
-// redefine the built-in window.confirm() function
-window.confirm = function() {
-  alert("The page script has also redefined 'confirm'");
-}</pre>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Ora un'estensione inietta uno script di contenuto nella pagina:</span></span></p>
-
-<pre class="brush: js">// content-script.js
-
-// can access and modify the DOM
-var pageScriptPara = document.getElementById("page-script-para");
-pageScriptPara.style.backgroundColor = "blue";
-
-// can't see page-script-added properties
-console.log(window.foo);  // undefined
-
-// sees the original form of redefined properties
-window.confirm("Are you sure?"); // calls the original window.confirm()</pre>
-
-<p>Lo stesso vale al contrario: gli script di pagina non possono vedere le proprietà JavaScript aggiunte dagli script di contenuto.</p>
-
-<p>Ciò significa che gli script di contenuto possono contare su proprietà DOM che si comportano in modo prevedibile, senza preoccuparsi delle sue variabili che si scontrano con le variabili dello script di pagina.</p>
-
-<p>Una conseguenza pratica di questo comportamento è che uno script di contenuto non avrà accesso a nessuna libreria JavaScript caricata dalla pagina. Ad esempio, se la pagina include jQuery, lo script di contenuto non sarà in grado di vederlo.</p>
-
-<p>Se uno script di contenuto desidera utilizzare una libreria JavaScript, la stessa libreria deve essere iniettata come script di contenuto insieme allo script di contenuto che vuole utilizzarlo:</p>
-
-<pre class="brush: json">"content_scripts": [
-  {
-    "matches": ["*://*.mozilla.org/*"],
-    "js": ["jquery.js", "content-script.js"]
-  }
-]</pre>
-
-<div class="blockIndicator note">
-<p><strong>Nota:</strong> Firefox <span class="tlid-translation translation" lang="it"><span title="">fornisce alcune API che consentono agli script di contenuto di accedere agli oggetti JavaScript creati dagli script di pagina e di esporre i propri oggetti JavaScript agli script di pagina.</span></span></p>
-
-<p>Vedere <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Sharing_objects_with_page_scripts">Condivisione di oggetti con script di pagina</a> per maggiori dettagli.</p>
-</div>
-
-<h3 id="WebExtension_APIs">WebExtension APIs</h3>
-
-<p>Oltre alle API DOM standard, gli script di contenuto possono utilizzare le seguenti API WebExtension:</p>
-
-<p>Da <code><a href="/en-US/Add-ons/WebExtensions/API/extension">extension</a></code>:</p>
-
-<ul>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/extension#getURL()">getURL()</a></code></li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/extension#inIncognitoContext">inIncognitoContext</a></code></li>
-</ul>
-
-<p>Da <code><a href="/en-US/Add-ons/WebExtensions/API/runtime">runtime</a></code>:</p>
-
-<ul>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#connect()">connect()</a></code></li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#getManifest()">getManifest()</a></code></li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#getURL()">getURL()</a></code></li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#onConnect">onConnect</a></code></li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#onMessage">onMessage</a></code></li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#sendMessage()">sendMessage()</a></code></li>
-</ul>
-
-<p>Da <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n">i18n</a></code>:</p>
-
-<ul>
- <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/getMessage">getMessage()</a></code></li>
- <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/getAcceptLanguages">getAcceptLanguages()</a></code></li>
- <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/getUILanguage">getUILanguage()</a></code></li>
- <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/detectLanguage">detectLanguage()</a></code></li>
-</ul>
-
-<p>Da <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus">menus</a></code>:</p>
-
-<ul>
- <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus/getTargetElement">getTargetElement</a></code></li>
-</ul>
-
-<p>Tutto da <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage">storage</a></code>.</p>
-
-<h3 id="XHR_e_Fetch">XHR e Fetch</h3>
-
-<p>Gli script di contenuto posso fare delle normali richieste usando <code><a href="/en-US/docs/Web/API/XMLHttpRequest">window.XMLHttpRequest</a></code> e <code><a href="/en-US/docs/Web/API/Fetch_API">window.fetch()</a></code> APIs.</p>
-
-<p>Gli script di contenuto ottengono gli stessi privilegi per i cross-domain del resto dell'estensione: quindi se l'estensione ha richiesto l'accesso tra cross-domain per un dominio utilizzando il tag <code><a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/permissions">permissions</a></code> nel file manifest.json, i suoi script di contenuto ottengono l'accesso anche a quel dominio.</p>
-
-<p>Ciò si ottiene esponendo le istanze XHR e di recupero più privilegiate nello script di contenuto, che ha l'effetto collaterale di non impostare le intestazioni di <code><a href="/en-US/docs/Web/HTTP/Headers/Origin">Origin</a></code> e <code><a href="/en-US/docs/Web/HTTP/Headers/Referer">Referer</a></code> come una richiesta dalla pagina stessa, spesso è preferibile evitare che la richiesta sveli la sua natura trasversale. Dalla versione 58 in poi le estensioni che devono eseguire richieste che si comportano come se fossero inviate dal contenuto stesso possono utilizzare <code>content.XMLHttpRequest</code> e <code>content.fetch()</code> instead. Per le estensioni cross-browser, la loro presenza deve essere rilevata dalla funzione.</p>
-
-<h2 id="Communicazione_con_gli_script_di_background">Communicazione con gli script di background</h2>
-
-<p>Sebbene gli script di contenuto non possano utilizzare direttamente la maggior parte delle API di WebExtension, possono comunicare con gli script in background dell'estensione utilizzando le API di messaggistica e pertanto possono accedere indirettamente a tutte le API a cui possono accedere gli script in background.</p>
-
-<p>Esistono due schemi di base per la comunicazione tra gli script in background e gli script di contenuto: è possibile inviare messaggi una tantum, con una risposta opzionale, oppure è possibile impostare una connessione più longeva tra i due lati e utilizzare tale connessione per scambiare messaggi .</p>
-
-<h3 id="Messaggi_one-off">Messaggi one-off</h3>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Per inviare messaggi one-off, con una risposta opzionale, puoi utilizzare le seguenti API:</span></span></p>
-
-<table class="fullwidth-table standard-table">
- <thead>
-  <tr>
-   <th scope="row"> </th>
-   <th scope="col">In content script</th>
-   <th scope="col">In background script</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Invia un messaggi</th>
-   <td><code><a href="/en-US/Add-ons/WebExtensions/API/runtime/sendMessage">browser.runtime.sendMessage()</a></code></td>
-   <td><code><a href="/en-US/Add-ons/WebExtensions/API/Tabs/sendMessage">browser.tabs.sendMessage()</a></code></td>
-  </tr>
-  <tr>
-   <th scope="row">Ricevi un messaggio</th>
-   <td><code><a href="/en-US/Add-ons/WebExtensions/API/runtime/onMessage">browser.runtime.onMessage</a></code></td>
-   <td><code><a href="/en-US/Add-ons/WebExtensions/API/runtime/onMessage">browser.runtime.onMessage</a></code></td>
-  </tr>
- </tbody>
-</table>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Ad esempio, ecco uno script di contenuto che si pone in ascolto degli eventi click in una pagina web.</span><br>
- <br>
- <span title="">Se il clic era su un collegamento, invia la pagina di sfondo con l'URL di destinazione:</span></span></p>
-
-<pre class="brush: js">// content-script.js
-
-window.addEventListener("click", notifyExtension);
-
-function notifyExtension(e) {
-  if (e.target.tagName != "A") {
-    return;
-  }
-  browser.runtime.sendMessage({"url": e.target.href});
-}</pre>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Lo script in background ascolta questi messaggi e visualizza una notifica utilizzando le</span></span> <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/notifications">notifications</a></code> API:</p>
-
-<pre class="brush: js">// background-script.js
-
-browser.runtime.onMessage.addListener(notify);
-
-function notify(message) {
-  browser.notifications.create({
-    "type": "basic",
-    "iconUrl": browser.extension.getURL("link.png"),
-    "title": "You clicked a link!",
-    "message": message.url
-  });
-}
-</pre>
-
-<p>(Questo codice di esempio è una riduzione dell'esempio <a href="https://github.com/mdn/webextensions-examples/tree/master/notify-link-clicks-i18n">notify-link-clicks-i18n</a> che è possibile trovare su GitHub.)</p>
-
-<h3 id="Messaggi_connection-based">Messaggi connection-based</h3>
-
-<p>L'invio di messaggi one-off può risultare complicato se si scambiano molti messaggi tra uno script in background e uno script di contenuto. Quindi uno schema alternativo è stabilire una connessione più longeva tra i due contesti e usare questa connessione per scambiare messaggi.</p>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Ogni lato ha un oggetto</span></span> <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/Port">runtime.Port</a></code>, <span class="tlid-translation translation" lang="it"><span title="">che può utilizzare per scambiare messaggi</span></span>.</p>
-
-<p>Per creare la connessione:</p>
-
-<ul>
- <li>Un lato attende la connessione usando il metodo <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onConnect">runtime.onConnect</a></code></li>
- <li>L'altro lato invoca:
-  <ul>
-   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/connect">tabs.connect()</a></code> (se si connette con uno script di contenuto); o</li>
-   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/connect">runtime.connect()</a></code> (per connettersi a duno script di background).</li>
-  </ul>
- </li>
-</ul>
-
-<p>Questo metodo ritorna un oggetto di tipo <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/Port">runtime.Port</a></code>.</p>
-
-<ul>
- <li>il listener <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onConnect">runtime.onConnect</a></code> riceve un oggetto <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/Port">runtime.Port</a></code>.</li>
-</ul>
-
-<p>Dopo che tutti e due i lati hanno una porta di comunicazione<span class="tlid-translation translation" lang="it"><span title=""> possono:</span></span></p>
-
-<ul>
- <li>inviare messaggi usando <code>runtime.Port.postMessage()</code>, e</li>
- <li>ricevere messaggi usando <code>runtime.Port.onMessage()</code></li>
-</ul>
-
-<p>Ad esempio, appena viene caricato, questo script di contenuto:</p>
-
-<ul>
- <li>Si collega ad uno script di background</li>
- <li>Memorizza la <code>Port</code> in una variabile <code>myPort</code></li>
- <li>Ascolta i messaggi su <code>myPort</code>, e li visualizza nella console di log</li>
- <li>Usa <code>myPort</code> per inviare messaggi allo script di background <span class="tlid-translation translation" lang="it"><span title="">quando l'utente fa clic sul documento</span></span></li>
-</ul>
-
-<pre class="brush: js">// content-script.js
-
-var myPort = browser.runtime.connect({name:"port-from-cs"});
-myPort.postMessage({greeting: "hello from content script"});
-
-myPort.onMessage.addListener(function(m) {
-  console.log("In content script, received message from background script: ");
-  console.log(m.greeting);
-});
-
-document.body.addEventListener("click", function() {
-  myPort.postMessage({greeting: "they clicked the page!"});
-});</pre>
-
-<p>Lo script di sfondo corrispondente:</p>
-
-<ul>
- <li>attende i tentativi di connessione dallo script di contenuto</li>
- <li>quando riceve un tentativo di connessione:
-  <ul>
-   <li>memorizza la porta in una variabile denominata <code>portFromCS</code></li>
-   <li>invia allo script del contenuto un messaggio utilizzando la porta</li>
-   <li>  inizia ad ascoltare i messaggi ricevuti sulla porta e li invia al log della console</li>
-  </ul>
- </li>
- <li>invia messaggi allo script di contenuto, utilizzando <code>portFromCS</code>, quando l'utente fa clic sull'azione del browser dell'estensione</li>
-</ul>
-
-<pre class="brush: js">// background-script.js
-
-var portFromCS;
-
-function connected(p) {
-  portFromCS = p;
-  portFromCS.postMessage({greeting: "hi there content script!"});
-  portFromCS.onMessage.addListener(function(m) {
-    console.log("In background script, received message from content script");
-    console.log(m.greeting);
-  });
-}
-
-browser.runtime.onConnect.addListener(connected);
-
-browser.browserAction.onClicked.addListener(function() {
-  portFromCS.postMessage({greeting: "they clicked the button!"});
-});
-</pre>
-
-<h4 id="Multipli_script_di_contenuto">Multipli script di contenuto</h4>
-
-<p><span class="tlid-translation translation" lang="it"><span title="">Se si dispone di più script di contenuto che comunicano contemporaneamente, è possibile memorizzare ciascuna connessione in un array.</span></span></p>
-
-<ul>
-</ul>
-
-<pre class="brush: js">// background-script.js
-
-var ports = []
-
-function connected(p) {
-  ports[p.sender.tab.id]    = p
-  //...
-}
-
-browser.runtime.onConnect.addListener(connected)
-
-browser.browserAction.onClicked.addListener(function() {
-  ports.forEach(p =&gt; {
-        p.postMessage({greeting: "they clicked the button!"})
-    })
-});
-</pre>
-
-<ul>
-</ul>
-
-<h2 id="Communicazione_con_la_pagina_web">Communicazione con la pagina web</h2>
-
-<p>Sebbene per impostazione predefinita gli script di contenuto non abbiano accesso agli oggetti creati dagli script di pagina, possono comunicare con gli script di pagina utilizzando la API DOM <code><a href="/en-US/docs/Web/API/Window/postMessage">window.postMessage</a></code> e <code><a href="/en-US/docs/Web/API/EventTarget/addEventListener">window.addEventListener</a></code>.</p>
-
-<p>Per esempio:</p>
-
-<pre class="brush: js">// page-script.js
-
-var messenger = document.getElementById("from-page-script");
-
-messenger.addEventListener("click", messageContentScript);
-
-function messageContentScript() {
-  window.postMessage({
-    direction: "from-page-script",
-    message: "Message from the page"
-  }, "*");</pre>
-
-<pre class="brush: js">// content-script.js
-
-window.addEventListener("message", function(event) {
-  if (event.source == window &amp;&amp;
-      event.data &amp;&amp;
-      event.data.direction == "from-page-script") {
-    alert("Content script received message: \"" + event.data.message + "\"");
-  }
-});</pre>
-
-<p>Per un esempio completo e funzionante, <a href="https://mdn.github.io/webextensions-examples/content-script-page-script-messaging.html">visitate la pagina demo su GitHub</a> e seguite le istruzioni.</p>
-
-<div class="warning">
-<p><span class="tlid-translation translation" lang="it"><span title="">Nota che ogni volta che si interagisce con contenuti web non fidati in questo modo, è necessario fare molta attenzione.</span> <span title="">Le estensioni sono codici privilegiati che possono avere potenti funzionalità e pagine Web ostili possono facilmente ingannarli per accedere a tali funzionalità.</span><br>
- <br>
- <span title="">Per fare un esempio banale, supponiamo che il codice dello script del contenuto che riceve il messaggio faccia qualcosa del genere:</span></span> </p>
-
-<pre class="brush: js">window.addEventListener("message", function(event) {
-  if (event.source == window &amp;&amp;
-      event.data.direction &amp;&amp;
-      event.data.direction == "from-page-script") {
-    eval(event.data.message);
-  }
-});</pre>
-
-<p>Ora lo script di pagina può eseguire qualsiasi codice con tutti i privilegi dello script di contenuto.</p>
-</div>
-
-<h2 id="Usare_eval()_in_uno_script_di_contenuto">Usare <code>eval()</code> in uno script di contenuto</h2>
-
-<p>In Chrome, <code><a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval">eval()</a></code> <span class="tlid-translation translation" lang="it"><span title="">esegue sempre il codice nel contesto dello script del contenuto, non nel contesto della pagina.</span></span></p>
-
-<p>In Firefox:</p>
-
-<ul>
- <li>Se usate <code>eval()</code>, esso esegue il codice nel contesto dello <strong>script di conteneto</strong>.</li>
- <li>Se usate <code>window.eval()</code>, esso esegue il code nel contesto della <strong>pagina</strong>.</li>
-</ul>
-
-<p>Per esempio, considerate uno script di contenuto simile a questo:</p>
-
-<pre class="brush: js">// content-script.js
-
-window.eval('window.x = 1;');
-eval('window.y = 2');
-
-console.log(`In content script, window.x: ${window.x}`);
-console.log(`In content script, window.y: ${window.y}`);
-
-window.postMessage({
-  message: "check"
-}, "*");</pre>
-
-<p>Questo codice crea semplicemente le variabili <code>x</code> e <code>y</code> usando <code>window.eval()</code> and <code>eval()</code>, quindi invia i loro valori al log della console, ed infine invia un messaggio alla pagina.</p>
-
-<p>Alla ricezione del messaggio, lo script della pagina invia le variabili al log della console:</p>
-
-<p> </p>
-
-<pre class="brush: js">window.addEventListener("message", function(event) {
-  if (event.source === window &amp;&amp; event.data &amp;&amp; event.data.message === "check") {
-    console.log(`In page script, window.x: ${window.x}`);
-    console.log(`In page script, window.y: ${window.y}`);
-  }
-});</pre>
-
-<p>In Chrome, si ottine questo risultato:</p>
-
-<pre>In content script, window.x: 1
-In content script, window.y: 2
-In page script, window.x: undefined
-In page script, window.y: undefined</pre>
-
-<p>In Firefox, invece, il risultato sarà il seguente:</p>
-
-<pre>In content script, window.x: undefined
-In content script, window.y: 2
-In page script, window.x: 1
-In page script, window.y: undefined</pre>
-
-<p>Lo stesso vale per <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout">setTimeout()</a></code>, <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setInterval">setInterval()</a></code>, e <code><a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function">Function()</a></code>.</p>
-
-<div class="blockIndicator warning">
-<p><span class="tlid-translation translation" lang="it"><span title="">Quando si esegue il codice nel contesto della pagina, è necessario prestare molta attenzione.</span> <span title="">L'ambiente della pagina è controllato da pagine Web potenzialmente dannose, che possono ridefinire gli oggetti con cui interagire per comportarsi in modi imprevisti:</span></span></p>
-
-<pre class="brush: js">// page.js redefines console.log
-
-var original = console.log;
-
-console.log = function() {
-  original(true);
-}
-</pre>
-
-
-<pre class="brush: js">// content-script.js calls the redefined version
-
-window.eval('console.log(false)');
-</pre>
-</div>
diff --git a/files/it/mozilla/add-ons/webextensions/index.html b/files/it/mozilla/add-ons/webextensions/index.html
deleted file mode 100644
index 078f67268d..0000000000
--- a/files/it/mozilla/add-ons/webextensions/index.html
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: WebExtensions
-slug: Mozilla/Add-ons/WebExtensions
-translation_of: Mozilla/Add-ons/WebExtensions
----
-<div>{{AddonSidebar}}</div>
-
-<p>Le WebExtensions sono un metodo cross-browser per sviluppare add-on. In larga parte il metodo è compatibile con le <a class="external-icon external" href="https://developer.chrome.com/extensions">extension API</a> supportate da Google, Chrome e Opera. Le estensioni create per questi browsers funzioneranno con <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_from_Google_Chrome">poche modifiche</a> su Firefox o <a href="https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/">Microsoft Edge</a>. Le API sono anche completamente compatibili con <a href="https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox">Firefox multiprocesso</a>.</p>
-
-<p>Vogliamo continuare ad estendere le API per supportare le necessità degli sviluppatori di add-ons, perciò se hai idee, ci piacerebbe sentirle. Contattaci su <a href="https://mail.mozilla.org/listinfo/dev-addons">dev-addons mailing list</a> o <a href="irc://irc.mozilla.org/webextensions">#webextensions</a> su <a href="https://wiki.mozilla.org/IRC">IRC</a>.</p>
-
-<div class="row topicpage-table">
-<div class="section">
-<h3 id="Iniziare">Iniziare</h3>
-
-<ul>
- <li><a href="/it/Add-ons/WebExtensions/Cosa_sono_le_WebExtensions">Cosa sono le WebExtensions?</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Your_first_WebExtension">La tua prima WebExtension</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Your_second_WebExtension">La seconda WebExtension</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension">Anatomia di una WebExtension</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Examples">Esempi di WebExtensions</a></li>
-</ul>
-
-<h3 id="Come_fare">Come fare</h3>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Intercept_HTTP_requests">Rilevare richieste HTTP</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Modify_a_web_page">Modificare una pagina web</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Add_a_button_to_the_toolbar">Aggiungere un bottone alla toolbar</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Implement_a_settings_page">Creare una pagina impostazioni</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard">Interagire con la clipboard</a></li>
- <li>Manipolare le tabs del browser</li>
- <li>Accedere e modificare bookmarks</li>
- <li>Accedere e modificare cookies</li>
-</ul>
-
-<h3 id="Concetti">Concetti</h3>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API">JavaScript API overview</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/User_interface_components">Componenti UI</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Content_scripts">Scripts contenuto</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Match_patterns">Match di patterns</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization">Internationazionalizzazione</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy">Policy di Sicurezza dei Contenuti</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging">Messaging Nativo</a></li>
-</ul>
-
-<h3 id="Porting">Porting</h3>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/Porting_from_Google_Chrome">Porting di una estensione Google Chrome</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on">Porting di un add-on Firefox</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Embedded_WebExtensions">Embedded WebExtensions</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK">Comparazione con la Add-on SDK</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Comparison_with_XUL_XPCOM_extensions">Comparazione con le estensioni XUL/XPCOM</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Chrome_incompatibilities">Incompatibilità di Chrome</a></li>
-</ul>
-
-<h3 id="Firefox_workflow">Firefox workflow</h3>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/Temporary_Installation_in_Firefox">Installazione</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Debugging">Debugging</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext">Iniziare con la web-ext</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/web-ext_command_reference">web-ext reference comandi</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/WebExtensions_and_the_Add-on_ID">WebExtensions e la Add-on ID</a></li>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Publishing_your_WebExtension">Pubblicare la tua WebExtension</a></li>
-</ul>
-</div>
-
-<div class="section">
-<h3 id="Riferimenti">Riferimenti</h3>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API">JavaScript API overview</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs">Compatibilità dei Browser con le APIs JavaScript</a></li>
-</ul>
-
-<h4 id="JavaScript_APIs">JavaScript APIs</h4>
-
-<div class="twocolumns">{{ ListSubpages ("/en-US/Add-ons/WebExtensions/API") }}</div>
-
-<h4 id="Manifest_keys">Manifest keys</h4>
-
-<div class="twocolumns">{{ ListSubpages ("/en-US/Add-ons/WebExtensions/manifest.json") }}</div>
-</div>
-</div>
diff --git a/files/it/mozilla/add-ons/webextensions/user_interface/index.html b/files/it/mozilla/add-ons/webextensions/user_interface/index.html
deleted file mode 100644
index bfc48bdc9e..0000000000
--- a/files/it/mozilla/add-ons/webextensions/user_interface/index.html
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Interfaccia utente
-slug: Mozilla/Add-ons/WebExtensions/user_interface
-translation_of: Mozilla/Add-ons/WebExtensions/user_interface
----
-<div>{{AddonSidebar}}</div>
-
-<p>Le estensioni che usa le API delle WebExtension sono fornite con diverse opzioni dell'interfaccia utente che possono aggiungere nuove funzioni all'utente. Un elenco di queste opzioni è presente di seguito, in questa sezione è presente una descrizione dettagliata di ogni opzione.</p>
-
-<div class="note">
-<p>Per consigli sull'utilizzo di questi componenti UI per permettere un migliore utilizzo, da parte dell'utente, della vostra estensione, guardate l'articolo <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/User_experience_best_practices">User experience best practices</a>.</p>
-</div>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">UI option</th>
-   <th scope="col">Description</th>
-   <th scope="col" style="width: 350px;">Example</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><a href="/Add-ons/WebExtensions/user_interface/Browser_action">Toolbar button</a> (browser action)</td>
-   <td>Un pulsante nella barra degli strumenti del browser che invia un evento all'estensione quando si fa clic sul pulsante. Per impostazione predefinita, il pulsante è visibile in tutte le schede.</td>
-   <td><img alt="Example showing a toolbar button (browser action)." src="https://mdn.mozillademos.org/files/15751/browser-action.png" style="height: 364px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td>Toolbar button with a <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Popups">popup</a></td>
-   <td><span class="tlid-translation translation" lang="it"><span title="">Una finestra popup che si attiva facendo clic su un pulsante nella barra degli strumenti del browser.</span> la finestra<span title=""> popup è definita in un documento HTML che gestisce l'interazione con l'utente.</span></span></td>
-   <td><img alt="Example of the pop-up on a toolbar button" src="https://mdn.mozillademos.org/files/15753/popup-shadow.png" style="height: 624px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td><a href="/Add-ons/WebExtensions/user_interface/Page_actions">Address bar button</a> (page action)</td>
-   <td><span class="tlid-translation translation" lang="it"><span title="">Un pulsante nella barra degli indirizzi del browser che invia un evento all'estensione quando si fa clic.</span> <span title="">Per impostazione predefinita, il pulsante è nascosto in tutte le schede.</span></span></td>
-   <td><img alt="Example showing an address bar button (page action) " src="https://mdn.mozillademos.org/files/15745/address_bar_button.png" style="height: 348px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td>Address bar button with a <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Popups">popup</a></td>
-   <td><span class="tlid-translation translation" lang="it"><span title="">Una finestra popup che si attiva facendo clic su un pulsante nella barra degli indirizzi del browser.</span> La<span title=""> finestra popup è definita in un documento HTML che gestisce l'interazione con l'utente.</span></span></td>
-   <td><img alt="Example of a popup on the address bar button" src="https://mdn.mozillademos.org/files/15747/page_action_popup.png" style="height: 524px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Context_menu_items">Context menu item</a></td>
-   <td>Elementi del menu, caselle di controllo e pulsanti di opzione su uno o più menu di scelta rapida del browser. Inoltre, i menu possono essere strutturati aggiungendo separatori. Quando si fa clic su una voce del menu, un evento viene inviato all'estensione.</td>
-   <td><img alt="Example of content menu items added by a WebExtension, from the context-menu-demo example" src="https://mdn.mozillademos.org/files/15756/context_menu_example.png" style="height: 942px; width: 864px;"></td>
-  </tr>
-  <tr>
-   <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Sidebars">Sidebar</a></td>
-   <td>
-    <p dir="ltr"><span class="tlid-translation translation" lang="it"><span title="">Un documento HTML visualizzato accanto a una pagina Web, con l'opzione per contenuti unici per pagina.</span> <span title="">La barra laterale viene aperta quando viene installata l'estensione, quindi obbedisce alla selezione della visibilità della barra laterale dell'utente.</span> <span title="">L'interazione dell'utente all'interno della barra laterale è gestita dal suo documento HTML.</span></span></p>
-   </td>
-   <td><img alt="Example of a sidebar" src="https://mdn.mozillademos.org/files/15755/bookmarks-sidebar.png" style="height: 846px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Options_pages">Options page</a></td>
-   <td>Una pagina che consente di definire le preferenze della vostra estensione che gli utenti possono modificare. L'utente può accedere a questa pagina dal gestore dei componenti aggiuntivi del browser.</td>
-   <td><img alt="Example showing the options page content added in the favorite colors example." src="https://mdn.mozillademos.org/files/15748/options_page.png"></td>
-  </tr>
-  <tr>
-   <td><a href="/Add-ons/WebExtensions/user_interface/Extension_pages">Extension page</a></td>
-   <td>Utilizzare le pagine Web incluse nell'estensione per fornire moduli, aiuto o qualsiasi altro contenuto richiesto, all'interno di finestre o schede.</td>
-   <td><img alt="Example of a simple bundled page displayed as a detached panel." src="https://mdn.mozillademos.org/files/15752/bundled_page_as_panel_small.png" style="height: 432px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Notifications">Notification</a></td>
-   <td>Notifiche temporanee visualizzate all'utente tramite il meccanismo delle notifiche del sistema operativo sottostante. Invia un evento all'estensione quando l'utente fa clic su una notifica o quando una notifica si chiude (automaticamente o su richiesta dell'utente).</td>
-   <td><img alt="Example of an extension triggered system notification" src="https://mdn.mozillademos.org/files/15754/notify-shadowed.png" style="height: 294px; width: 780px;"></td>
-  </tr>
-  <tr>
-   <td><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Omnibox">Address bar suggestion</a></td>
-   <td>Offre suggerimenti personalizzati sulla barra degli indirizzi quando l'utente inserisce una parola chiave.</td>
-   <td><img alt="Example showing the result of the firefox_code_search WebExtension's customization of the address bar suggestions." src="https://mdn.mozillademos.org/files/15749/omnibox_example_small.png" style="height: 464px; width: 700px;"></td>
-  </tr>
-  <tr>
-   <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/devtools_panels">Developer tools panel</a></td>
-   <td>Una scheda con un documento HTML associato che viene visualizzato negli strumenti di sviluppo del browser.</td>
-   <td><img alt="Example showing the result of the firefox_code_search WebExtension's customization of the address bar suggestions." src="https://mdn.mozillademos.org/files/15746/developer_panel_tab.png" style="height: 224px; width: 700px;"></td>
-  </tr>
- </tbody>
-</table>
-
-<p>Le seguenti guide pratiche forniscono indicazioni dettagliate per la creazione di alcune di queste opzioni dell'interfaccia utente:</p>
-
-<ul>
- <li><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Add_a_button_to_the_toolbar">Add a button to the toolbar</a></li>
- <li><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Implement_a_settings_page">Implement a settings page</a></li>
- <li><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Extending_the_developer_tools">Extending the developer tools</a></li>
-</ul>
diff --git a/files/it/mozilla/add-ons/webextensions/what_are_webextensions/index.html b/files/it/mozilla/add-ons/webextensions/what_are_webextensions/index.html
deleted file mode 100644
index 94139ae0ae..0000000000
--- a/files/it/mozilla/add-ons/webextensions/what_are_webextensions/index.html
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Cosa sono le estensioni?
-slug: Mozilla/Add-ons/WebExtensions/What_are_WebExtensions
-tags:
-  - Estensioni
-  - WebExtension
-translation_of: Mozilla/Add-ons/WebExtensions/What_are_WebExtensions
-original_slug: Mozilla/Add-ons/WebExtensions/Cosa_sono_le_WebExtensions
----
-<div>{{AddonSidebar}}</div>
-
-<p>Un'estensione modifica le funzionalità di un browser. Viene creata utilizzando gli standard della tecnologia web - HTML, CSS, e JavaScript. Può trarre vantaggio dalle stesse web API come JavaScript può in una pagina web, ma un'estensione ha anche accesso ad un proprio set di API JavaScript. Questo significa che puoi fare molto di più in un'estensione di quanto tu ne possa fare con il codice in una pagina. Questi sono soltanto alcuni esempi delle cose che puoi fare:</p>
-
-<p><strong>Migliorare o completare un sito web</strong>: Usa un'estensione per inviare nel browser caratteristiche o informazioni aggiuntive dal tuo sito web. Permettere agli utenti di raccogliere informazioni dalle pagine che visitano per migliorare il servizio che offri.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/15808/Amazon_add_on.png"></p>
-
-<p>Esempi: <a href="https://addons.mozilla.org/it/firefox/addon/amazon-browser-bar/">Amazon Assistant</a>, <a href="https://addons.mozilla.org/it/firefox/addon/onenote-clipper/">OneNote Web Clipper</a> e <a href="https://addons.mozilla.org/it/firefox/addon/grammarly-1/">Grammarly for Firefox</a></p>
-
-<p><strong>Permettere agli utenti di mostrare la loro personalità</strong>: Le estensioni del browser possono manipolare il contenuto delle pagine che l'utente visita. Aiuta gli utenti ad aggiungere un logo o un'immagine preferita come sfondo di tutte le pagine che visitano. Le estensioni ti danno anche la possibilità di aggiornare l'aspetto di Firefox. (Puoi aggiornare l'aspetto di Firefox anche con i <a href="https://developer.mozilla.org/en-US/Add-ons/Themes/Theme_concepts">temi</a>).</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/15809/MyWeb_New_Tab_add_on.png" style="height: 398px; width: 540px;"></p>
-
-<p>Esempi: <a href="https://addons.mozilla.org/it/firefox/addon/myweb-new-tab/">MyWeb New Tab</a>, <a href="https://addons.mozilla.org/it/firefox/addon/tabliss/">Tabliss</a> e <a href="https://addons.mozilla.org/it/firefox/addon/vivaldifox/">VivaldiFox</a></p>
-
-<p><strong>Aggiungere o rimuovere contenuti dalle pagine web</strong>: Potresti voler aiutare le persone a bloccare le pubblicità intrusive dalle pagine web, fornire l'accesso ad una guida di viaggio ogni volta che un paese o una città vengono menzionati in una pagina web, o ristrutturare il contenuto di una pagina per offrire un'esperienza di lettura coerente. Con la possibilità di poter accedere e aggiornare sia l'HTML che il CSS di una pagina, puoi aiutare gli utenti a fargli vedere il web nel modo in cui lo desiderano.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/15807/ublock_origin_add_on.png" style="height: 480px; width: 640px;"></p>
-
-<p>Esempi: <a href="https://addons.mozilla.org/it/firefox/addon/ublock-origin/">uBlock Origin</a>, <a href="https://addons.mozilla.org/it/firefox/addon/reader/">Reader</a> e <a href="https://addons.mozilla.org/it/firefox/addon/toolbox-google-play-store/">Toolbox for Google Play Store™</a></p>
-
-<p><strong>Aggiungere strumenti e nuove funzionalità di navigazione</strong>: Aggiungi nuove funzionalità ad una taskboard, o generare immagini di codici QR da URL, da collegamenti ipertestuali, o dal testo di una pagina. Con le opzioni flessibili dell'UI e dal potenziale delle WebExtension API, puoi aggiungere facilmente nuove funzionalità ad un browser. Inoltre, puoi aumentare le caratteristiche e le funzionalità di qualsiasi sito web, anche se non è il tuo.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/15806/QR_Code_Image_Generator_add_on.png"></p>
-
-<p>Esempi: <a href="https://addons.mozilla.org/it/firefox/addon/qr-code-image-generator/">QR Code Image Generator</a>, <a href="https://addons.mozilla.org/it/firefox/addon/swimlanes-for-trello/">Swimlanes for Trello</a> e <a href="https://addons.mozilla.org/it/firefox/addon/tomato-clock/">Tomato Clock</a></p>
-
-<p><strong>Giochi</strong>: Offri giochi per computer tradizionali, con la possibilità di giocare offline, ma anche esplorare nuove possibilità di gioco, ad esempio, incorporando il gameplay nella navigazione di tutti i giorni.</p>
-
-<p> <img alt="" src="https://mdn.mozillademos.org/files/15805/Asteroids_in_Popup_add_on%20.png" style="height: 438px; width: 700px;"></p>
-
-<p>Esempi: <a href="https://addons.mozilla.org/it/firefox/addon/asteroids-in-popup/">Asteroids in Popup</a>, <a href="https://addons.mozilla.org/it/firefox/addon/solitaire-card-game-new-tab/">Solitaire Card Game New Tab</a> e <a href="https://addons.mozilla.org/it/firefox/addon/2048-prime/">2048 Prime</a></p>
-
-<p><strong>Aggiungere strumenti di sviluppo</strong>: Puoi fornire strumenti di sviluppo web per il tuo lavoro, o hai sviluppato una tecnica utile o un approccio allo sviluppo web che vuoi condividere. In entrambi i casi, puoi migliorare gli strumenti di sviluppo integrati in Firefox aggiungendo una nuova scheda alla barra di strumenti per sviluppatori.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/15804/aXe_Developer_Tools_add_on.png" style="height: 261px; width: 700px;"></p>
-
-<p>Esempi: <a href="https://addons.mozilla.org/it/firefox/addon/web-developer/">Web Developer</a>, <a href="https://addons.mozilla.org/it/firefox/addon/react-devtools/">Web React Developer Tools</a> e <a href="https://addons.mozilla.org/it/firefox/addon/axe-devtools/">aXe Developer Tools</a></p>
-
-<p>Le estensioni per Firefox vengono create utilizzando le WebExtension API, un sistema cross-browser per lo sviluppo delle estensioni. In gran parte, l'API è compatibile con l'<a class="external external-icon" href="https://developer.chrome.com/extensions">API delle estensioni</a> supportato da Google Chrome e Opera. Le estensioni scritte per questi browser in molti casi funzioneranno in Firefox o Microsoft Edge soltanto con poche <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension">modifiche</a>. L'API è anche completamente compatibile con <a href="https://developer.mozilla.org/it/Firefox/Multiprocess_Firefox">multiprocess Firefox</a>.</p>
-
-<p>Se hai idee, domande, o hai bisogno di aiuto per migrare un add-on ad una WebExtension, puoi raggiungerci nella<a class="external external-icon" href="https://mail.mozilla.org/listinfo/dev-addons">dev-addons mailing list</a> o in <a href="irc://irc.mozilla.org/extdev">#extdev</a> su <a class="external external-icon" href="https://wiki.mozilla.org/IRC">IRC</a>.</p>
-
-<h2 id="E_adesso">E adesso?</h2>
-
-<ul>
- <li>Segui passo dopo passo lo sviluppo di una semplice estensione nella <a href="/it/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension">Tua prima estensione</a>.</li>
- <li>Scopri la struttura di un'estensione in <a href="/it/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension">Anatomia di una estensione</a>.</li>
- <li>Prova alcuni esempi di estensione in <a href="/it/Add-ons/WebExtensions/Examples">Esempi di estensioni</a>.</li>
-</ul>
diff --git a/files/it/mozilla/add-ons/webextensions/your_first_webextension/index.html b/files/it/mozilla/add-ons/webextensions/your_first_webextension/index.html
deleted file mode 100644
index 88781a40c2..0000000000
--- a/files/it/mozilla/add-ons/webextensions/your_first_webextension/index.html
+++ /dev/null
@@ -1,154 +0,0 @@
----
-title: La tua prima estensione
-slug: Mozilla/Add-ons/WebExtensions/Your_first_WebExtension
-tags:
-  - Guida
-  - WebExtension
-translation_of: Mozilla/Add-ons/WebExtensions/Your_first_WebExtension
-original_slug: Mozilla/Add-ons/WebExtensions/La_tua_prima_WebExtension
----
-<div>{{AddonSidebar}}</div>
-
-<p>In questo articolo creeremo passo dopo passo un'estensione per Firefox, dall'inizio alla fine. L'estensione aggiungerà un bordo rosso a tutte le pagine caricate da "mozilla.org" o da un suo sottodominio.</p>
-
-<p>Il codice sorgente di questo esempio è su GitHub: <a href="https://github.com/mdn/webextensions-examples/tree/master/borderify">https://github.com/mdn/webextensions-examples/tree/master/borderify</a>.</p>
-
-<p>Per prima cosa hai bisogno di Firefox versione 45 o superiore.</p>
-
-<h2 id="Scrittura_dell'estensione">Scrittura dell'estensione</h2>
-
-<p>Crea una cartella e posizionati al suo interno:</p>
-
-<pre class="brush: bash">mkdir borderify
-cd borderify</pre>
-
-<h3 id="manifest.json">manifest.json</h3>
-
-<p>Ora, crea un nuovo file chiamato "manifest.json" all'interno della cartella "borderify". Scrivi nel file il seguente contenuto:</p>
-
-<pre class="brush: json">{
-
-  "manifest_version": 2,
-  "name": "Borderify",
-  "version": "1.0",
-
-  "description": "Aggiunge un bordo rosso a tutte le pagine caricate da mozilla.org.",
-
-  "icons": {
-    "48": "icons/border-48.png"
-  },
-
-  "content_scripts": [
-    {
-      "matches": ["*://*.mozilla.org/*"],
-      "js": ["borderify.js"]
-    }
-  ]
-
-}</pre>
-
-<ul>
- <li>Le prime tre chiavi: <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/manifest_version">manifest_version</a></code>, <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/name">name</a></code>, and <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/version">version</a></code>, sono obbligatorie e contengono metadati base per l'estensione.</li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/manifest.json/description">description</a></code> è opzionale, ma raccomandata: viene mostrata in Gestione componenti aggiuntivi.</li>
- <li><code><a href="/en-US/Add-ons/WebExtensions/manifest.json/icons">icons</a></code> è opzionale, ma raccomandata: ti permette di specificare un'icona per l'estenzione che verrà mostrata in Gestione componenti aggiuntivi.</li>
-</ul>
-
-<p>La chiave più interessante è <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/content_scripts">content_scripts</a></code>, dice a Firefox di caricare uno script nelle pagine Web i cui URL corrispondono ad uno schema specifico. In questo caso, chiediamo a Firefox di caricare uno script chiamato "borderify.js" in tutto le pagine HTTP o HTTPS fornite da "mozilla.org" o dai suoi sottodomini.</p>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/Content_scripts">Ulteriori informazioni sugli script di contenuto.</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Match_patterns">Ulteriori informazioni sugli schemi di corrispondenza</a>.</li>
-</ul>
-
-<div class="warning">
-<p><a href="/en-US/Add-ons/WebExtensions/WebExtensions_and_the_Add-on_ID#When_do_you_need_an_Add-on_ID">In alcune situazioni è necessario specificare un ID per la propria estensione</a>. Se devi specificare l'ID dell'estensione, includi la chiave  <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/applications">applications</a></code> nel file <code>manifest.json</code> e imposta la sua proprietà <code>gecko.id</code>:</p>
-
-<pre class="brush: json">"applications": {
-  "gecko": {
-    "id": "borderify@example.com"
-  }
-}</pre>
-</div>
-
-<h3 id="iconsborder-48.png">icons/border-48.png</h3>
-
-<p>L'estensione dovrebbe avere un'icona. Essa verrà mostrata accanto alla lista delle estensioni in Gestione componenti aggiuntivi. Il file manifest.json ha dichiarato di avere un'icona a "icons/border-48.png".</p>
-
-<p>Crea la cartella "icons" all'interno della cartella "borderify". Salva un'icona al suo interno chiamata "border-48.png".  Puoi usare <a href="https://github.com/mdn/webextensions-examples/blob/master/borderify/icons/border-48.png">la stessa del nostro esempio</a>, presa dal set di icone di Google Material Design, e usata secondo i termini della licenza <a href="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike</a>.</p>
-
-<p>Se scegli di usare la tua icona, dovrebbe essere di 48x48 pixel. Potresti anche fornire un'icona di 96x96 pixel, per i display ad alta risoluzione. Se la aggiungi, dovrà essere specificata con la proprietà <code>96</code> dell'oggetto <code>icons</code> nel file manifest.json:</p>
-
-<pre class="brush: json">"icons": {
-  "48": "icons/border-48.png",
-  "96": "icons/border-96.png"
-}</pre>
-
-<p>In alternativa, potresti fornite un file SVG che verrà ridimensionato correttamente. (Comunque: se utilizzi SVG e la tua icona comprende del testo, puoi utilizzare lo strumento "converti in percorso" dell'editor SVG per appiattire il testo, in modo da poter essere ridimensionato con una dimensione/posizione coerente.)</p>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/manifest.json/icons">Ulteriori informazioni per specificare le icone.</a></li>
-</ul>
-
-<h3 id="borderify.js">borderify.js</h3>
-
-<p>Infine, crea un file chiamato "borderify.js" all'interno della cartella "borderify" e scrivici questo contenuto:</p>
-
-<pre class="brush: js">document.body.style.border = "5px solid red";</pre>
-
-<p>Questo script verrà caricato in tutte le pagine che corrispondono allo schema specificato nella chiave <code>content_scripts</code> nel file manifest.json. Lo script ha accesso diretto al documento, proprio come gli script caricati normalmente dalla pagina.</p>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/Content_scripts">Ulteriori informazioni sugli schemi di corrispondenza.</a></li>
-</ul>
-
-<h2 id="Provala">Provala</h2>
-
-<p>Innanzitutto, controlla di avere i file giusti nei posti giusti:</p>
-
-<pre>borderify/
-    icons/
-        border-48.png
-    borderify.js
-    manifest.json</pre>
-
-<h3 id="Installazione">Installazione</h3>
-
-<p>Apri "about:debugging" in Firefox, clicca "Carica comp. aggiuntivo temporaneo" e seleziona un qualsiasi file nella cartella dell'estensione:</p>
-
-<p>{{EmbedYouTube("cer9EUKegG4")}}</p>
-
-<p>L'estensione verrà ora installata e rimarrà finché non riavvii Firefox.</p>
-
-<p>In alternativa, puoi eseguire l'estensione da riga di comanto utilizzando lo strumento <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext">web-ext</a>.</p>
-
-<h3 id="Prova">Prova</h3>
-
-<p>Ora prova a visitare una pagina di "mozilla.org", dovresti vedere un bordo rosso intorno alla pagina:</p>
-
-<p>{{EmbedYouTube("rxBQl2Z9IBQ")}}</p>
-
-<div class="note">
-<p>Non provarlo su addons.mozilla.org, però! Gli script di contenuto sono attualmente bloccatu su quel dominio.</p>
-</div>
-
-<p>Prova a sperimentare un po. Modifica lo script per far cambiare il colore del bordo, o fai qualcosaltro al contenuto della pagina. Salva lo script e ricarica i file dell'estensione cliccando il pulsante "Ricarica" in about:debugging. Puoi vedere subito i cambiamenti:</p>
-
-<p>{{EmbedYouTube("NuajE60jfGY")}}</p>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/Temporary_Installation_in_Firefox">Ulteriori informazioni sul caricamento delle estensioni</a></li>
-</ul>
-
-<h2 id="Impacchettamento_e_pubblicazione">Impacchettamento e pubblicazione</h2>
-
-<p>Per far utilizzare la tua estensione ad altre persone, devi impacchettarla e inviarla a Mozilla per firmarla. Per saperne di più, guarda <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Publishing_your_WebExtension">"Pubblicazione della tua estensione"</a>.</p>
-
-<h2 id="E_adesso">E adesso?</h2>
-
-<p>Ora hai un'idea del processo di sviluppo di una WebExtension per firefox, prosegui con:</p>
-
-<ul>
- <li><a href="/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension">l'anatomia di un'estensione</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/Your_second_WebExtension">scrivere un'estensione più complessa</a></li>
- <li><a href="/en-US/Add-ons/WebExtensions/API">API Javascript disponibili per le estensioni.</a></li>
-</ul>
diff --git a/files/it/mozilla/firefox/experimental_features/index.html b/files/it/mozilla/firefox/experimental_features/index.html
deleted file mode 100644
index 1ae49b3ab3..0000000000
--- a/files/it/mozilla/firefox/experimental_features/index.html
+++ /dev/null
@@ -1,1507 +0,0 @@
----
-title: Funzionalità sperimentali in Firefox
-slug: Mozilla/Firefox/Experimental_features
-translation_of: Mozilla/Firefox/Experimental_features
-original_slug: Mozilla/Firefox/Funzionalità_sperimentali
----
-<div>{{FirefoxSidebar}}</div>
-
-<p class="summary">In order to test new features, Mozilla publishes a test version of the Firefox browser, <a href="https://nightly.mozilla.org/">Firefox Nightly</a>, every day. These nightly builds of Firefox typically include experimental or partially-implemented features, including those for proposed or cutting-edge Web platform standards.</p>
-
-<p class="summary"><span class="seoSummary">This page lists features that are in Nightly versions of Firefox along with information on how to activate them, if necessary.</span> You can test your Web sites and applications before these features get released and ensure everything will still work with the latest Web technology capabilities.</p>
-
-<p>To test these experimental features, you need to download <a href="https://nightly.mozilla.org/">Firefox Nightly</a> or <a href="https://www.mozilla.org/en-US/firefox/developer/">Firefox Developer Edition</a>. Which you need is described alongside each feature's description below.</p>
-
-<div class="blockIndicator note">
-<p><strong>Editor's note:</strong> When adding features to these tables, please try to include a link to the relevant bug or bugs using the {{TemplateLink("bug")}} macro: <code>\{{bug(<em>bug-number</em>)}}</code>.</p>
-</div>
-
-<h2 id="HTML">HTML</h2>
-
-<h3 id="Element_&lt;dialog>">Element: &lt;dialog&gt;</h3>
-
-<p>The HTML {{HTMLElement("dialog")}} element and its associated DOM APIs provide support for HTML-based modal dialog boxes. The current implementation is a little inelegant but is basically functional. See {{bug(840640)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>53</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>53</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>53</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>53</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.dialog_element.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Global_attribute_inputmode">Global attribute: inputmode</h3>
-
-<p>Our implementation of the <code><a href="/en-US/docs/Web/HTML/Global_attributes/inputmode">inputmode</a></code> global attribute has been updated as per the WHATWG spec ({{bug(1509527)}}), but we still need to make other changes too, like making it available on contenteditable content. See also {{bug(1205133)}} for details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>75</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.forms.inputmode</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="&lt;link_relpreload>">&lt;link rel="preload"&gt;</h3>
-
-<p>The {{HTMLElement("link")}} element's {{htmlattrxref("rel", "link")}} attribute is intended to help provide performance gains by letting you download resources earlier in the page lifecycle, ensuring that they're available earlier and are less likely to block page rendering. Read <a href="/en-US/docs/Web/HTML/Preloading_content">Preloading content with rel="preload"</a> for more details. For more details on the status of this feature, see {{bug(1639607)}}.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>78</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>78</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>78</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>78</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>network.preload</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="CSS">CSS</h2>
-
-<h3 id="Display_stray_control_characters_in_CSS_as_hex_boxes">Display stray control characters in CSS as hex boxes</h3>
-
-<p>This feature renders control characters (Unicode category Cc) other than <em>tab</em> (<code>U+0009</code>), <em>line feed</em> (<code>U+000A</code>), <em>form feed</em> (<code>U+000C</code>), and <em>carriage return</em> (<code>U+000D</code>) as a hexbox when they are not expected.<br>
- <br>
- See {{bug(1099557)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>43</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>43</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>43</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>43</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.control-characters.enabled</code> or <code>layout.css.control-characters.visible</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Property_initial-letter">Property: initial-letter</h3>
-
-<p>The {{cssxref("initial-letter")}} CSS property is part of the {{SpecName("CSS3 Inline")}} specification and allows you to specify how dropped, raised, and sunken initial letters are displayed.<br>
- <br>
- See {{bug(1223880)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>50</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>50</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>50</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>50</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.initial-letter.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Conic_gradients">Conic gradients</h3>
-
-<p><a href="/en-US/docs/Web/CSS/gradient#Conic_gradient">Conic gradients</a> expand CSS gradients to allow the color transitions to be rendered circling around a center point rather than radiating from it. See {{bug(1175958)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.conic-gradient.enabled</code> and <code>gfx.webrender.all</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Pseudo-class_focus-visible">Pseudo-class: :focus-visible</h3>
-
-<p>Allows focus styles to be applied to elements like buttons and form controls, only when they are focused using the keyboard (e.g. when tabbing between elements), and not when they are focused using a mouse or other pointing device. See <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1617600">bug 1617600</a> for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.focus-visible.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Single_numbers_as_aspect_ratio_in_media_queries">Single numbers as aspect ratio in media queries</h3>
-
-<p>Support for using a single {{cssxref("number")}} as a {{cssxref("ratio")}} when specifying the aspect ratio for a <a href="/en-US/docs/Web/CSS/Media_Queries">media query</a>. See {{bug(1565562)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.aspect-ratio-number.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Property_backdrop-filter">Property: backdrop-filter</h3>
-
-<p>The {{cssxref("backdrop-filter")}} property applies filter effects to the area behind an element. See {{bug(1178765)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>70</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.backdrop-filter.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Grid_Masonry_layout">Grid: Masonry layout</h3>
-
-<p>Adds support for a masonry style layout based on grid layout where one axis has a masonry layout while having normal grid layout on the other. This allows to create gallery style layouts like on Pinterest. See {{bug(1607954)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.grid-template-masonry-value.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="APIs">APIs</h2>
-
-<h3 id="Graphics_Canvas_WebGL_and_WebGPU">Graphics: Canvas, WebGL, and WebGPU</h3>
-
-<h4 id="Interface_OffscreenCanvas">Interface: OffscreenCanvas</h4>
-
-<p>The {{domxref("OffscreenCanvas")}} interface provides a canvas that can be rendered offscreen. It is available in both the window and <a href="/en-US/docs/Web/API/Web_Workers_API">worker</a> contexts. See {{bug(1390089)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>44</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>44</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>44</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>44</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>gfx.offscreencanvas.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Hit_regions">Hit regions</h4>
-
-<p>Whether the mouse coordinates are within a particular area on the canvas is a common problem to solve. The hit region API allows you define an area of your canvas and provides another possibility to expose interactive content on a canvas to accessibility tools.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>30</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>30</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>30</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>30</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>canvas.hitregions.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="WebGL_Draft_extensions">WebGL: Draft extensions</h4>
-
-<p>When this preference is enabled, any WebGL extensions currently in "draft" status which are being tested are enabled for use. Currently, there are no WebGL extensions being tested by Firefox.</p>
-
-<h4 id="WebGPU_API">WebGPU API</h4>
-
-<p>This new API provides low-level support for performing computation and graphics rendering using the {{interwiki("wikipedia", "Graphics Processing Unit")}} (GPU) of the user's device or computer. The <a href="https://gpuweb.github.io/gpuweb/">specification</a> is still a work-in-progress. See {{bug(1602129)}} for our progress on this API.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.webgpu.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="HTML_DOM_API">HTML DOM API</h3>
-
-<h4 id="Global_event_beforeinput">Global event: beforeinput</h4>
-
-<p>The global {{domxref("HTMLElement.beforeinput_event", "beforeinput")}} event is sent to an {{HTMLElement("input")}} element—or any element whose {{htmlattrxref("contenteditable")}} attribute is enabled—immediately before the element's value changes.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>74</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>74</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>74</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>74</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.input_events.beforeinput.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="HTMLMediaElement_method_setInkId">HTMLMediaElement method: setInkId()</h4>
-
-<p>{{domxref("HTMLMediaElement.setSinkId()")}} allows you to set the sink ID of an audio output device on an {{domxref("HTMLMediaElement")}}, thereby changing where the audio is being output. See {{bug(934425)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>64</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>64</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>64</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>64</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>media.setsinkid.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="HTMLMediaElement_properties_audioTracks_and_videoTracks">HTMLMediaElement properties: audioTracks and videoTracks</h4>
-
-<p>Enabling this feature adds the {{domxref("HTMLMediaElement.audioTracks")}} and {{domxref("HTMLMediaElement.videoTracks")}} properties to all HTML media elements. However, because Firefox doesn't currently suport multiple audio and video tracks, the most common use cases for these properties don't work, so they're both disabled by default. See {{bug(1057233)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>33</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>33</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>33</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>33</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>media.track.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="DOM">DOM</h3>
-
-<h4 id="Document_property_autoplayPolicy">Document property: autoplayPolicy</h4>
-
-<p>The {{domxref("document")}} property {{domxref("Document.autoplayPolicy", "autoplayPolicy")}} returns a string indicating how the browser handles requests to automatically play media (either using the {{domxref("HTMLMediaElement.autoplay", "autoplay")}} property on a media element or by attempting to trigger playback from JavaScript code. The spec for this API is still being written. The value changes over time depending on what the user is doing, their preferences, and the state of the browser in general. Potential values include <code>allowed</code> (autoplay is currently permitted), <code>allowed-muted</code> (autoplay is allowed but only with no—or muted—audio), and <code>disallowed</code> (autoplay is not allowed at this time). See {{bug(1506289)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>66</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>66</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>66</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>66</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.media.autoplay.autoplay-policy-api</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="GeometryUtils_methods_convertPointFromNode_convertRectFromNode_and_convertQuadFromNode">GeometryUtils methods: convertPointFromNode(), convertRectFromNode(), and convertQuadFromNode()</h4>
-
-<p>The {{domxref("GeometryUtils")}} methods {{domxref("GeometryUtils.convertPointFromNode", "convertPointFromNode()")}}, {{domxref("GeometryUtils.convertRectFromNode", "convertRectFromNode()")}}, and {{domxref("GeometryUtils.convertQuadFromNode", "convertQuadFromNode()")}} map the given point, rectangle, or quadruple from the {{domxref("Node")}} on which they're called to another node. See {{bug(918189)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>31</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>31</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>31</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>31</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.getBoxQuads.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="GeometryUtils_method_getBoxQuads">GeometryUtils method: getBoxQuads()</h4>
-
-<p>The {{domxref("GeometryUtils")}} method {{domxref("GeometryUtils.getBoxQuads", "getBoxQuads()")}} returns the CSS boxes for a {{domxref("Node")}} relative to any other node or viewport. See {{bug(917755)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>31</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>31</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>31</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>31</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.convertFromNode.enable</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Payment_Request_API">Payment Request API</h3>
-
-<h4 id="Primary_payment_handling">Primary payment handling</h4>
-
-<p>The <a href="/en-US/docs/Web/API/Payment_Request_API">Payment Request API</a> provides support for handling web-based payments within web content or apps. Due to a bug that came up during testing of the user interface, we have decided to postpone shipping this API while discussions over potential changes to the API are held. Work is ongoing. See {{bug(1318984)}} for more details on the state of this API.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>55</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>55</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>55</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>55</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.payments.request.enabled</code> and<br>
-    <code>dom.payments.request.supportedRegions</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Basic_Card_API">Basic Card API</h4>
-
-<p>Extends the <a href="/en-US/docs/Web/API/Payment_Request_API">Payment Request API</a> with dictionaries that define data structures describing card payment types and payment responses. See {{domxref("BasicCardRequest")}} and {{domxref("BasicCardResponse")}}.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>56</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>56</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>56</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>56</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.payments.request.enabled</code> and<br>
-    <code>dom.payments.request.supportedRegions</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Visual_Viewport_API">Visual Viewport API</h3>
-
-<p>The <a href="/en-US/docs/Web/API/Visual_Viewport_API">Visual Viewport API</a> provides access to information describing the position of the {{Glossary("visual viewport")}} relative to the document as well as to the window's content area. It also supports events to monitor changes to this information. See {{bug(1550390)}} for more details. There currently is no real plan to ship this on desktop, but you can track the state of that just in case it changes in {{bug(1551302)}}.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>63</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>63</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>63</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>63</td>
-   <td>Starting in Firefox 68, on Android only</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.visualviewport.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="Constructable_stylesheets">Constructable stylesheets</h3>
-
-<p>The addition of a constructor to the {{domxref("CSSStyleSheet")}} interface as well as a variety of related changes makes it possible to directly create new stylesheets without having to add the sheet to the HTML. This makes it much easier to create reusable stylesheets for use with <a href="/en-US/docs/Web/Web_Components/Using_shadow_DOM">Shadow DOM</a>. Our implementation is not yet complete; see {{bug(1520690)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>73</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>layout.css.constructable-stylesheets.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h3 id="WebRTC_and_media">WebRTC and media</h3>
-
-<p>The following experimental features include those found in the <a href="/en-US/docs/Web/API/WebRTC_API">WebRTC API</a>, the <a href="/en-US/docs/Web/API/Web_Audio_API">Web Audio API</a>, the <a href="/en-US/docs/Web/API/Media_Session_API">Media Session API</a>, the <a href="/en-US/docs/Web/API/Media_Source_Extensions_API">Media Source Extensions API</a>, the <a href="/en-US/docs/Web/API/Encrypted_Media_Extensions_API">Encrypted Media Extensions API</a>, and the <a href="/en-US/docs/Web/API/Media_Streams_API">Media Capture and Streams API</a>.</p>
-
-<h4 id="Media_Session_API">Media Session API</h4>
-
-<p>The entire Firefox implementation of the Media Session API is currently experimental. This API is used to customize the handling of media-related notifications, to manage events and data useful for presenting a user interface for managing media playback, and to obtain media file metadata. See {{bug(1112032)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>71</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>71</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>71</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>71</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.media.mediasession.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Asynchronous_SourceBuffer_add_and_remove">Asynchronous SourceBuffer add and remove</h4>
-
-<p>This adds the promise-based methods {{domxref("SourceBuffer.appendBufferAsync", "appendBufferAsync()")}} and {{domxref("SourceBuffer.removeAsync", "removeAsync()")}} for adding and removing media source buffers to the {{domxref("SourceBuffer")}} interface. See {{bug(1280613)}} and {{bug(778617)}} for more information.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>62</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>62</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>62</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>62</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>media.mediasource.experimental.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="AVIF_AV1_Image_File_format_support">AVIF (AV1 Image File format) support</h4>
-
-<p>With this feature enabled, Firefox supports the AV1 Image File (AVIF) format. This is a still image file format that leverages the capabilities of the AV1 video compression algorithms to reduce image size. See {{bug(1443863)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>image.avif.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Security_and_privacy">Security and privacy</h2>
-
-<h4 id="Block_plain_text_requests_from_Flash_on_encrypted_pages">Block plain text requests from Flash on encrypted pages</h4>
-
-<p>In order to help mitigate man-in-the-middle (MitM) attacks caused by Flash content on encrypted pages, a preference has been added to treat <code>OBJECT_SUBREQUEST</code>s as active content. See {{bug(1190623)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>59</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>59</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>59</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>59</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>security.mixed_content.block_object_subrequest</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Insecure_page_labeling">Insecure page labeling</h4>
-
-<p>These two preferences add a "Not secure" text label in the address bar next to the traditional lock icon when a page is loaded insecurely (that is, using {{Glossary("HTTP")}} rather than {{Glossary("HTTPS")}}). See {{bug(1335970)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>security.insecure_connection_text.enabled</code> for normal browsing mode; <code>security.insecure_connection_text.pbmode.enabled</code> for private browsing mode</th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Upgrading_mixed_display_content">Upgrading mixed display content</h4>
-
-<p>When enabled, this preference causes Firefox to automatically upgrade requests for media content from HTTP to HTTPS on secure pages. The intent is to prevent mixed-content conditions in which some content is loaded securely while other content is insecure. If the upgrade fails (because the media's host doesn't support HTTPS), the media is not loaded. See {{bug(1435733)}} for more details.</p>
-
-<p>This also changes the console warning; if the upgrade succeeds, the message indicates that the request was upgraded, instead of showing a warning.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>60</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>security.mixed_content.upgrade_display_content</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Implicit_relnoopener_on_links_with_target_blank">Implicit rel="noopener" on links with target="_blank"</h4>
-
-<p>Following Safari's lead, this experiment causes setting the {{htmlattrxref("target", "a")}} attribute on an {{HTMLElement("a")}} element to <code>_blank</code> (that is, using <code>target="_blank"</code>) to imply that the default value of {{htmlattrxref("rel", "a")}} is <code>noopener</code> rather than <code>opener</code>, which is the usual default. To bypass this security measure, web developers should explicitly request an opener relationship using <code>rel="opener"</code> on their <code>&lt;a&gt;</code> elements that use <code>target="_blank"</code> to open the link into a new window or tab. See {{bug(1503681)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>65</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>65</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>65</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>65</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>dom.targetBlankNoOpener.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="FTP_support_disabled">FTP support disabled</h4>
-
-<p>For security reasons, Mozilla intends to remove support for {{Glossary("FTP")}} from Firefox in 2010, effective in Firefox 82. See {{bug(1622409)}} for implementation progress. The <code>network.ftp.enabled</code> preference must be enabled (set to <code>true</code>) to allow FTP to be used.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>77</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>77</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>network.ftp.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Developer_tools">Developer tools</h2>
-
-<p>Mozilla's developer tools are constantly evolving. We experiment with new ideas, add new features, and test them on the Nightly and Developer Edition channels before letting them go through to beta and release. The features below are the current crop of experimental developer tool features.</p>
-
-<h4 id="Color_scheme_simulation">Color scheme simulation</h4>
-
-<p>Adds an option to simulate different color schemes allowing to test {{cssxref("@media/prefers-color-scheme", "@prefers-color-scheme")}} media queries. Using this media query lets your style sheet specify whether it prefers a light or dark user interface. This feature lets you test your code without having to change settings in your browser (or operating system, if the browser follows a system-wide color scheme setting).</p>
-
-<p>See {{bug(1550804)}} and {{bug(1137699)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>72</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>72</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>72</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>72</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>devtools.inspector.color-scheme-simulation.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Execution_context_selector">Execution context selector</h4>
-
-<p>This feature displays a button on the console's command line that lets you change the context in which the expression you enter will be executed. See {{bug(1605154)}} and {{bug(1605153)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>75</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>devtools.webconsole.input.context</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h4 id="Mobile_gesture_support_in_Responsive_Design_Mode">Mobile gesture support in Responsive Design Mode</h4>
-
-<p>Mouse gestures are used to simulate mobile gestures like swiping/scrolling, double-tap and pinch-zooming and long-press to select/open the context menu. See {{bug(1621781)}}, {{bug(1245183)}}, and {{bug(1401304)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>76<sup>[1]</sup></td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>76<sup>[1]</sup></td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>76<sup>[1]</sup></td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>76<sup>[1]</sup></td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2">n/a</th>
-  </tr>
- </tbody>
-</table>
-
-<p>[1] Support for zooming using the double-tap gesture was added in Firefox 76. The other gestures were added for Firefox 79.</p>
-
-<h4 id="Compatibility_panel">Compatibility panel</h4>
-
-<p>A side panel for the Page Inspector that shows you information detailing your app's cross-browser compatibility status. See {{bug(1584464)}} for more details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>71</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>71</td>
-   <td>Yes</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>71</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>71</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>devtools.inspector.compatibility.enabled</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="UI">UI</h2>
-
-<h4 id="Desktop_zooming">Desktop zooming</h4>
-
-<p>This feature lets you enable smooth pinch zooming on desktop computers without requiring layout reflows, just like mobile devices do. See {{bug(1245183)}} for further details.</p>
-
-<table class="standard-table" style="max-width: 42rem;">
- <thead>
-  <tr>
-   <th scope="col" style="vertical-align: bottom;">Release channel</th>
-   <th scope="col" style="vertical-align: bottom;">Version added</th>
-   <th scope="col" style="vertical-align: bottom;">Enabled by default?</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th scope="row">Nightly</th>
-   <td>42</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Developer Edition</th>
-   <td>42</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Beta</th>
-   <td>42</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Release</th>
-   <td>42</td>
-   <td>No</td>
-  </tr>
-  <tr>
-   <th scope="row">Preference name</th>
-   <th colspan="2"><code>apz.allow_zooming</code> and (on Windows) <code>apz.windows.use_direct_manipulation</code></th>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Firefox/Releases">Firefox developer release notes</a></li>
- <li><a href="https://nightly.mozilla.org/">Firefox Nightly</a></li>
- <li><a href="https://www.mozilla.org/en-US/firefox/developer/">Firefox Developer Edition</a></li>
-</ul>
diff --git a/files/it/mozilla/firefox/index.html b/files/it/mozilla/firefox/index.html
deleted file mode 100644
index c49c144593..0000000000
--- a/files/it/mozilla/firefox/index.html
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Firefox
-slug: Mozilla/Firefox
-tags:
-  - Firefox
-  - Mozilla
-  - NeedsTranslation
-  - TopicStub
-translation_of: Mozilla/Firefox
----
-<div>{{FirefoxSidebar}}</div>
-
-<div class="boxed translate-display">
-<p><a href="https://www.mozilla.org/firefox/">Firefox</a> è il popolare browser web di Mozilla, disponibile per varie piattaforme, tra cui Windows, Mac OS X, e Linux sul desktop, Android e altri dispositivi mobile. Con la sua ampia compatibilità, le ultime novità nelle tecnologie web e i potenti strumenti di sviluppo, Firefox è una scelta fantastica sia per gli sviluppatori web che per gli utenti.</p>
-
-<p>Firefox è un progetto open source; la maggior parte del codice è stata scritta dalla nostra enorme comunità di volontari. In questo documento è possibile imparare come contribuire al progetto Firefox e anche trovare link alle informazioni riguardanti lo sviluppo di componenti aggiuntivi per Firefox, utilizzare gli strumenti di sviluppo e altro ancora.</p>
-
-<div class="summary">
-<p>Impara a creare componenti aggiuntivi per <a href="http://www.mozilla.org/firefox/">Firefox</a>, sviluppare e compilare Firefox stesso e come funzionano le parti interne di Firefox e dei suoi sottoprogetti.</p>
-</div>
-
-<ul class="card-grid">
- <li><span>Note di rilascio per gli sviluppatori</span>
-
-  <p><a href="https://developer.mozilla.org/it/Firefox/Releases">Note di rilascio focalizzate sugli sviluppatori</a>; scopri quali nuove capacità vengono incluse in ogni versione di Firefox, sia per lo sviluppo di siti web che per i componenti aggiuntivi.</p>
- </li>
- <li><span>Documentazione del progetto</span>
-  <p>Ottieni informazioni dettagliate riguardo <a href="https://developer.mozilla.org/it/docs/Mozilla">il funzionamento interno di Firefox</a> e il suo sistema di compilazione, per aiutarti a trovare ciò che cerchi nel codice.</p>
- </li>
- <li><span>Guida per gli sviluppatori</span>
-  <p>La nostra <a href="https://developer.mozilla.org/it/docs/Developer_Guide">guida per gli sviluppatori</a> fornisce i dettagli riguardanti il come ottenere e compilare i sorgenti di Firefox, come orientarsi e come contribuire al progetto.</p>
- </li>
-</ul>
-
-<p>Firefox è disponibile su quattro <strong>canali</strong>. Il canale release è adatto all'uso quotidiano; è la versione fornita e usata dalle persone di tutto il mondo. Gli altri canali vengono utilizzati dai tester, dai pionieri e dai veri entusiasti.</p>
-
-<ul class="card-grid">
- <li class="download-box"><span>Firefox Nightly</span>
-
-  <p>Compilazioni notturne solo per scopi di test.</p>
-  <a class="download-button external ignore-external" href="https://nightly.mozilla.org/" rel="noopener">Scarica Nightly</a></li>
- <li class="download-box"><span>Firefox Aurora</span>
-  <p>Le ultime innovazioni in un ambiente sperimentale.</p>
-  <a class="download-button external ignore-external" href="https://www.mozilla.org/firefox/channel/#aurora" rel="noopener">Scarica Aurora</a></li>
- <li class="download-box"><span>Firefox Beta</span>
-  <p>Le ultime novità in un ambiente più stabile.</p>
-  <a class="download-button external ignore-external" href="https://www.mozilla.org/firefox/channel/#beta" rel="noopener">Scarica Beta</a></li>
- <li class="download-box"><span>Firefox</span>
-  <p>Provato, testato e usato da milioni di utenti in tutto il mondo.</p>
-  <a class="download-button external ignore-external" href="https://www.mozilla.org/firefox/channel/#firefox" rel="noopener">Scarica Firefox</a></li>
-</ul>
-</div>
diff --git a/files/it/mozilla/firefox/releases/1.5/adapting_xul_applications_for_firefox_1.5/index.html b/files/it/mozilla/firefox/releases/1.5/adapting_xul_applications_for_firefox_1.5/index.html
deleted file mode 100644
index 8781c43c6c..0000000000
--- a/files/it/mozilla/firefox/releases/1.5/adapting_xul_applications_for_firefox_1.5/index.html
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Adattare le applicazioni XUL a Firefox 1.5
-slug: Mozilla/Firefox/Releases/1.5/Adapting_XUL_Applications_for_Firefox_1.5
-tags:
-  - Estensioni
-  - Tutte_le_categorie
-  - XUL
-translation_of: Mozilla/Firefox/Releases/1.5/Adapting_XUL_Applications_for_Firefox_1.5
-original_slug: Adattare_le_applicazioni_XUL_a_Firefox_1.5
----
-<div>{{FirefoxSidebar}}</div><p> </p>
-
-<p>Questa pagina contiene un elenco di modifiche in <a href="it/Firefox_1.5">Firefox 1.5</a>, che coinvolgono gli sviluppatori XUL.</p>
-
-<h3 id="Cambiamenti_specifici" name="Cambiamenti_specifici">Cambiamenti specifici</h3>
-
-<ul>
- <li><a href="it/Modifica_dell'API_tree">Modifica dell'API tree</a></li>
- <li><a href="it/Caratteri_internazionali_nei_JavaScript_XUL">Caratteri internazionali nei JavaScript XUL</a> (ha efficacia solo su quelle estensioni che hanno dei file JavaScript contenenti caratteri non-ASCII)</li>
- <li><a href="it/Modifica_di_XMLHttpRequest_per_Gecko1.8">Modiche di XMLHttpRequest</a></li>
- <li><a href="it/Cambiamenti_di_XUL_per_Firefox_1.5">Cambiamenti di XUL per Firefox 1.5</a></li>
- <li><a href="it/XPCNativeWrapper">XPCNativeWrapper</a> sono attivati come opzione predefinita, e il comportamento è in parte cambiato rispetto alla versione 1.0.x</li>
- <li>Un metodo più semplice di <a href="it/Registrazione_Chrome">Registrazione Chrome</a> rende obsoleto contents.rdf.</li>
- <li>Per i menu contestuali con overlay: la funzione gContextMenu.linkURL() è stata rinominata come gContextMenu.getLinkURL(), e linkURL ora è una proprietà. Per utilizzarla mantenendo la retrocompatibilità:<br>
-  url = 'getLinkURL' in gContextMenu ? gContextMenu.getLinkURL() : gContextMenu.linkURL();</li>
-</ul>
-
-<h3 id="Altre_informazioni" name="Altre_informazioni">Altre informazioni</h3>
-
-<ul>
- <li><a href="it/Utilizzare_nsIXULAppInfo">Come controllare la versione dell'applicazione utilizzando nsIXULAppInfo</a></li>
- <li><a class="external" href="http://kb.mozillazine.org/Dev_:_Extensions_:_Cross-Version_Compatibility_Techniques">MozillaZine</a></li>
-</ul>
-
-<p>{{ languages( { "fr": "fr/Adaptation_des_applications_XUL_pour_Firefox_1.5", "en": "en/Adapting_XUL_Applications_for_Firefox_1.5" } ) }}</p>
diff --git a/files/it/mozilla/firefox/releases/1.5/index.html b/files/it/mozilla/firefox/releases/1.5/index.html
deleted file mode 100644
index e7299f00b5..0000000000
--- a/files/it/mozilla/firefox/releases/1.5/index.html
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: Firefox 1.5 per Sviluppatori
-slug: Mozilla/Firefox/Releases/1.5
-tags:
-  - Da_unire
-  - Sviluppo_Web
-  - Tutte_le_categorie
-translation_of: Mozilla/Firefox/Releases/1.5
-original_slug: Firefox_1.5_per_Sviluppatori
----
-<div>{{FirefoxSidebar}}</div><h2 id="Firefox_1.5">Firefox 1.5</h2>
-
-<p>Firefox 1.5 è stato rilasciato ed è disponibile <strong><a class="external" href="http://www.mozilla.com/firefox/">per il download</a></strong>. Basato sul motore <a href="it/Gecko">Gecko</a> 1.8, questa ultima versione del browser migliora il supporto agli standard e fornisce nuove possibilità per implementare applicazioni web di ultima generazione. Le funzionalità di Firefox 1.5 comprendono un supporto più esteso ai <a href="it/CSS">CSS</a> livello 2 e 3, API per applicazioni grafiche vettoriali 2D tramite <a href="it/SVG">SVG</a> 1.1 e l'elemento <code>&lt;canvas&gt;</code>, eventi <a href="it/XForms">XForms</a> e <a href="it/XML">XML</a>, oltre a miglioramenti per <a href="it/DHTML">DHTML</a>, <a href="it/JavaScript">JavaScript</a> e <a href="it/DOM">DOM</a>.</p>
-
-<p><strong>Firefox 1.5</strong> è disponibile per il download a questo indirizzo: <a class="external" href="http://www.mozilla.com/firefox/" rel="freelink">http://www.mozilla.com/firefox/</a></p>
-
-<h3 id="Strumenti_di_sviluppo" name="Strumenti_di_sviluppo">Strumenti di sviluppo</h3>
-
-<p>Esistono diversi strumenti ed estensioni che possono essere d'aiuto agli sviluppatori per supportare Firefox 1.5.</p>
-
-<ul>
- <li><a href="it/DOM_Inspector">DOM Inspector</a>, uno strumento che permette agli sviluppatori di esaminare e modificare i documenti senza dover agire direttamente sul documento. Questa estensione è disponibile come opzione nell'installazione personalizzata di Firefox 1.5.</li>
- <li>JavaScript console, uno strumento per scrivere e testare codice JavaScript e CSS.</li>
- <li>View page source, che comprende la sintassi evidenziata e una funzionalità di ricerca.</li>
- <li><a class="link-https" href="https://addons.mozilla.org/extensions/showlist.php?application=firefox&amp;category=Developer%20Tools">Browser extensions</a>, <a class="external" href="http://www.joehewitt.com/software/firebug/">Firebug</a>, <a href="it/Web_Developer_Extension_(external)">Web Developer toolbar</a>, <a href="it/Live_HTTP_Headers_(external)">Live HTTP Headers</a>, <a href="it/HTML_Validator_(external)">HTML Validator</a> e molti altri.</li>
-</ul>
-
-<p><strong>Nota:</strong> alcune estensioni potrebbero non supportare ancora Firefox 1.5 e potrebbero essere automaticamente disabilitate.</p>
-
-<p><strong>Nota:</strong> non tutte le estensioni hanno una traduzione in italiano.</p>
-
-<h3 id="Panoramica" name="Panoramica">Panoramica</h3>
-
-<p>Alcune nuove funzionalità di Firefox 1.5.</p>
-
-<h4 id="Sviluppatori_di_siti_e_applicazioni_web" name="Sviluppatori_di_siti_e_applicazioni_web">Sviluppatori di siti e applicazioni web</h4>
-
-<dl>
- <dt><a href="it/Introduzione_a_SVG_in_HTML">Introduzione a SVG in HTML</a></dt>
- <dd>impara a utilizzare JavaScript e i CSS per manipolare le immagini nello stesso modo in cui manipoleresti un normale documento XHTML. Vedi anche <a href="it/SVG_in_Firefox_1.5">SVG in Firefox 1.5</a> per conoscere lo stato e i problemi conosciuti dell'implementazione di SVG in Firefox 1.5.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Disegnare_grafici_con_le_Canvas">Disegnare grafici con le Canvas</a></dt>
- <dd>come utilizzare il nuovo tag <code>&lt;canvas&gt;</code> per disegnare grafici e altri oggetti.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Le_colonne_CSS3">Le colonne CSS3</a></dt>
- <dd>Il supporto per il testo multicolonna introdotto da CSS3.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Usare_la_cache_di_Firefox_1.5">Usare la cache di Firefox 1.5</a></dt>
- <dd>Come <code>bfcache</code> velocizza la navigazione coi tasti Indietro e Avanti</dd>
-</dl>
-
-<h4 id="Sviluppatori_XUL_e_sviluppatori_di_estensioni" name="Sviluppatori_XUL_e_sviluppatori_di_estensioni">Sviluppatori XUL e sviluppatori di estensioni</h4>
-
-<dl>
- <dt><a href="it/Creare_un'estensione">Creare un'estensione</a></dt>
- <dd>Questo tutorial spiega tutti i passi necessari per creare una semplicissima estensione per Firefox. Si veda anche <a class="external" href="http://kb.mozillazine.org/Getting_started_with_extension_development">another tutorial on MozillaZine knowledge base</a> (EN), che illustra le nuove funzionalità dell'Extension Manager nell'1.5 e spiega come creare una nuova estensione ancora più facile.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/XPCNativeWrapper">XPCNativeWrapper</a></dt>
- <dd><code>XPCNativeWrapper</code> è un modo per far sì che un oggetto sia accessibile in maniera sicura dal DOM. Si può utilizzare in tutte le versioni di Firefox, sebbene il suo comportamento sia leggermente cambiato in Firefox 1.5.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Sistema_di_Preferenze">Sistema di Preferenze</a></dt>
- <dd>Illustra i nuovi widget che permettono di creare finestre di opzioni in maniera molto semplice e utilizzando poco codice JavaScript.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Caratteri_internazionali_nel_JavaScript_di_XUL">Caratteri internazionali nel JavaScript di XUL</a></dt>
- <dd>i file JavaScript delle applicazioni XUL ora possono contenere caratteri non ASCII.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Cambiementi_nell'API_di_Tree">Cambiementi nell'API di Tree</a></dt>
- <dd>Le interfacce per accedere all'elemento XUL <code>&lt;tree&gt;</code> sono cambiate.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Modifiche_a_XUL_in_Firefox_1.5">Modifiche a XUL in Firefox 1.5</a></dt>
- <dd>Un sommario dei cambiamenti di XUL. Si veda anche <a href="it/Adattare_le_applicazioni_XUL_per_Firefox_1.5">Adattare le applicazioni XUL per Firefox 1.5</a>.</dd>
-</dl>
-
-<dl>
- <dt>Modifiche relative al networking</dt>
- <dd> </dd>
-</dl>
-
-<ul>
- <li>Certificate prompts can now be overridden on a per-channel basis. This works by setting an interface requestor as an <a href="it/NsIChannel">nsIChannel</a>'s notificationCallbacks and giving out an interface for <a href="it/NsIBadCertListener">nsIBadCertListener</a>.</li>
- <li>nsIWebBrowserPersist's listeners can now implement <a href="it/NsIInterfaceRequestor">nsIInterfaceRequestor</a>::GetInterface and will get an opportunity to provide all interfaces that channels might ask for, including <a href="it/NsIProgressEventSink">nsIProgressEventSink</a> (not too useful, redundant with <a href="it/NsIWebProgressListener">nsIWebProgressListener</a>). Useful interfaces here include <a href="it/NsIChannelEventSink">nsIChannelEventSink</a> and <a href="it/NsIBadCertListener">nsIBadCertListener</a>.</li>
- <li>Extensions or other necko consumers, including XMLHttpRequest, can set a Cookie header explicitly, and necko will not replace it. Stored cookies will be merged with the explicitly set header, in a way that the explicit header will override the stored cookies</li>
-</ul>
-
-<h3 id="Nuove_funzionalit.C3.A0_per_gli_utenti_finali" name="Nuove_funzionalit.C3.A0_per_gli_utenti_finali">Nuove funzionalità per gli utenti finali</h3>
-
-<h4 id="Esperienza_utente" name="Esperienza_utente">Esperienza utente</h4>
-
-<ul>
- <li><strong>Navigazione più veloce</strong> con miglioramenti alle performance dei bottoni Avanti e Indietro.</li>
- <li><strong>Possibilità di riordinare le schede col drag and drop</strong></li>
- <li><strong>Answers.com</strong> è stato aggiunto alla lista dei motori di ricerca</li>
- <li><strong>Miglioramenti nell'usabilità</strong>, comprese pagine di errore più chiare, un menu di opzioni riprogettato, la rilevazione automatica di RSS e il "Safe Mode".</li>
- <li><strong>Migliorata l'accessibilità</strong>, anche in DHTML.</li>
- <li><strong>Sito non funzionante</strong> - una funzionalità per segnalare agli sviluppatori di Firefox i siti che non vengono visualizzati correttamente.</li>
- <li><strong>Migliorato il supporto per MacOS X</strong> (10.2 e successivi), compresa l'importazione dei profili da Safari e Mac Internet Explorer.</li>
-</ul>
-
-<h4 id="Sicurezza_e_Privacy" name="Sicurezza_e_Privacy">Sicurezza e Privacy</h4>
-
-<ul>
- <li><strong>Aggiornamenti automatici</strong> in linea. Quando un aggiornamento è disponibile viene notificato in maniera più visibile e gli update ora possono essere di mezzo megabyte o anche più piccoli. Anche l'aggiornamento delle estensioni è stato migliorato.</li>
- <li><strong>Miglioramenti al blocco dei popup</strong>.</li>
- <li><strong>Elimina i dati personali</strong> - selezionando questa voce nel menu Strumenti o premendo Canc+Ctrl+Maiusc, vengono eliminati tutti i dati personali.</li>
-</ul>
-
-<h4 id="Supporto_agli_standard" name="Supporto_agli_standard">Supporto agli standard</h4>
-
-<p>Firefox offre un supporto coerente multipiattaforma per i seguenti standard del web:</p>
-
-<ul>
- <li>Hypertext Markup Language (<a href="it/HTML">HTML</a>) e Extensible Hypertext Markup Language (<a href="it/XHTML">XHTML</a>): <a class="external" href="http://www.w3.org/TR/html401/">HTML 4.01</a> e <a class="external" href="http://www.w3.org/TR/xhtml1/">XHTML 1.0/1.1</a></li>
- <li>Cascading Style Sheets (<a href="it/CSS">CSS</a>): <a class="external" href="http://www.w3.org/TR/REC-CSS1">CSS Level 1</a>, <a class="external" href="http://www.w3.org/TR/REC-CSS2">CSS Level 2</a> e parti di <a class="external" href="http://www.w3.org/Style/CSS/current-work.html">CSS Level 3</a></li>
- <li>Document Object Model (<a href="it/DOM">DOM</a>): <a class="external" href="http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/">DOM Level 1</a>, <a class="external" href="http://www.w3.org/DOM/DOMTR#dom2">DOM Level 2</a> e parti di <a class="external" href="http://www.w3.org/DOM/DOMTR#dom3">DOM Level 3</a></li>
- <li>Mathematical Markup Language: <a class="external" href="http://www.w3.org/Math/">MathML Version 2.0</a></li>
- <li>Extensible Markup Language (<a href="it/XML">XML</a>): <a class="external" href="http://www.w3.org/TR/REC-xml">XML 1.0</a>, <a class="external" href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>, <a class="external" href="http://www.w3.org/TR/xml-stylesheet/">Associating Style Sheets with XML Documents 1.0</a>, <a class="external" href="http://lists.w3.org/Archives/Public/www-xml-linking-comments/2001AprJun/att-0074/01-NOTE-FIXptr-20010425.htm">Fragment Identifier for XML</a></li>
- <li>XSL Transformations (<a href="it/XSLT">XSLT</a>): <a class="external" href="http://www.w3.org/TR/xslt">XSLT 1.0</a></li>
- <li>XML Path Language (<a href="it/XPath">XPath</a>): <a class="external" href="http://www.w3.org/TR/xpath">XPath 1.0</a></li>
- <li>Resource Description Framework (<a href="it/RDF">RDF</a>): <a class="external" href="http://www.w3.org/RDF/">RDF</a></li>
- <li>Simple Object Access Protocol (SOAP): <a class="external" href="http://www.w3.org/TR/SOAP/">SOAP 1.1</a></li>
- <li><a href="it/JavaScript">JavaScript</a> 1.6, basato su <a href="it/ECMA-262">ECMA-262</a>, revision 3: <a class="external" href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMA-262</a></li>
-</ul>
-
-<p>Firefox 1.5 supporta anche:</p>
-
-<ul>
- <li>HTTP, FTP, SSL, TLS e altri protocolli per il trasporto dei dati.</li>
- <li>La codifica Unicode.</li>
- <li>GIF, JPEG, PNG, SVG e altri formati per le immagini</li>
- <li>JavaScript 1.6 (si veda <a href="it/Novit%c3%a0_in_JavaScript_1.6">Novità in JavaScript 1.6</a>)</li>
-</ul>
-
-<h3 id="Cambiamenti_da_Firefox_1.0" name="Cambiamenti_da_Firefox_1.0">Cambiamenti da Firefox 1.0</h3>
-
-<p>Sono stati introdotti diversi cambiamenti in Firefox dalla sua prima release il 9 novembre 2004. Questo browser ha visto molti progressi, molte nuove funzionalità e sono stati corretti molti bug. Le<em>release notes</em> sono un'eccellente fonte di informazioni sulle modifiche che sono state apportate:</p>
-
-<ul>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5-comprehensive.html">What's new in Firefox 1.5 (comprehensive)</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5rc3.html">What's new in Firefox 1.5 RC 3</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5rc2.html">What's new in Firefox 1.5 RC 2</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5rc1.html">What's new in Firefox 1.5 RC 1</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5b2.html">What's new in Firefox 1.5 Beta 2</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5b1.html">What's new in Firefox 1.5 Beta 1</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5a2.html">What's new in Deer Park Alpha 2</a></li>
- <li><a class="external" href="http://www.squarefree.com/burningedge/releases/1.5a1.html">What's new in Deer Park Alpha 1</a></li>
-</ul>
-
-<p><strong>Nota:</strong> le note di rilascio qui linkate sono tutte in inglese.</p>
-
-<p>{{ languages( { "en": "en/Firefox_1.5_for_Developers", "es": "es/Firefox_1.5_para_Desarrolladores", "fr": "fr/Firefox_1.5_pour_les_d\u00e9veloppeurs", "ja": "ja/Firefox_1.5_for_Developers", "nl": "nl/Firefox_1.5_voor_ontwikkelaars", "pl": "pl/Firefox_1.5_dla_programist\u00f3w", "pt": "pt/Firefox_1.5_para_Desenvolvedores" } ) }}</p>
diff --git a/files/it/mozilla/firefox/releases/18/index.html b/files/it/mozilla/firefox/releases/18/index.html
deleted file mode 100644
index 7a24df60c8..0000000000
--- a/files/it/mozilla/firefox/releases/18/index.html
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Firefox 18 per sviluppatori
-slug: Mozilla/Firefox/Releases/18
-tags:
-  - Firefox
-  - Firefox 18
-translation_of: Mozilla/Firefox/Releases/18
-original_slug: Firefox_18_for_developers
----
-<div>{{FirefoxSidebar}}</div><p>{{ draft() }}</p>
-
-<p><span id="result_box" lang="it"><span class="hps">Firefox</span> <span class="hps">18 è stato</span> <span class="hps">pubblicato</span> <span class="hps">l'8 gennaio</span> <span class="hps">2013.</span> <span class="hps">In questo articolo</span> <span class="hps">sono elencate</span> <span class="hps">le modifiche</span> <span class="hps">principali</span> <span class="hps">che sono utili</span> <span class="hps">non solo</span> <span class="hps">per gli sviluppatori web</span><span>,</span> <span class="hps">ma anche</span> <span class="hps">gli sviluppatori</span> <span class="hps">di Firefox</span> <span class="hps">e Gecko</span> <span class="hps">così come</span> <span class="hps">add-on</span> <span class="hps">per gli sviluppatori.</span><br>
- <br>
- <span class="hps">Vuoi aiutare</span> la <span class="hps">documentazione di</span> <span class="hps">Firefox</span> <span class="hps">18? </span></span><a class="external" href="http://beta.elchi3.de/doctracker/#list=fx&amp;version=18.0">lista dei bug su cui bisogna scrivere</a><span id="result_box" lang="it"> <span class="hps">(Vedi l'elenco dei</span> <span class="hps">bug )</span></span></p>
-
-<h2 id="Modifiche_per_gli_sviluppatori_Web">Modifiche per gli sviluppatori Web</h2>
-
-<h3 id="HTML">HTML</h3>
-
-<ul>
- <li>L' attributo {{htmlattrxref("reversed","ol")}} dell' elemento  {{HTMLElement("ol")}} è ora supportato ({{bug("601912")}}).</li>
- <li>L' attributo {{htmlattrxref("crossorigin","link")}} dell' elemento {{HTMLElement("link")}} è ora supportato ({{bug("786564")}}).</li>
-</ul>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li>Il {{cssxref("min-width")}} e {{cssxref("min-height")}} adesso utilizza la keyword <code>auto</code> come <em>valore iniziale </em>(Questo ha effetto solo sugli elementi  contratti quando si risolve a <code>0</code>, il precedente valore iniziale, per gli altri elementi). ({{bug("763689")}})</li>
- <li>Il cascade è stato aggiornato: adesso l'autore delle regole <code>!important</code> non tiene conto delle <a href="/en-US/docs/CSS/Using_CSS_animations" title="/en-US/docs/CSS/Using_CSS_animations">animazioni CSS</a>. ({{bug("783714")}})</li>
- <li>La proprietà stenografica {{cssxref("background")}} adesso riconosce la proprietà CSS3 {{cssxref("background-size")}} specificata all'interno. ({{bug("570326")}})</li>
- <li>Il supporto iniziale per il Modulo CSS Flexbox è stato soppiantato. E' disabilito di default ma può essere abilitato settando <code>layout.css.flexbox.enabled</code> a true. ({{bug('666041')}})</li>
-</ul>
-
-<h3 id="DOM"> DOM</h3>
-
-<ul>
- <li><code>navigator.mozPay</code> è stato soppiantato. ({{bug("767818")}})</li>
- <li><code>window.devicePixelRatio</code> è stato soppiantato. ({{bug("564815")}})</li>
- <li>The MacOS X backend for <code>window.navigator.battery</code> è stato implementato. ({{bug("696045")}})</li>
- <li>{{domxref("BlobBuilder", "MozBlobBuilder")}} è rimosso. Gli sviluppatori necessitano di usare il costrutto {{domxref("Blob")}} per creare un oggetto<code> Blob</code>. ({{bug("744907")}})</li>
- <li>L'evento {{event("visibilitychange")}} e la <a href="/en-US/docs/DOM/Using_the_Page_Visibility_API" title="/en-US/docs/DOM/Using_the_Page_Visibility_API">Pagina di Visibilità API</a> sono stati privati di prefisso ({{bug("812086")}}).</li>
- <li><code>TextDecoder</code> e <code>TextEncoder</code> sono state aggiunte. ({{bug("764234")}})</li>
- <li><code>HTMLMediaElement</code><code>.src</code> è stata divisa in due proprietà: la prorietà standard <code>src</code>, affiancata da {{domxref("DOMString")}}, e la proprietà con prefisso <code>mozSrcObject</code>, affiancata dai <a href="/en-US/docs/WebRTC/MediaStream_API" title="/en-US/docs/WebRTC/MediaStream_API">flussi media</a> ({{bug("792665")}}).</li>
-</ul>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<ul>
- <li>I <a href="/en-US/docs/JavaScript/Reference/Global_Objects/Proxy">Direct Proxies </a>dell'Harmony (ECMAScript 6) sono stati soppiantati ({{bug("703537")}}). Avvertenza: l'implementatione contiene un paio di bug riconosciuti, mancate funzionalità e disallineamenti con l'attuale stato della spec. Non fate affidamento per la creazione di codice.</li>
- <li>Il metodo ECMAScript 6 <code>contains()</code> adesso è implementato sulle stringhe.  Questo sfortunatamente non è compatibile con Mootools 1.2, che si aspetta un comportamento differente da <code>contains()</code> sulle stringhe ma non ve lo assicuro.  Le nuove versioni di Mootools risolvono questo problema; i siti sites dovrebbero fare un upgrade alle loro versioni di Mootools verso versione più recenti della 1.2.</li>
-</ul>
-
-<h3 id="WebGL">WebGL</h3>
-
-<h3 id="SVG">SVG</h3>
-
-<h3 id="MathML">MathML</h3>
-
-<h3 id="XUL">XUL</h3>
-
-<h3 id="Network">Network</h3>
-
-<ul>
- <li>I fattori di qualità ("q-values") adesso sono bloccati a due cifre nell'intestazione HTTP <code>Accept-Language</code> ({{bug("672448")}}).</li>
- <li>La sintassi <code>ALLOW-FROM</code> dell'intestazione <a href="/en-US/docs/The_X-FRAME-OPTIONS_response_header" title="/en-US/docs/The_X-FRAME-OPTIONS_response_header"><code>X-FRAME-OPTIONS</code></a> HTTP di risposta adesso è supportata ({{bug("690168")}}).</li>
-</ul>
-
-<h3 id="Strumenti_di_sviluppo">Strumenti di sviluppo</h3>
-
-<h2 id="Novità_per_add-on_e_sviluppatori_Mozilla">Novità per add-on e sviluppatori Mozilla</h2>
-
-<h3 id="Novità_dell'Interfaccia">Novità dell'Interfaccia</h3>
-
-<dl>
- <dt>{{ interface("nsIStreamListener") }}</dt>
- <dd>The 4th parameter (aOffset) of <code>onDataAvailable()</code> method changes to unsigned long long. ({{bug("784912")}})</dd>
- <dt>{{ interface("nsIUploadChannel") }}</dt>
- <dd><code>setUploadStream()</code> supports over 2GB content-length ({{bug("790617")}})</dd>
- <dt>{{ interface("nsIEditor") }}</dt>
- <dd><code>addEditorObserver()</code> has been removed, use <code>setEditorObserver()</code> instead, <code>removeEditorObserver()</code> no longer takes a {{ interface("nsIEditorObserver") }} parameter ({{bug("785091")}})</dd>
-</dl>
-
-<dl>
- <dt>{{ interface("nsIHttpProtocolHandler") }}</dt>
- <dd><code>http-on-modify-request</code> observers are no longer guaranteed to be called synchronously during<br>
- <code>nsIChannel.asyncOpen(). </code>For observers that need to be called during <code>asyncOpen</code>(), the new <code>http-on-opening-request</code> observer topic has been added.  <code>See</code> ({{bug("800799")}})</dd>
-</dl>
-
-<h4 id="New_interfaces">New interfaces</h4>
-
-<h4 id="Removed_interfaces">Removed interfaces</h4>
-
-<p>The following interfaces have been removed.</p>
-
-<ul>
- <li>{{ interface("nsIEditorObserver") }}</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="http://www.mozilla.org/en-US/firefox/18.0beta/releasenotes/">Firefox 18 Beta Release Notes</a></li>
- <li><a href="https://hacks.mozilla.org/2012/10/aurora-18-hidpi-touch-events/">Aurora 18: HiDPI &amp; Touch Events</a> (Mozilla Hacks)</li>
- <li><a href="/en-US/docs/Site_Compatibility_for_Firefox_18">Site Compatibility for Firefox 18</a></li>
- <li><a href="https://blog.mozilla.org/addons/2012/12/28/compatibility-for-firefox-18/">Add-on Compatibility for Firefox 18</a> (Add-ons Blog)</li>
-</ul>
-
-<h3 id="Older_versions">Older versions</h3>
-
-<p>{{Firefox_for_developers('17')}}</p>
diff --git a/files/it/mozilla/firefox/releases/2/index.html b/files/it/mozilla/firefox/releases/2/index.html
deleted file mode 100644
index 6ebca8fe1e..0000000000
--- a/files/it/mozilla/firefox/releases/2/index.html
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: Firefox 2.0 per Sviluppatori
-slug: Mozilla/Firefox/Releases/2
-tags:
-  - Sviluppo_Web
-  - Tutte_le_categorie
-translation_of: Mozilla/Firefox/Releases/2
-original_slug: Firefox_2.0_per_Sviluppatori
----
-<div>{{FirefoxSidebar}}</div><h2 id="Nuove_funzionalit.C3.A0_per_sviluppatori_in_Firefox_2" name="Nuove_funzionalit.C3.A0_per_sviluppatori_in_Firefox_2">Nuove funzionalità per sviluppatori in Firefox 2</h2>
-
-<p>Firefox 2 introduce una vasta gamma di nuove funzionalità. Questo articolo fornisce i link alle rispettive pagine.</p>
-
-<h3 id="Per_gli_sviluppatori_di_siti_web_e_di_applicazioni" name="Per_gli_sviluppatori_di_siti_web_e_di_applicazioni">Per gli sviluppatori di siti web e di applicazioni</h3>
-
-<dl>
- <dt><a class="external" href="http://wiki.mozilla.org/Microsummaries">Microsummaries</a> (EN)</dt>
- <dd>I microsommari sono informazioni importanti regolarmente aggiornate e succinte riguardo alle pagine web. Sia un sito che degli sviluppatori esterni possono fornirle e gli utenti possono scegliere di visualizzare i microsommari invece dei titoli statici nei bookmark.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Creare_un_Microsommario">Creare un Microsommario</a></dt>
- <dd>Un tutorial che insegna a creare un generatore di microsommari.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Creare_Plugin_MozSearch">Creare Plugin MozSearch</a></dt>
- <dd>Firefox 2 supporta MozSearch, un formato per i plugin di ricerca basato su OpenSearch.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Supportare_i_suggerimenti_nei_plugin_di_ricerca">Supportare i suggerimenti nei plugin di ricerca</a></dt>
- <dd>Come permettere ai plugin in MozSearch di supportare i suggerimenti di ricerca, che appaiono in una casella popup mentre di scrive nella barra di ricerca.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Novit%c3%a0_in_JavaScript_1.7">Novità in JavaScript 1.7</a></dt>
- <dd>Firefox 2 supporta JavaScript 1.7, che comprende nuove funzionalità come <code>let</code>, assegnamento destrutturato, generatori e iteratori.</dd>
-</dl>
-
-<dl>
- <dt><a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/#scs-client-side">WHATWG Client-side session and persistent storage</a> (EN)</dt>
- <dd>La persistenza dei dati permette alle applicazioni web di immagazzinare dati strutturati nel browser.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/SVG_in_Firefox">SVG in Firefox</a></dt>
- <dd>Firefox 2 migliora il supporto a Scalable Vector Graphics (SVG), implementando l'elemento <code>&lt;textPath&gt;</code> e aggiungendo il supporto ad alcuni attributi precedentemente ignorati.</dd>
-</dl>
-
-<h3 id="Per_gli_sviluppatori_di_applicazioni_XUL_e_di_estensioni" name="Per_gli_sviluppatori_di_applicazioni_XUL_e_di_estensioni">Per gli sviluppatori di applicazioni XUL e di estensioni</h3>
-
-<dl>
- <dt><a href="it/Session_restore_API">Session restore API</a></dt>
- <dd>Aiuta a salvare e recuperare successivamente i dati di sessione in sessione.</dd>
-</dl>
-
-<dl>
- <dt>Feed content access API</dt>
- <dd><em>Questa API è ancora in stato di revisione; la documentazione verrà pubblicata in futuro.</em></dd>
-</dl>
-
-<dl>
- <dt><a href="it/SAX">Supporto a SAX</a></dt>
- <dd>API di un parser XML basata sugli eventi.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Installare_plugin_di_ricerca_dalle_pagine_web">Installare plugin di ricerca dalle pagine web</a></dt>
- <dd>E' possibile installare in Firefox un nuovo motore di ricerca tramite JavaScript. Il plugin di ricerca può essere scritto utilizzando anche OpenSearch o il formato Sherlock.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/Aggiungere_fornitori_di_dati_anti-phishing">Aggiungere fornitori di dati anti-phishing</a></dt>
- <dd>E' possibile migliorare la protezione anti-phishing aggiungendo alcuni fornitori di fati per la navigazione sicura.</dd>
-</dl>
-
-<dl>
- <dt><a href="it/MozStorage">mozStorage</a></dt>
- <dd>Firefox 2 introduce mozStorage, un'architettura di database basata su SqlLite.</dd>
-</dl>
-
-<dl>
- <dt>Le pratiche migliori per il versioning delle estensioni</dt>
- <dd>Come utilizzare i numeri di versione.</dd>
-</dl>
-
-<h2 id="Nuove_funzionalit.C3.A0_per_gli_utenti_finali" name="Nuove_funzionalit.C3.A0_per_gli_utenti_finali">Nuove funzionalità per gli utenti finali</h2>
-
-<p>Firefox 2 offre una versione migliorata dell'interfaccia utente impiegata nelle versioni precedenti, a cui sono state aggiunte varie caratteristiche di sicurezza finalizzate a rendere la vostra navigazione più semplice e piacevole di prima.</p>
-
-<h3 id="Esperienza_utente" name="Esperienza_utente">Esperienza utente</h3>
-
-<ul>
- <li>Il <strong>controllo ortografico nelle aree di testo</strong> permette all'utente di compilare i form in maniera più sicura.</li>
- <li>I <strong>microsommari</strong> consentono di creare bookmark che mostrino informazioni rilevate dal sito a cui si riferiscono. Queste informazioni sono aggiornate automaticamente.</li>
- <li>L'interfaccia utente dell' <strong>Extension Manager</strong> è stata migliorata.</li>
- <li>Il <strong>search engine manager</strong> permette di riordinare e rimuovere i motori di ricerca mostrati nella barra.</li>
- <li>I miglioramenti al <strong>tabbed browsing</strong> comprendono un bottone di chiusura per ogni scheda, riapertura dell'ultima scheda aperta quando si chiude la scheda corrente e preferenze semplificate.</li>
- <li>Il <strong>rilevamento automatico dei motori di ricerca</strong> propone all'utente di installare automaticamente nella barra di ricerca i siti visitati, se forniscono un plugin di ricerca.</li>
- <li>I <strong>suggerimenti di ricerca</strong> sono dei suggerimenti che appaiono mentre si digitano i termini da ricercare.</li>
-</ul>
-
-<h3 id="Sicurezza_e_Privacy" name="Sicurezza_e_Privacy">Sicurezza e Privacy</h3>
-
-<ul>
- <li><strong>Funzionalità anti-phishing</strong> per avvisare gli utenti se il sito web che si sta vedendo sembra contraffatto.</li>
-</ul>
-
-<h2 id="Argomenti_correlati" name="Argomenti_correlati">Argomenti correlati</h2>
-
-<ul>
- <li><a href="it/Gecko">Gecko</a></li>
- <li><a href="it/XULRunner">XULRunner</a></li>
- <li><a href="it/Firefox_1.5_per_Sviluppatori">Firefox 1.5 per Sviluppatori</a></li>
-</ul>
-
-<p>{{ languages( { "en": "en/Firefox_2_for_developers", "fr": "fr/Firefox_2_pour_les_d\u00e9veloppeurs", "ja": "ja/Firefox_2_for_developers", "pt": "pt/Firefox_2_para_desenvolvedores" } ) }}</p>
diff --git a/files/it/mozilla/firefox/releases/40/index.html b/files/it/mozilla/firefox/releases/40/index.html
deleted file mode 100644
index 0b57ccb6ba..0000000000
--- a/files/it/mozilla/firefox/releases/40/index.html
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Firefox 40 per sviluppatori
-slug: Mozilla/Firefox/Releases/40
-tags:
-  - Firefox
-  - Rilasci
-translation_of: Mozilla/Firefox/Releases/40
----
-<div>{{FirefoxSidebar}}</div><div class="column-container zone-callout"><a href="https://nightly.mozilla.org/" style="float: right; margin-bottom: 20px; padding: 10px; text-align: center; border-radius: 4px; display: inline-block; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Installa Firefox Nightly</a></div>
-
-<h2 id="Novità_per_Sviluppatori_Web">Novità per Sviluppatori Web</h2>
-
-<h3 id="Strumenti_per_sviluppatore">Strumenti per sviluppatore</h3>
-
-<ul>
- <li>I messaggi {{domxref("Console")}} API da {{domxref("SharedWorker")}} o {{domxref("ServiceWorker")}} adesso vengono mostrati nella console web ({{bug(1125205)}}).</li>
-</ul>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li>Le regole prefissate (<code>-moz-</code>) per {{cssxref("text-decoration-color")}}, {{cssxref("text-decoration-line")}}, e {{cssxref("text-decoration-style")}} sono state rimosse ({{bug(1097922)}}).</li>
- <li>La proprietà {{cssxref("text-align")}} adesso supporta il valore <code>match-parent</code> ({{bug(645642)}}).</li>
- <li>Nella modalità Quirks, il valore predefinito per {{cssxref("empty-cells")}} adesso è <code>show</code>, come nella modalità standard ({{bug(1020400)}}).</li>
-</ul>
-
-<h3 id="HTML">HTML</h3>
-
-<p><em>Nessuna novità.</em></p>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<ul>
- <li>Il codice illegibile dopo la dichiarazione {{jsxref("Statements/return", "return")}} (inclusa l'espressione illegibile dopo {{jsxref("Statements/return", "semicolon-less return statements", "#Automatic_semicolon_insertion", 1)}}) adesso mostreranno un avvertimento nella console ({{bug(1005110)}}, {{bug(1151931)}}).</li>
- <li>{{jsxref("Symbol.match")}} è stato aggiunto ({{bug(1054755)}}).</li>
- <li>Passando un oggetto che ha una proprietà chiamata {jsxref("Symbol.match")}} con un valore {{Glossary("truthy")}} verso {{jsxref("String.prototype.startsWith")}}, {{jsxref("String.prototype.endsWith")}}, e {{jsxref("String.prototype.contains")}} adesso attiva un {{jsxref("TypeError")}} ({{bug(1054755)}}).</li>
- <li>La funzione {{jsxref("RegExp")}} richiama uno schema a sé, se chiamato senza {{jsxref("Operators/new", "new")}} e l'oggetto dello schema ha una proprietà chiamata {{jsxref("Symbol.match")}} con un valore {{Glossary("truthy")}}, e la proprietà <code>constructor </code>dell'oggetto dello schema è uguale a lla funzione {{jsxref("RegExp")}}. ({{bug(1147817)}}).</li>
- <li>Il supporto per il non-standard for-in destrutturante JS1.7 è stato abbandonato ({{bug(1083498)}}).</li>
- <li><a href="/en-US/docs/Web/JavaScript/Reference/Statements/for...in#Firefox-specific_notes">L'inizializzatore di espressioni non-standard </a>è stato rimosso dai cicli <a href="/en-US/docs/Web/JavaScript/Reference/Statements/for...in">for...in</a> ({{bug(748550)}}).</li>
- <li>\u{xxxxxx} unicode codepoint in {{jsxref("Global_Objects/String", "string literals", "", 1)}} è stato aggiunto ({{bug(320500)}}).</li>
- <li>{{jsxref("String.prototype.includes", "String.prototype.contains", "#String.prototype.contains")}} è stato sostituito con {{jsxref("String.prototype.includes")}}, <code>String.prototype.contains</code> è mantenuto come alias ({{bug(1102219)}}).</li>
-</ul>
-
-<h3 id="InterfacceAPIsDOM">Interfacce/APIs/DOM</h3>
-
-<ul>
- <li>Il CSS Font Loading API ora è abilitato di default nelle versioni Nightly e Developer Edition ({{bug(1088437)}}). E' ancora disattivato di default nella Beta e Release browsers.</li>
- <li>Miglioramento nella nostra implementazione sperimentale di Web Animations: {{domxref("AnimationPlayer.currentTime")}} ora può anche essere impostato ({{bug(1072037)}}).</li>
- <li>WebRTC: il {{event("negotiationneeded")}} adesso è anche inviato per negoziazioni iniziali, non solamente per ri-negoziazioni ({{bug(1149838)}}).</li>
- <li>Quando inadatto ad analizzare il {{htmlattrxref("srcset", "image")}}, il metodo {{domxref("HTMLImageElement.currentSrc")}} non ritorna più <code>null</code> ma <code>""</code>, come richiesto dall'ultima specifica ({{bug(1139560)}}).</li>
- <li>Il <a href="/en-US/docs/Web/API/Push_API">Push API</a> è stato implementato ({{bug(1038811)}}).</li>
- <li>Nuove estensioni per il <a href="/en-US/docs/Web/API/Web_Audio_API">Web Audio API</a>:
-  <ul>
-   <li>La proprietà {{domxref("AudioContext.state")}} come anche i metodi {{domxref("AudioContext.suspend()")}}, {{domxref("AudioContext.resume()")}}, e {{domxref("AudioContext.close()")}} sono stati aggiunti ({{bug(1094764)}}).</li>
-   <li>{{domxref("AudioBufferSourceNode")}} ora implementa l'attributo {{domxref("AudioBufferSourceNode.detune")}} <a href="/it/docs/DOM/AudioParam#k-rate">k-rate</a> ({{bug(1153783)}}).</li>
-  </ul>
- </li>
- <li>Come per le immagini, Firefox ora restringe {{domxref("Window.requestAnimationFrame()")}} per non-visible {{HTMLElement("iframe")}} ({{bug(1145439)}}).</li>
- <li>{{domxref("Navigator.taintEnabled")}} non è più disponibile per i Web workers ({{bug(1154878)}}).</li>
- <li>{{domxref("DataStore")}} ora è disponibile nei Web workers ({{bug(916196)}}).</li>
- <li>L'interfaccia <code>CSSCharsetRule</code> è stata rimossa e  tali oggetti non sono più disponibili nel CSSOM ({{bug(1148694)}}). Questo corrisponde la spec (recentemente adattata) e il comportamento di Chrome.</li>
- <li>La proprietà {{domxref("Console.timeStamp")}} è stata aggiunta ({{bug(922221)}}).</li>
- <li>Lieve miglioramento nel nostro <a href="/en-US/docs/Web/API/ServiceWorker_API">Service Worker API</a>: il metodo {{domxref("ServiceWorkerRegistration.update()", "update()")}} è stato spostato da {{domxref("ServiceWorkerGlobalScope")}} a {{domxref("ServiceWorkerRegistration")}} ({{bug(1131350)}}).</li>
- <li>{{domxref("IDBTransaction")}} adesso sono non-durable di default ({{bug(1112702)}}). Questo favorisce prestazioni superaffidabili e corrisponde a ciò che gli altri browsers stanno facendo.</li>
-</ul>
-
-<h3 id="MathML">MathML</h3>
-
-<p><em>Nessuna novità.</em></p>
-
-<h3 id="SVG">SVG</h3>
-
-<p><em>Nessuna novità.</em></p>
-
-<h3 id="AudioVideo">Audio/Video</h3>
-
-<p><em>Nessuna novità.</em></p>
-
-<h2 id="Networking">Networking</h2>
-
-<p><em>Nessuna novità.</em></p>
-
-<h2 id="Sicurezza">Sicurezza</h2>
-
-<p><em>Nessuna novità.</em></p>
-
-<h2 id="Novità_per_componenti_aggiuntivi_e_sviluppatori_Mozilla">Novità per componenti aggiuntivi e sviluppatori Mozilla</h2>
-
-<h3 id="XUL">XUL</h3>
-
-<p><em>Nessuna novità.</em></p>
-
-<h3 id="Moduli_di_codice_JavaScript">Moduli di codice JavaScript</h3>
-
-<ul>
- <li>Dict.jsm è stato rimosso {{bug(1123309)}}. Usate invece {{jsxref("Map")}}.</li>
-</ul>
-
-<h3 id="XPCOM">XPCOM</h3>
-
-<p><em>Nessuna novità.</em></p>
-
-<h3 id="Altro">Altro</h3>
-
-<ul>
- <li>Places Keywords API sono state deprecate e saranno rimosse presto ({{bug(1140395)}}).</li>
-</ul>
-
-<h2 id="Vedi_anche">Vedi anche</h2>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Firefox/Releases/40/Site_Compatibility">Compatibilità siti per Firefox 40</a></li>
-</ul>
-
-<h2 id="Vecchie_versioni">Vecchie versioni</h2>
-
-<p>{{Firefox_for_developers('39')}}</p>
diff --git a/files/it/mozilla/firefox/releases/42/index.html b/files/it/mozilla/firefox/releases/42/index.html
deleted file mode 100644
index 5d02b8ce79..0000000000
--- a/files/it/mozilla/firefox/releases/42/index.html
+++ /dev/null
@@ -1,189 +0,0 @@
----
-title: Firefox 42 for developers
-slug: Mozilla/Firefox/Releases/42
-tags:
-  - Firefox
-  - Note di rilascio
-  - Rilasci
-translation_of: Mozilla/Firefox/Releases/42
----
-<div>{{FirefoxSidebar}}</div>
-
-<div class="column-container zone-callout"><a href="https://www.mozilla.org/firefox/developer/" style="float: right; margin-left: 10px; margin-bottom: 20px; padding: 10px; text-align: center; border-radius: 4px; display: inline-block; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Installa Firefox Developer Edition </a> <span>Firefox 42 was released on November 3, 2015. This article lists key changes that are useful not only for web developers, but also Firefox and Gecko developers as well as add-on developers.</span></div>
-
-<h2 id="Modifiche_per_gli_sviluppatori">Modifiche per gli sviluppatori</h2>
-
-<h3 id="Strumenti_per_gli_sviluppatori">Strumenti per gli sviluppatori</h3>
-
-<p>In evidenza:</p>
-
-<ul>
- <li><a href="/en-US/docs/Tools/Remote_Debugging/Debugging_Firefox_for_Android_over_Wifi">Debugging Firefox per Android tramite Wifi</a></li>
- <li><a href="/en-US/docs/Tools/WebIDE/Setting_up_runtimes#Configuring_Simulators">Firefox OS Simulator configuration in WebIDE</a></li>
- <li><a href="/en-US/docs/Tools/Page_Inspector/How_to/Edit_CSS_filters#Saving_filter_presets">CSS filter presets</a></li>
-</ul>
-
-<p><a class="external external-icon" href="https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&amp;classification=Client%20Software&amp;chfieldto=2015-08-10&amp;query_format=advanced&amp;chfield=resolution&amp;chfieldfrom=2015-06-29&amp;chfieldvalue=FIXED&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;component=Developer%20Tools&amp;component=Developer%20Tools%3A%203D%20View&amp;component=Developer%20Tools%3A%20Canvas%20Debugger&amp;component=Developer%20Tools%3A%20Console&amp;component=Developer%20Tools%3A%20Debugger&amp;component=Developer%20Tools%3A%20Framework&amp;component=Developer%20Tools%3A%20Graphic%20Commandline%20and%20Toolbar&amp;component=Developer%20Tools%3A%20Inspector&amp;component=Developer%20Tools%3A%20Memory&amp;component=Developer%20Tools%3A%20Netmonitor&amp;component=Developer%20Tools%3A%20Object%20Inspector&amp;component=Developer%20Tools%3A%20Performance%20Tools%20%28Profiler%2FTimeline%29&amp;component=Developer%20Tools%3A%20Responsive%20Mode&amp;component=Developer%20Tools%3A%20Scratchpad&amp;component=Developer%20Tools%3A%20Source%20Editor&amp;component=Developer%20Tools%3A%20Storage%20Inspector&amp;component=Developer%20Tools%3A%20Style%20Editor&amp;component=Developer%20Tools%3A%20User%20Stories&amp;component=Developer%20Tools%3A%20Web%20Audio%20Editor&amp;component=Developer%20Tools%3A%20WebGL%20Shader%20Editor&amp;component=Developer%20Tools%3A%20WebIDE&amp;product=Firefox&amp;list_id=12478437">All devtools bugs fixed between Firefox 41 and Firefox 42</a>.</p>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li>Vertical {{cssxref('writing-mode')}} is now supported with rtl scripts ({{bug(1131451)}}).</li>
- <li>Non-standard proprieties like {{cssxref('-moz-margin-start')}} are now aliases of their standard counterpart ({{cssxref('margin-inline-start')}}, …). Previously, it was the opposite. This affects the value returned by {{domxref('CSSStyleDeclaration.cssText')}} and iteration of the properties in a style ruleand iteration of the properties in a style rule, that both use the canonical form ({{bug(1118103)}}).</li>
-</ul>
-
-<h3 id="HTML">HTML</h3>
-
-<ul>
- <li>The {{htmlattrxref("referrer", "input")}} attribute of the {{HTMLElement("input")}} ({{bug(1166910)}}), {{HTMLElement("a")}} and {{HTMLElement("area")}} ({{bug(1174913)}}) has been implemented.</li>
-</ul>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<ul>
- <li>The {{jsxref("Reflect")}} object has been implemented ({{bug(987514)}}).</li>
- <li>The implementation of the {{jsxref("Proxy")}} {{jsxref("Global_Objects/Proxy/handler/ownKeys", "handler.ownKeys()")}} trap has been updated to match the final ES2015 specification ({{bug(1049662)}}).</li>
- <li>Calling {{jsxref("Map")}}, {{jsxref("Set")}}, or {{jsxref("WeakMap")}} without {{jsxref('Operators', 'new')}}, will now throw a {{jsxref("TypeError")}} ({{bug(1083752)}}).</li>
-</ul>
-
-<h3 id="InterfacesAPIsDOM">Interfaces/APIs/DOM</h3>
-
-<h4 id="DOM_HTML_DOM">DOM &amp; HTML DOM</h4>
-
-<ul>
- <li>{{domxref('Event.offsetX')}} and {{domxref('Event.offsetY')}} have been added ({{bug(69787)}}).</li>
- <li>The {{domxref("HTMLInputElement")}} interface has been experimentally extended to handle the upload of directories ({{bug(1164310)}}). These four members are now available behind the <code>dom.input.dirpicker</code> preference:
-  <ul>
-   <li>{{domxref("HTMLInputElement.directory")}}</li>
-   <li>{{domxref("HTMLInputElement.isFilesAndDirectoriesSupported")}}</li>
-   <li>{{domxref("HTMLInputElement.getFilesAndDirectories()")}}</li>
-   <li>{{domxref("HTMLInputElement.chooseDirectory()")}}</li>
-  </ul>
- </li>
- <li>The {{domxref("Directory")}} interface has been experimentally extended ({{bug(1177688)}}). The two members {{domxref("Directory.path")}} and {{domxref("Directory.getContents")}} are now available.</li>
- <li>The <code>HTMLMediaElement.mozSrcObject</code> has been renamed in {{domxref('HTMLMediaElement.srcObject')}} ({{bug(1175523)}}).</li>
-</ul>
-
-<h4 id="Service_Workers">Service Workers</h4>
-
-<ul>
- <li>{{domxref('Request.context')}} has been removed ({{bug(1188062)}}).</li>
- <li>The <a href="/en-US/docs/Web/API/Push_API">Push API</a> has been activated by default on Firefox for Desktop ({{bug(1153499)}}), but only on the Nightly/Dev Edition/Beta channels. It is being deactivated by default in the Release channel until consumer UX and debugging features have been properly implemented ({{bug(1207875)}}.) You can still activate it by enabling the <span id="summary_alias_container"><span id="short_desc_nonedit_display"><code>dom.push.enabled</code> pref in <a>about:config</a>.</span></span></li>
- <li>The {{domxref("PushManager.hasPermission()")}} method has been deprecated in the spec, and replaced with the {{domxref("PushManager.permissionState()")}} method. Firefox has updated its implementation to reflect this ({{bug("1183853")}}.)</li>
- <li>Service-worker-related additions to the <a href="/en-US/docs/Web/API/Notifications_API">Notifications API</a> have been implemented ({{bug(1114554)}}), but are disabled in this release.</li>
-</ul>
-
-<h4 id="Web_Animations_API">Web Animations API</h4>
-
-<p>Our experimental implementation of <a href="/en-US/docs/Web/API/Web_Animations_API">Web Animations API</a> have been extended to support:</p>
-
-<ul>
- <li>The {{domxref('AnimationPlayer.playbackRate')}} property ({{bug(1127380)}}).</li>
- <li>The {{domxref('CSSAnimation')}} and {{domxref('CSSTransition')}} interfaces ({{bug(1178186)}}).</li>
- <li>The {{domxref('Animation.reverse()')}} method ({{bug(1150808)}}).</li>
- <li>The {{domxref('AnimationPlaybackEvent')}} interface has been added and {{event('cancel')}} and {{event('finish')}} are now fired on {{domxref('Animation')}} ({{bug(1178664)}}).</li>
-</ul>
-
-<h4 id="Web_Components">Web Components</h4>
-
-<p>Our experimental implementation of the <a href="/en-US/docs/Web/Web_Components/Shadow_DOM">Shadow DOM</a> has been modified:</p>
-
-<ul>
- <li>When trying to invoke {{domxref('Node.cloneNode()')}} on a {{domxref('ShadowRoot')}}, throws a <code>DataCloneError</code> exception ({{bug(1176757)}}).</li>
- <li>When invoking {{domxref('Document.importNode()')}} with a {{domxref('ShadowRoot')}} as an argument, we now throws a <code>NotSupportedError</code> exception ({{bug(1177914)}}).</li>
- <li>When invoking {{domxref('Document.adoptNode()')}} with a {{domxref('ShadowRoot')}} as an argument, we now throws a <code>HierarchyRequestError</code> exception ({{bug(1177991)}}).</li>
-</ul>
-
-<h4 id="WebGL">WebGL</h4>
-
-<ul>
- <li>WebGL2 {{domxref('WebGLTransformFeedback')}} has been implemented ({{bug(1048724)}}).</li>
- <li>The <code>WEBGL_debug_renderer_info</code> extension has been turned on by default ({{bug(1171228)}}).</li>
- <li>To obtain a WebGL2 context, {{domxref('HTMLCanvasElement.getContext()')}} now takes <code>webgl2</code> instead of <code>experimental-webgl2</code> previously ({{bug(1187174)}}).</li>
-</ul>
-
-<h4 id="WebRTC">WebRTC</h4>
-
-<ul>
- <li>The <code>RTCICECandidatePairStats.mozPriority</code> has been renamed to {{domxref('RTCICECandidatePairStats.priority')}} ({{bug(1184426)}}).</li>
-</ul>
-
-<h4 id="New_APIs">New APIs</h4>
-
-<ul>
- <li>The {{domxref("ImageBitmap")}} interface and the {{domxref("ImageBitmapFactories.createImageBitmap","createImageBitmap()")}} method have been implemented. They are available on regular window scripts and in Web workers and allow efficient posting of images between window and worker contexts ({{bug(1044102)}}).</li>
-</ul>
-
-<h4 id="Miscellaneous">Miscellaneous</h4>
-
-<ul>
- <li>The {{domxref('IDBCursorWithValue')}} interface is now available in <a href="/en-US/docs/Web/API/Web_Workers_API">Web workers</a> ({{bug(1188115)}}).</li>
- <li>Error events sent in <a href="/en-US/docs/Web/API/Web_Workers_API">Web workers</a> doesn't bubble anymore ({{bug(1188141)}}).</li>
- <li><a href="/en-US/docs/Web/API/Media_Stream_Extensions">Media Source Extensions</a> (MSE) has been activated for all Web sites, and no more for a white list of sites ({{bug(1185611)}}).</li>
- <li>The non-standard and deprecated {{domxref('Window.mozRequestAnimationFrame()')}} has been removed ({{bug(909154)}}). Use the standard {{domxref('Window.requestAnimationFrame()')}} instead.</li>
-</ul>
-
-<h3 id="MathML">MathML</h3>
-
-<p><em>No change.</em></p>
-
-<h3 id="SVG">SVG</h3>
-
-<p><em>No change.</em></p>
-
-<h3 id="AudioVideo">Audio/Video</h3>
-
-<p><em>No change.</em></p>
-
-<h2 id="HTTP">HTTP</h2>
-
-<p><em>No change.</em></p>
-
-<h2 id="Networking">Networking</h2>
-
-<ul>
- <li>The CSP <code><a href="/Web/Security/CSP/CSP_policy_directives#upgrade-insecure-requests">upgrade-insecure-requests</a></code> directive has been implemented ({{bug(1139297)}}).</li>
-</ul>
-
-<h2 id="Sicurezza">Sicurezza</h2>
-
-<ul>
- <li>EV certificates with a validity greater than 39 months are now considered and handled as DV certificates ({{bug(1145679)}}).</li>
-</ul>
-
-<h2 id="Cambiamenti_per_gli_add-on_e_Mozilla_developers">Cambiamenti per gli add-on e Mozilla developers</h2>
-
-<h3 id="Interfaces">Interfaces</h3>
-
-<h4 id="nsIContentPolicy">nsIContentPolicy</h4>
-
-<ul>
- <li>The <code><strong>TYPE_EMBED</strong></code> constant has been added to <code><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIContentPolicy" title="">nsIContentPolicy</a></code> to allow Gecko internals and add-on code to better differentiate different types of requests. Previously, <code><strong>TYPE_OBJECT</strong></code> was used for these cases ({{bug(1148030)}}).</li>
- <li>Similarly, the <strong><code>TYPE_SUBDOCUMENT</code></strong> constants has been split into <code><strong>TYPE_FRAME</strong></code> and <strong><code>TYPE_IFRAME</code></strong> ({{bug(1148044)}}).</li>
-</ul>
-
-<h3 id="XUL">XUL</h3>
-
-<p><em>No change.</em></p>
-
-<h3 id="JavaScript_code_modules">JavaScript code modules</h3>
-
-<p><em>No change.</em></p>
-
-<h3 id="XPCOM">XPCOM</h3>
-
-<p><em>No change.</em></p>
-
-<h3 id="Other">Other</h3>
-
-<p><em>No change.</em></p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://www.fxsitecompat.com/en-US/versions/42/">Site Compatibility for Firefox 42</a></li>
-</ul>
-
-<h2 id="Older_versions">Older versions</h2>
-
-<p>{{Firefox_for_developers('41')}}</p>
diff --git a/files/it/mozilla/firefox/releases/59/index.html b/files/it/mozilla/firefox/releases/59/index.html
deleted file mode 100644
index 7d1cec5737..0000000000
--- a/files/it/mozilla/firefox/releases/59/index.html
+++ /dev/null
@@ -1,203 +0,0 @@
----
-title: Firefox 59 per sviluppatori
-slug: Mozilla/Firefox/Releases/59
-translation_of: Mozilla/Firefox/Releases/59
----
-<div>{{FirefoxSidebar}}</div><p class="summary"><span id="result_box" lang="it"><span>Questo articolo fornisce informazioni sulle modifiche in Firefox 59 che interesseranno gli sviluppatori. </span></span> Firefox 59 è l'attuale <a href="https://www.mozilla.org/en-US/firefox/channel/desktop/#beta">versione Beta di Firefox</a>, che  sarà pubblicata il 13 marzo<a href="https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates"> 2018</a>.</p>
-
-<h2 id="Cambios_pro_le_disveloppatores_de_web">Cambios pro le disveloppatores de web</h2>
-
-<h3 id="Utensiles_pro_le_disveloppatores_de_web">Utensiles pro le disveloppatores de web</h3>
-
-<ul>
- <li>Le scheda de responsa de <a href="/en-US/docs/Tools/Network_Monitor">Network Monitor</a> ora monstra un <a href="/en-US/docs/Tools/Network_Monitor#HTML_preview">vista preliminar del HTML rendite</a> — si le responsa es HTML ({{bug(1353319)}}).</li>
- <li>Cookie information shown in the Storage Inspector (see <a href="/en-US/docs/Tools/Storage_Inspector#Cookies">Cookies</a>) now includes a <em>sameSite</em> column showing what the same-site status of each cookie is ({{bug(1298370)}}).</li>
- <li>The <a href="/en-US/docs/Tools/Rulers">Rulers</a> tool now includes a readout showing the current dimensions of the viewport ({{bug(1402633)}}).</li>
- <li>In <a href="/en-US/docs/Tools/Responsive_Design_Mode">Responsive Design Mode</a>, you can now set the screen dimensions using the cursor keys ({{bug(1421663)}}). See the <a href="/en-US/docs/Tools/Responsive_Design_Mode#Setting_screen_size">Setting screen size</a> section for more details.</li>
- <li>The <em>Raw headers</em> display in the <a href="/en-US/docs/Tools/Network_Monitor">Network Monitor</a> <em>Headers</em> tab now includes the response's status code ({{bug(1419401)}}).</li>
-</ul>
-
-<h3 id="HTML">HTML</h3>
-
-<p>The {{HTMLElement("textarea")}} element's {{htmlattrxref("autocomplete", "textarea")}} attribute has been implemented. This lets you enable or disable form auto-fill for the element.</p>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li>The {{cssxref("overscroll-behavior")}} property and its associated longhand properties — {{cssxref("overscroll-behavior-x")}} and {{cssxref("overscroll-behavior-y")}} — have been implemented ({{bug(951793)}}), and it has been enabled by default on all releases ({{bug(1428879)}}).</li>
- <li>The behavior of "unusual elements" (elements that aren’t rendered purely by CSS box concepts such as replaced elements) when given a {{cssxref("display")}} value of <code>contents</code> has been updated as per spec ({{bug(1427292)}}). See <a href="https://drafts.csswg.org/css-display/#unbox">Appendix B: Effects of display: contents on Unusual Elements</a> for exactly what the specced behaviors are.</li>
- <li>{{cssxref("position")}} <code>sticky</code> is now supported on appropriate <a href="/en-US/docs/Learn/HTML/Tables">HTML table</a> parts (e.g. {{htmlelement("th")}} elements) ({{bug(975644)}}).</li>
- <li>{{cssxref("calc()")}} is now supported in {{cssxref("&lt;color&gt;")}} values — <code>rgb()</code>, <code>rgba()</code>, <code>hsl()</code>, and <code>hsla()</code> ({{bug(984021)}}).</li>
- <li>In Firefox 59, support for {{cssxref("calc()")}} in <a href="/en-US/docs/Web/CSS/Media_Queries">media query</a> values has been added {{bug(1396057)}}.</li>
- <li>The {{cssxref("@document")}} at-rule has been limited to use only in user and UA sheets ({{bug(1035091)}}).</li>
- <li>Implement the {{cssxref("font-optical-sizing")}} property ({{bug(1435692)}}).</li>
-</ul>
-
-<h3 id="SVG">SVG</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="APIs">APIs</h3>
-
-<h4 id="New_APIs">New APIs</h4>
-
-<p>{{domxref("PointerEvent","PointerEvents")}} have been enabled in Firefox Desktop ({{bug(1411467)}}).</p>
-
-<h4 id="DOM">DOM</h4>
-
-<ul>
- <li>The {{domxref("EventTarget.EventTarget()","EventTarget()")}} constructor has been implemented ({{bug(1379688)}}).</li>
- <li>The {{domxref("Response.Response()","Response()")}} constructor can now accept a <code>null</code> value for its <code>body</code> parameter, as per spec ({{bug(1303025)}}).</li>
-</ul>
-
-<h4 id="DOM_events">DOM events</h4>
-
-<p>The {{domxref("Event.composedPath()")}} method has been implemented ({{bug(1412775)}}).</p>
-
-<h4 id="Service_workers">Service workers</h4>
-
-<ul>
- <li>The service worker <a href="/en-US/docs/Web/API/Clients">Clients API</a> can now find and communicate with windows in a separate browser process ({{bug(1293277)}}) .</li>
- <li>Nested about:blank and about:srcdoc iframes will now inherit their parent's controlling service worker. Fixed in ({{bug(1293277)}}) and ({{bug(1426979)}}).</li>
- <li>When a service worker provides a {{domxref("Response")}} to {{domxref("FetchEvent.respondWith()")}}, the {{domxref("Response.url")}} value will not be propagated to the intercepted network request as the final resolved URL.  In the past the {{domxref("Request.url","FetchEvent.request.url")}} was used for this instead.  This means, for example, if a service worker intercepts a stylesheet or worker script, then the provided <code>Response.url</code> will be used to resolve any relative {{cssxref("@import")}} or {{domxref("WorkerGlobalScope.importScripts()","importScripts()")}} subresource loads ({{bug(1222008)}}).</li>
- <li><code>FetchEvent.respondWith()</code> will now trigger a network error if the {{domxref("Request.mode","FetchEvent.request.mode")}} is <code>"same-origin"</code> and the provided {{domxref("Response.type")}} is <code>"cors"</code>. ({{bug(1222008)}})</li>
-</ul>
-
-<h4 id="Media_and_WebRTC">Media and WebRTC</h4>
-
-<ul>
- <li>The {{domxref("MediaStreamTrack")}} property {{domxref("MediaStreamTrack.muted")}}, along with the events {{event("mute")}} and {{event("unmute")}} and the corresponding event handlers, {{domxref("MediaStreamTrack.onmute", "onmute")}} and {{domxref("MediaStreamTrack.onmute", "onunmute")}}, have been implemented. A track's <code>muted</code> state indicates that the track is not currently able to provide media data.
-
-  <div class="note"><strong>Note:</strong> The <code>muted</code> state of a track isn't useful for what's typically thought of as muting and unmuting a track. Instead, use the {{domxref("MediaStreamTrack.enabled", "enabled")}} property; setting <code>enabled</code> to <code>false</code> causes the track to output only empty frames.</div>
- </li>
- <li>The {{domxref("RTCRtpReceiver")}} methods {{domxref("RTCRtpReceiver.getContributingSources", "getContributingSources()")}} and {{domxref("RTCRtpReceiver.getSynchronizationSources", "getSynchronizationSources()")}} have been implemented to provide information about the sources of each RTP stream. However, a specification change occurred before release and we have disabled these by default behind the preference <code>media.peerconnection.rtpsourcesapi.enable</code> ({{bug(1363667)}}, {{bug(1430213)}}, and {{bug(1433236)}}.</li>
- <li>The {{domxref("RTCRtpTransceiver")}} interface has now been implemented, since the Firefox implementation of WebRTC now supports transceivers, with <code>RTCPeerConnection</code> and other interfaces updated to use them per the latest specification.</li>
- <li>The {{domxref("RTCPeerConnection.addTransceiver()")}} method has been added. In addition, the behavior of {{domxref("RTCPeerConnection.addTrack", "addTrack()")}} has been updated to create a transceiver as required.</li>
- <li>Support for <a href="/en-US/docs/Web/API/WebVTT_API">WebVTT</a> regions was implemented in Firefox 58 but disabled by default. They're now available by default ({{bug(1415805)}}).</li>
- <li>Firefox now supports WebVTT <code>REGION</code> definition blocks whose settings list has one setting per line instead of all of the settings being on the same line of the WebVTT file ({{bug(1415821)}}.</li>
-</ul>
-
-<h4 id="Canvas_and_WebGL">Canvas and WebGL</h4>
-
-<p><em>No changes.</em></p>
-
-<h3 id="CSSOM">CSSOM</h3>
-
-<p>The {{domxref("CSSNamespaceRule")}} interface and its <code>namespaceURL</code> and <code>prefix</code> properties have been implemented ({{bug(1326514)}}).</p>
-
-<h3 id="HTTP">HTTP</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="Security">Security</h3>
-
-<ul>
- <li>Top-level navigation to <code>data://</code> URIs has been blocked {{bug(1401895)}}. See <a href="https://blog.mozilla.org/security/2017/11/27/blocking-top-level-navigations-data-urls-firefox-58/">Blocking Top-Level Navigations to data URLs for Firefox 58</a> for more details.</li>
- <li>The <code>SAMEORIGIN</code> directive of the {{httpheader("X-Frame-Options")}} header has been changed so that it checks not only the top-level IFrame is in the same origin, but all its ancestors as well ({{bug(725490)}}).</li>
- <li>Image resources loaded from different origins to the current document are no longer able to trigger HTTP authentication dialogs ({{bug(1423146)}}). See <a href="https://www.fxsitecompat.com/en-CA/docs/2017/http-auth-dialog-can-no-longer-be-triggered-by-cross-origin-images/">HTTP auth dialog can no longer be triggered by cross-origin images</a> for more details.</li>
- <li>HTTP authentication now uses <code>utf-8</code> encoding for usernames and passwords (rather than <code>ISO-8859-1</code>) for parity with other browsers, and to avoid potential problems as described in {{bug(1419658)}}.</li>
-</ul>
-
-<h3 id="Plugins">Plugins</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="Other">Other</h3>
-
-<p><em>No changes.</em></p>
-
-<h2 id="Removals_from_the_web_platform">Removals from the web platform</h2>
-
-<h3 id="HTML_2">HTML</h3>
-
-<p>The non-standard <code>version</code> parameter of the {{htmlelement("script")}} element's {{htmlattrxref("type","script")}} attribute (e.g.  <code>type="application/javascript;version=1.8"</code>) has been removed ({{bug(1428745)}}).</p>
-
-<h3 id="CSS_2">CSS</h3>
-
-<ul>
- <li>The proprietary <code>mozmm</code> {{cssxref("&lt;length&gt;")}} unit has been removed ({{bug(1416564)}}).</li>
- <li>The proprietary {{cssxref("-moz-border-top-colors")}}, {{cssxref("-moz-border-right-colors")}}, {{cssxref("-moz-border-bottom-colors")}}, and {{cssxref("-moz-border-left-colors")}} properties have been limited to usage in chrome code only ({{bug(1417200)}}).</li>
-</ul>
-
-<h3 id="JavaScript_2">JavaScript</h3>
-
-<ul>
- <li>Non-standard <a href="/en-US/docs/Web/JavaScript/Reference/Statements/try...catch#Conditional_catch_clauses">conditional catch clauses</a> have been removed ({{bug(1228841)}}).</li>
-</ul>
-
-<h3 id="APIs_2">APIs</h3>
-
-<ul>
- <li>The non-standard method <code>Event.getPreventDefault()</code> has been removed. You should instead use the {{domxref("Event.defaultPrevented")}} property to determine whether or not {{domxref("Event.preventDefault", "preventDefault()")}} was called on the {{domxref("Event")}}.</li>
- <li>The propretary <code><a href="/en-US/docs/Archive/API/Navigator/mozNotification">Navigator.mozNotification</a></code> property and <code>DesktopNotification</code> interface have been removed, in favor of the standard <a href="/en-US/docs/Web/API/Notifications_API">Notifications API</a> ({{bug(952453)}}).</li>
- <li>The proprietary <code>window.external.addSearchEngine()</code> method has been removed ({{bug("862147")}}). Also see {{domxref("Window.sidebar")}} for more details.</li>
- <li>The non-standard Firefox-only {{domxref("HTMLMediaElement")}} property <code>mozAutoplayEnabled</code> has been removed.</li>
-</ul>
-
-<h3 id="SVG_2">SVG</h3>
-
-<p>Support for SMIL's <code>accessKey</code> feature has been removed ({{bug(1423098)}}).</p>
-
-<h3 id="Other_2">Other</h3>
-
-<p>Support for the non-standard <code>pcast://</code> and <code>feed://</code> protocols has been removed from Firefox ({{bug(1420622)}}).</p>
-
-<h2 id="Changes_for_add-on_and_Mozilla_developers">Changes for add-on and Mozilla developers</h2>
-
-<h3 id="WebExtensions">WebExtensions</h3>
-
-<ul>
- <li><a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/theme">Theme</a> updates:
-
-  <ul>
-   <li>new properties: <code>colors.background_tab_text</code>, <code>colors.toolbar_field_border</code></li>
-   <li>all color properties now support both Chrome-style arrays and CSS color values.</li>
-  </ul>
- </li>
- <li>New <a href="/en-US/Add-ons/WebExtensions/API/browserSettings">browser settings</a>:
-  <ul>
-   <li><a href="https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/contextMenuShowEvent"><code>contextMenuShowEvent</code></a></li>
-   <li><a href="https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/openBookmarksInNewTabs"><code>openBookmarksInNewTabs</code></a></li>
-   <li><a href="https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/openSearchResultsInNewTabs"><code>openSearchResultsInNewTabs</code></a></li>
-   <li><a href="https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/proxyConfig"><code>proxyConfig</code></a></li>
-  </ul>
- </li>
- <li>New <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs">tabs</a></code> APIs:
-  <ul>
-   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/captureTab">tabs.captureTab()</a></code></li>
-   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/hide">tabs.hide()</a></code></li>
-   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/show">tabs.show()</a></code></li>
-  </ul>
- </li>
- <li>The <code><a href="/en-US/docs/Archive/Add-ons/Legacy_Firefox_for_Android/API/NativeWindow/contextmenus">contextMenus</a></code> API now supports a <a href="/en-US/Add-ons/WebExtensions/API/menus/ContextType">"bookmark" context</a>.</li>
- <li>New <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/contentScripts">contentScripts</a></code> API enables runtime registration of content scripts.</li>
- <li>New <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/pageAction">pageAction</a></code>, <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/browserAction">browserAction</a></code>, <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/sidebarAction">SidebarAction</a></code> APIs:
-  <ul>
-   <li><code>browserAction/pageAction/sidebarAction.set*</code> functions now accept <code>null</code> to undo changes.</li>
-   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/browserAction/isEnabled">browserAction.isEnabled()</a></code>, <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/pageAction/isShown">pageAction.isShown()</a></code> , <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/sidebarAction/isOpen">sidebarAction.isOpen()</a></code> functions.</li>
-  </ul>
- </li>
- <li>New option in <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/page_action">page_action</a></code> to show page actions by default.</li>
- <li>New values for <code>protocol_handers</code>:
-  <ul>
-   <li>"ssb" for Secure Scuttlebutt communications</li>
-   <li>"dat" for DATproject</li>
-   <li>"ipfs", "ipns", "dweb" for IPFS</li>
-  </ul>
- </li>
- <li>New <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/privacy/websites">privacy.websites</a></code> setting "cookieConfig".</li>
- <li>Support in <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/cookies">cookies</a></code> API for <a href="/en-US/Add-ons/WebExtensions/API/cookies#First-party_isolation">first-party isolation</a>.</li>
- <li>New option <code>upgradeToSecure</code> in <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest">webRequest</a></code>.</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<p><a href="https://www.fxsitecompat.com/en-CA/versions/59/">Site compatibility for Firefox 59</a></p>
-
-<h2 id="Older_versions">Older versions</h2>
-
-<p>{{Firefox_for_developers(58)}}</p>
diff --git a/files/it/mozilla/firefox/releases/64/index.html b/files/it/mozilla/firefox/releases/64/index.html
deleted file mode 100644
index dd7d4e1532..0000000000
--- a/files/it/mozilla/firefox/releases/64/index.html
+++ /dev/null
@@ -1,184 +0,0 @@
----
-title: Firefox 64 for developers
-slug: Mozilla/Firefox/Releases/64
-translation_of: Mozilla/Firefox/Releases/64
----
-<div>{{FirefoxSidebar}}</div>
-
-<p class="summary">Questo articolo fornisce informazioni riguardo i cambiamenti in Firefox 64 che interesseranno gli sviluppatori. Firefox 64 è stato rilasciato l' 11 Dicembre, 2018.</p>
-
-<h2 id="Changes_for_web_developers">Changes for web developers</h2>
-
-<h3 id="Developer_tools">Developer tools</h3>
-
-<ul>
- <li>The <a href="/en-US/docs/Tools/Accessibility_inspector#Highlighting_of_UI_items">Accessibility info-bar</a> has been enhanced to include information about the color contrast ratio of text or images on the page ({{bug(1473037)}}).</li>
- <li><a href="/en-US/docs/Tools/Responsive_Design_Mode">Responsive Design Mode</a> device selection is now saved between sessions ({{bug(1248619)}}).</li>
- <li>Resources that are potentially affected by <a href="/en-US/docs/Mozilla/Firefox/Privacy/Tracking_Protection">Tracking Protection</a> are now <a href="/en-US/docs/">indicated</a> in the <a href="/en-US/docs/Tools/Network_Monitor">Network Monitor</a>. ({{bug(1333994)}})</li>
- <li>The <a href="/en-US/docs/Tools/Web_Console">Web Console</a> got improvements around entering and evaluating code:
-  <ul>
-   <li><a href="/en-US/docs/Tools/Web_Console/The_command_line_interpreter#Autocomplete">Autocomplete</a> for Console expressions is now case-insensitive ({{bug(672733)}}).</li>
-   <li>You can now step through the <a href="/en-US/docs/Tools/Web_Console/The_command_line_interpreter#Command_history">Console expression history</a> with bash-like reverse search ({{bug(1024913)}}).</li>
-   <li><a href="/en-US/docs/Tools/Web_Console/The_command_line_interpreter">Evaluated code</a> in the Console is now syntax-highlighted in both the input and output ({{bug(1463669)}}).</li>
-  </ul>
- </li>
- <li>Stepping in the <a href="/en-US/docs/Tools/Debugger">JavaScript Debugger</a> also had some improvements:
-  <ul>
-   <li>The debugger now persists <a href="/en-US/docs/Tools/Debugger/UI_Tour#Scopes">expanded variables</a> while stepping through code ({{bug(1491471)}}).</li>
-   <li><a href="/en-US/docs/Tools/Debugger/How_to/Step_through_code">Stepping out</a> of a function in the Debugger now skips the return value. ({{bug(923975)}})</li>
-  </ul>
- </li>
-</ul>
-
-<h4 id="Removals">Removals</h4>
-
-<ul>
- <li>The Developer Tools GCLI has been removed ({{bug(1429421)}}).</li>
-</ul>
-
-<h3 id="HTML">HTML</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li><a href="/en-US/docs/Web/CSS/CSS_Scrollbars">CSS Scrollbars</a> spec functionality has been enabled by default ({{bug(1492012)}}).</li>
- <li>Interaction Media Features implemented, including <code><a href="/en-US/docs/Web/CSS/@media/pointer">pointer:coarse</a></code> ({{bug(1035774)}}). For <code><a href="/en-US/docs/Web/CSS/@media/any-pointer">any-pointer</a></code> and <code><a href="/en-US/docs/Web/CSS/@media/any-hover">any-hover</a></code> implementation, see {{bug(1483111)}}.</li>
- <li>The <code><a href="/en-US/docs/Web/CSS/@media/prefers-reduced-motion">prefers-reduced-motion</a></code> media feature is now supported in Firefox for Android ({{bug(1478505)}}).</li>
- <li>CSS {{cssxref("&lt;gradient&gt;")}} values now support multi-position color stop syntax, e.g. <code>yellow 25%, yellow 50%</code> can now be written <code>yellow 25% 50%</code> ({{bug(1352643)}}).</li>
- <li>The {{cssxref("text-transform")}} property now accepts the <code>full-size-kana</code> value ({{bug(1498148)}}).</li>
- <li>Support added for {{cssxref("appearance", "-webkit-appearance")}} to alleviate associated web compat issues ({{bug(1368555)}}).</li>
- <li>Closely associated with the above update, we've also removed most of the Firefox-specific <code>-moz-appearance</code> values ({{bug(1496720)}}).</li>
- <li>{{cssxref("display")}}: <code>list-item</code> is now supported on {{htmlelement("legend")}} elements ({{bug(1486602)}}).</li>
- <li>SVG <code>path()</code>s, as usable in {{cssxref("offset-path")}}, are now animatable ({{bug(1486094)}}).</li>
- <li>If a selector chain or group includes a <code>-webkit-</code>prefixed pseudo-element, that pseudo-element no longer invalidates it (see {{bug(1424106)}} for the details, and {{bug(1486325)}} for enabling this feature).</li>
-</ul>
-
-<h4 id="Removals_2">Removals</h4>
-
-<ul>
- <li>The non-standard <a href="/en-US/docs/Mozilla/Gecko/Chrome/CSS/display-xul"><code style="white-space: nowrap;">-moz-box</code> and <code style="white-space: nowrap;">-moz-inline-box</code></a> {{CSSxRef("display")}} values have been hidden from web content ({{bug(1496961)}}).</li>
- <li>The non-standard {{CSSxRef("::-moz-tree")}} <a href="/en-US/docs/Web/CSS/Pseudo-elements" style="white-space: nowrap;">pseudo-elements</a> have been hidden from web content ({{bug(1496961)}}).</li>
- <li>The <code>layout.css.filters.enabled</code> preference has been removed; <a href="/en-US/docs/Web/CSS/Filter_Effects">CSS filters</a> can no longer be disabled ({{bug(1408841)}}).</li>
- <li>A previous change — to swap the values of the 2-value {{cssxref("overflow")}} syntax so block is specified first and inline second ({{bug(1481866)}}) — has been reverted ({{bug(1492567)}}). See <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1481866#c14">Bug 1481866 comment 14</a> for why.</li>
-</ul>
-
-<h3 id="SVG">SVG</h3>
-
-<p><em>No changes.</em></p>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<ul>
- <li>The TC39 <a href="https://github.com/tc39/proposal-well-formed-stringify">Well-formed JSON.stringify</a> proposal has been implemented, to prevent {{jsxref("JSON.stringify")}} from returning ill-formed Unicode strings ({{bug(1469021)}}).</li>
- <li>Proxied functions can now be be passed to {{jsxref("Function.prototype.toString")}}<code>.call()</code> ({{bug(1440468)}}).</li>
- <li>In the {{jsxref("WebAssembly.Global")}} constructor, if no value is specified a typed 0 value is used. This is specified by the <a href="https://webassembly.github.io/spec/js-api/#defaultvalue"><code>DefaultValue</code> algorithm</a> ({{bug(1490286)}}).</li>
-</ul>
-
-<h3 id="APIs">APIs</h3>
-
-<h4 id="DOM">DOM</h4>
-
-<ul>
- <li>A number of changes related to the {{domxref("Fullscreen_API", "Fullscreen API", "", "1")}} have been implemented:
-  <ul>
-   <li>The API has been unprefixed ({{bug(1269276)}}).</li>
-   <li>The {{domxref("Element.requestFullscreen()")}} and {{domxref("Document.exitFullscreen()")}} methods both now return a {{jsxref("Promise")}}, which is resolved when the mode change is complete ({{bug(1188256)}} and {{bug(1491212)}}).</li>
-   <li>Previously, {{domxref("fullscreenchange")}} and {{domxref("fullscreenerror")}} events were dispatched to the {{domxref("Document")}} first, then the {{domxref("Element")}}. This has been reversed so that the element gets the event first. This matches the latest specification as well as the behavior of Google Chrome ({{bug(1375319)}}).</li>
-  </ul>
- </li>
- <li>The {{domxref("WebVR_API", "WebVR API", "", "1")}} (1.1) is now re-enabled in macOS ({{bug(1476091)}}).</li>
- <li>{{domxref("Window.screenLeft")}} and {{domxref("Window.screenTop")}} have been implemented, as aliases of {{domxref("Window.screenX")}} and {{domxref("Window.screenY")}} ({{bug(1498860)}}).</li>
- <li>The {{domxref("XMLHttpRequest.getAllResponseHeaders()")}} method now returns header names all in lowercase, as per spec ({{bug(1398718)}}).</li>
- <li>The legacy <code>HTMLAllCollection</code> interface has been updated as per recent <a href="https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#htmlallcollection">spec updates</a> ({{bug(1398354)}}).</li>
- <li>{{domxref("Navigator.buildID")}} now returns a fixed timestamp as a privacy measure ({{bug(583181)}}).</li>
-</ul>
-
-<h4 id="Service_workers">Service workers</h4>
-
-<ul>
- <li>The {{domxref("ServiceWorkerContainer.startMessages()")}} method has been implemented ({{bug(1263734)}}).</li>
-</ul>
-
-<h4 id="Media_Web_Audio_and_WebRTC">Media, Web Audio, and WebRTC</h4>
-
-<ul>
- <li>The {{domxref("PannerNode.refDistance")}}, {{domxref("PannerNode.maxDistance")}}, {{domxref("PannerNode.rolloffFactor")}}, and {{domxref("PannerNode.coneOuterGain")}} properties now correctly throw exceptions when set to values outside their accepted ranges ({{bug(1487963)}}).</li>
- <li>{{domxref("RTCRtpEncodingParameters")}} settings changed via {{domxref("RTCRtpSender.setParameters()")}} used to not update if the changes were made during a call. They will now update live, without renegotiation ({{bug(1253499)}}).</li>
- <li>{{domxref("RTCIceCandidateStats.relayProtocol")}} has been implemented — this is the standardized version of {{domxref("RTCIceCandidateStats.mozLocalTransport")}}, which has now been deprecated ({{bug(1435789)}}).</li>
-</ul>
-
-<h4 id="Removals_3">Removals</h4>
-
-<ul>
- <li>The {{domxref("Window.event")}} property, added in Firefox 63 to aid with web compat issues, has been put behind a pref (<code>dom.window.event.enabled</code>) and disabled by default in release versions for now due to other issues that have been uncovered ({{bug(1493869)}}). Note that this was actually done late in the Firefox 63 release cycle, but we are mentioning it here just in case.</li>
- <li>The {{domxref("LocalMediaStream")}} interface and its <code>stop()</code> method have been removed ({{bug(1258143)}}). This method is no longer available with the deprecation of <code>LocalMediaStream</code>. See {{SectionOnPage("/en-US/docs/Web/API/MediaStreamTrack/stop", "Stopping a video stream")}} to learn how to stop an entire stream.</li>
- <li>The <code>AudioStreamTrack</code> and <code>VideoStreamTrack</code> interfaces have been removed, as both have been deprecated for some time ({{bug(1377146)}}). Their functionality has been merged into {{domxref("MediaStreamTrack")}}; tracks are now identified by the value of their {{domxref("MediaStreamTrack.kind", "kind")}} property, such as <code>audio</code> or <code>video</code>.</li>
-</ul>
-
-<h3 id="Security">Security</h3>
-
-<ul>
- <li>The Symantec CA Distrust plan has been implemented (see {{bug(1409257)}}; see also the <a href="https://groups.google.com/forum/#!topic/mozilla.dev.security.policy/FLHRT79e3XE/discussion">Mozilla’s Plan for Symantec Roots</a> discussion for more details).</li>
- <li>{{httpheader("Referrer-Policy")}} can now be used to govern resources fetched via stylesheets ({{bug(1330487)}}) — see {{SectionOnPage("/en-US/docs/Web/HTTP/Headers/Referrer-Policy", "Integration with CSS")}} for more information.</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>
-
-<h4 id="Menus">Menus</h4>
-
-<ul>
- <li>A new API, <code>browser.menus.overrideContext()</code>, can be called from the <code>contextmenu</code> DOM event to set a custom context menu in extension pages. This API allows extensions to hide all default Firefox menu items in favor of providing a custom context menu UI. This context menu can consist of multiple top-level menu items from the extension, and may optionally include tab or bookmark context menu items from other extensions. See <a href="https://blog.mozilla.org/addons/2018/11/08/extensions-in-firefox-64/#cm">this blog post</a> for more details.
-
-  <ul>
-   <li><code>browser.menus.overrideContext()</code> was implemented in ({{bug(1280347)}}).</li>
-   <li>The <code>showDefaults: false</code> option, which can be used to hide the default context menu options, was implemented in ({{bug(1367160)}}).</li>
-  </ul>
- </li>
- <li>You can now restrict where context menus can appear in an add-on using the new <code>viewTypes</code> property in {{WebExtAPIRef("menus.create()")}} and {{WebExtAPIRef("menus.update()")}} ({{bug(1416839)}}).</li>
- <li>{{WebExtAPIRef("menus.update()")}} can now be used to update the icon of an existing menu item ({{bug(1414566)}}).</li>
- <li>Extensions can now detect which mouse button was used when a menu item was clicked — this can be found using the new <code>button</code> property of {{WebExtAPIRef("menus.OnClickData")}} ({{bug(1469148)}}).</li>
-</ul>
-
-<h4 id="Windows">Windows</h4>
-
-<ul>
- <li>The {{WebExtAPIRef("windows.create()")}} method now has a new option available — <code>cookieStoreId</code> — which specifies the <code>CookieStoreId</code> to use for all tabs that were created when the window is opened ({{bug(1393570)}}).</li>
-</ul>
-
-<h4 id="Privacy">Privacy</h4>
-
-<ul>
- <li>The {{WebExtAPIRef("privacy.websites")}} <code>cookieConfig</code> property is an object that can accept a <code>behavior</code> property — this property can now take a new value, <code>reject_trackers</code>, which instructs the extension to reject tracking cookies ({{bug(1493057)}}).</li>
-</ul>
-
-<h4 id="devtools.panels_API">devtools.panels API</h4>
-
-<ul>
- <li>The <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/devtools.panels/elements">devtools.panels.elements</a></code> <code>Sidebar.setPage()</code> method is now supported ({{bug(1398734)}}).</li>
-</ul>
-
-<h3 id="Manifest_changes">Manifest changes</h3>
-
-<ul>
- <li>The new <code>pinned</code> property of the <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/page_action">page_action</a></code> manifest key enables extensions to control whether their page actions should be pinned to the location bar on install or not ({{bug(1494135)}}).</li>
- <li>In native manifests on Windows, the 32-bit registry view (<a class="external external-icon" href="https://en.wikipedia.org/wiki/WoW64#Registry_and_file_system" rel="noopener">Wow6432Node)</a> will be checked first for registry keys, followed by the "native" registry view; you should use whichever is appropriate for your application ({{bug(1494709)}}).</li>
- <li>The <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/chrome_settings_overrides">chrome_settings_overrides</a></code> field's <code>search_provider</code> object can now include new properties — <code>suggest_url</code> and <code>suggest_url_post_params</code> ({{bug(1486819)}}), and <code>search_url_post_params</code>.</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://www.fxsitecompat.com/en-CA/versions/64/">Site compatibility for Firefox 64</a></li>
-</ul>
-
-<h2 id="Older_versions">Older versions</h2>
-
-<p>{{Firefox_for_developers(64)}}</p>
diff --git a/files/it/mozilla/firefox/releases/66/index.html b/files/it/mozilla/firefox/releases/66/index.html
deleted file mode 100644
index 85441c5ce4..0000000000
--- a/files/it/mozilla/firefox/releases/66/index.html
+++ /dev/null
@@ -1,156 +0,0 @@
----
-title: Firefox 66 for developers
-slug: Mozilla/Firefox/Releases/66
-translation_of: Mozilla/Firefox/Releases/66
----
-<div>{{FirefoxSidebar}}</div>
-
-<p class="summary"><span class="tlid-translation translation" lang="it"><span title="">Questo articolo fornisce informazioni sulle modifiche in Firefox 66 che interesseranno gli sviluppatori.</span></span> <span class="tlid-translation translation" lang="it"><span title="">Firefox 66 è l'attuale</span></span> <a href="https://www.mozilla.org/en-US/firefox/channel/desktop/#beta" rel="noopener">versione Beta di Firefox</a>, <span class="tlid-translation translation" lang="it"><span title=""> sarà disponibile</span></span> <a href="https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates" rel="noopener">19 Marzo del 2019</a>.</p>
-
-<h2 id="Modifiche_per_gli_sviluppatori_web"><span class="tlid-translation translation" lang="it"><span title="">Modifiche per gli sviluppatori web</span></span></h2>
-
-<h3 id="Strumenti_di_sviluppo"><span class="tlid-translation translation" lang="it"><span title="">Strumenti di sviluppo</span></span></h3>
-
-<ul>
- <li>JavaScript getters can now be executed from the auto-completion popup in the <a href="/en-US/docs/Tools/Web_Console">Web Console</a> ({{bug(1499289)}}).</li>
- <li>The Window methods {{domxref("Window.alert()", "alert()")}}, {{domxref("Window.prompt()","prompt()")}}, and {{domxref("Window.confirm()","confirm()")}} now work again in <a href="/en-US/docs/Tools/Responsive_Design_Mode">Responsive Design Mode</a>, after a period of being broken ({{bug(1273997)}}).</li>
-</ul>
-
-<h3 id="HTML">HTML</h3>
-
-<ul>
- <li>UTF-8-encoded HTML (and plain text) files loaded from <code>file:</code> URLs are now supported without <code>&lt;meta charset="utf-8"&gt;</code> or the UTF-8 BOM, making it easier to work on such files locally before uploading them to a server. You still need to make sure that the server sends <code>charset=utf-8</code> in the <code>Content-Type</code> HTTP header for such files, otherwise the detection mechanism used for local files would break incremental loading in the network case ({{bug(1071816)}}).</li>
-</ul>
-
-<h4 id="Removals">Removals</h4>
-
-<ul>
- <li>The <code>x-moz-errormessage</code> attribute has been removed from the {{HTMLElement("input")}} element ({{bug(1513890)}}). You should use  {{domxref("Constraint_validation", "Constraint validation features", "", "1")}} to implement custom validation messages instead.</li>
-</ul>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li><a href="https://drafts.csswg.org/css-scroll-anchoring/">Scroll anchoring</a> has been implemented in Firefox Desktop (but not mobile yet), which includes the {{cssxref("overflow-anchor")}} property ({{bug(1305957)}}).</li>
- <li>We've implemented the case-sensitive <a href="/en-US/docs/Web/CSS/Attribute_selectors">attribute selector</a> modifier, <code>s</code> ({{Bug(1512386)}}).</li>
- <li>Several <a href="/en-US/docs/Web/CSS/CSS_Logical_Properties">logical property</a> shorthands have landed, along with the flow-relative border radius properties:
-  <ul>
-   <li>{{cssxref("padding-block")}} and {{cssxref("padding-inline")}} ({{bug(1519847)}}).</li>
-   <li>{{cssxref("margin-block")}} and {{cssxref("margin-inline")}} ({{bug(1519944)}}).</li>
-   <li>{{cssxref("inset")}}, {{cssxref("inset-block")}}, and {{cssxref("inset-inline")}} ({{bug(1520229)}}).</li>
-   <li>{{cssxref("border-block-color")}}, {{cssxref("border-block-style")}}, {{cssxref("border-block-width")}}, {{cssxref("border-inline-color")}}, {{cssxref("border-inline-style")}}, and {{cssxref("border-inline-width")}} ({{bug(1520236)}}).</li>
-   <li>{{cssxref("border-block")}} and {{cssxref("border-inline")}} ({{bug(1520396)}}).</li>
-   <li>{{cssxref("border-start-start-radius")}}, {{cssxref("border-start-end-radius")}}, {{cssxref("border-end-start-radius")}}, and {{cssxref("border-end-end-radius")}} ({{bug(1520684)}}).</li>
-  </ul>
- </li>
- <li>We implemented the {{cssxref("@media/overflow-inline", "overflow-inline")}} and {{cssxref("@media/overflow-block", "overflow-block")}} media queries ({{Bug(1422235)}}).</li>
- <li>{{cssxref("grid-template-columns")}} and {{cssxref("grid-template-rows")}} are now animatable, as per the rules set out in their specs ({{bug(1348519)}}).</li>
- <li>We now support {{cssxref("calc")}} with percentages for table cells and column widths ({{bug(957915)}}).</li>
- <li>The <code>min-content</code> and <code>max-content</code> keywords are now available unprefixed ({{bug(1322780)}}). These can be set on:
-  <ul>
-   <li>{{cssxref("width")}}</li>
-   <li>{{cssxref("height")}}</li>
-   <li>{{cssxref("flex-basis")}}</li>
-   <li>{{cssxref("min-width")}}</li>
-   <li>{{cssxref("max-width")}}</li>
-   <li>{{cssxref("min-height")}}</li>
-   <li>{{cssxref("max-height")}}</li>
-   <li>{{cssxref("min-block-size")}}</li>
-   <li>{{cssxref("min-inline-size")}}</li>
-   <li>{{cssxref("max-block-size")}}</li>
-   <li>{{cssxref("max-inline-size")}}</li>
-   <li>{{cssxref("block-size")}}</li>
-   <li>{{cssxref("inline-size")}}</li>
-  </ul>
- </li>
-</ul>
-
-<h3 id="SVG">SVG</h3>
-
-<p><em>No additions.</em></p>
-
-<h4 id="Removals_2">Removals</h4>
-
-<ul>
- <li>We removed support for the <code><a href="/en-US/docs/XML_introduction/xml:base">xml:base</a></code> attribute ({{Bug(903372)}}).</li>
-</ul>
-
-<h3 id="JavaScript">JavaScript</h3>
-
-<p>No changes.</p>
-
-<h3 id="APIs">APIs</h3>
-
-<h4 id="New_APIschanges">New APIs/changes</h4>
-
-<ul>
- <li>Autoplaying audio will be blocked by default soon after 66 becomes the release version of Firefox ({{bug(1487844)}}, see {{bug(1535667)}} for rollout details). The feature will be rolled out gradually to users until everyone has it.</li>
-</ul>
-
-<h4 id="DOM">DOM</h4>
-
-<ul>
- <li>The {{domxref("HTMLSlotElement.assignedElements()")}} method has been implemented ({{bug(1425685)}}).</li>
- <li>The {{domxref("TextEncoder.encodeInto()")}} method has been implemented ({{bug(1514664)}}).</li>
-</ul>
-
-<h4 id="DOM_events">DOM events</h4>
-
-<ul>
- <li>The {{domxref("InputEvent.inputType")}} property has been implemented ({{bug(1447239)}}).</li>
- <li>The {{domxref("Window.event")}} and {{domxref("Event.returnValue")}} properties — originally proprietary IE features, then also supported across other browsers for compatibility purposes — have been re-introduced in Firefox 66, after first being added in versions 63 and 64 respectively but then removed again due to compatibility issues. </li>
- <li>From 66 onwards, when the {{domxref("KeyboardEvent.keyCode")}} property of the {{event("keypress")}} event object is 0, the value will be the same as {{domxref("KeyboardEvent.charCode")}}. Conversely, when <code>charCode</code> is 0, it will be the same as <code>keyCode</code>. This mirroring behavior matches other browsers and is expected to solve most associated compatibility issues, however user agent sniffing might cause further issues in some JavaScript libraries. Note that in spec terms, we've switched from the <em>split model</em> to the <em>conflated model</em> (see <a href="https://w3c.github.io/uievents/#determine-keypress-keyCode">How to determine keyCode for keypress events</a> in the UI Event spec).</li>
-</ul>
-
-<h4 id="Media_Web_Audio_and_WebRTC">Media, Web Audio, and WebRTC</h4>
-
-<ul>
- <li>The {{domxref("MediaDevices")}} method {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}}, available as <code>navigator.mediaDevices.getDisplayMedia()</code>, has been added and synchronized with the specification. This method lets you capture a screen or part of a screen as a {{domxref("MediaStream")}} for manipulation or sharing ({{bug(1321221)}}).</li>
- <li>As a step toward eventually deprecating the Firefox-specific {{domxref("MediaDevices.getUserMedia", "getUserMedia()")}}-based method for capturing screen and window contents, the non-standard <code>mediaSource</code> constraint now treats the values <code>screen</code> and <code>window</code> identically. Both now present a list of both screens and windows for the user to choose from ({{bug(1474376)}}).</li>
- <li>{{domxref("RTCRtpStreamStats.qpSum", "qpSum")}} has been added to local outbound {{domxref("RTCRTPStreamStats")}} objects. This measures the total of the Quantization Parameter values for every frame sent or received on the video track. The higher this number, the more compressed the stream probably is ({{bug(1347070)}}).</li>
- <li>In a step along the road toward implementing support for Feature Policy in a future Firefox update, {{domxref("MediaDevices.getUserMedia", "getUserMedia()")}} can no longer be used in situations in which there is no proper origin for the content, such as when called from a sandboxed {{HTMLElement("iframe")}} or from a <code>data</code> URL entered into the address bar by the user. For more specifics and details, see {{SectionOnPage("/en-US/docs/Web/API/MediaDevices/getUserMedia", "Security")}} ({{bug(1371741)}}).</li>
-</ul>
-
-<h4 id="Removals_3">Removals</h4>
-
-<ul>
- <li>The legacy WebRTC {{domxref("PeerConnection.getStats()")}} method has been removed, along with associated types ({{bug(1328194)}}).</li>
-</ul>
-
-<h3 id="Networking">Networking</h3>
-
-<ul>
- <li>The default value of the {{httpheader("Accept")}} header has been changed to <code>*/*</code> ({{bug(1417463)}}).</li>
-</ul>
-
-<h3 id="Security">Security</h3>
-
-<p><em>No changes.</em></p>
-
-<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>
-
-<h4 id="Menus">Menus</h4>
-
-<ul>
- <li>Extension menu items of the "bookmark" {{WebExtAPIRef("menus.ContextType", "type")}} will also appear in the Bookmarks sidebar (<kbd>Ctrl</kbd> + <kbd>B</kbd>) and Library window (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>B</kbd>) ({{bug(1419195)}}).</li>
-</ul>
-
-<h3 id="Manifest_changes">Manifest changes</h3>
-
-<p><em>No changes.</em></p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://www.fxsitecompat.com/en-CA/versions/66/">Site compatibility for Firefox 66</a></li>
-</ul>
-
-<h2 id="Older_versions">Older versions</h2>
-
-<p>{{Firefox_for_developers(65)}}</p>
diff --git a/files/it/mozilla/firefox/releases/index.html b/files/it/mozilla/firefox/releases/index.html
deleted file mode 100644
index a7185bc5e5..0000000000
--- a/files/it/mozilla/firefox/releases/index.html
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Firefox developer note di rilascio
-slug: Mozilla/Firefox/Releases
-tags:
-  - Firefox
-translation_of: Mozilla/Firefox/Releases
----
-<div>{{FirefoxSidebar}}</div><p>Questa pagina fornisce i link "Firefox X per sviluppatori" agli articoli di ogni rilascio Firefox. Queste note ci mostrano quali funzionalità saranno aggiunte e quali bug verranno eliminati in ogni versione di Firefox.</p>
-
-<div class="multiColumnList">{{ListSubpages("",1,0,1)}}</div>
diff --git a/files/it/mozilla/index.html b/files/it/mozilla/index.html
deleted file mode 100644
index e24ed8a774..0000000000
--- a/files/it/mozilla/index.html
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Mozilla
-slug: Mozilla
-tags:
-  - NeedsTranslation
-  - TopicStub
-translation_of: Mozilla
----
-<div>
-  {{draft}}</div>
-<p>This will soon be an awesome landing page for Mozilla internals. For now, it's not.</p>
-<div>
-  {{ListSubpages}}</div>