initial commit

3 files changed, 291 insertions, 0 deletions

diff --git a/files/pt-pt/plugins/ativacao_de_flash_colon__comparacao_de_navegador/index.html b/files/pt-pt/plugins/ativacao_de_flash_colon__comparacao_de_navegador/index.html
new file mode 100644
index 0000000000..e804f3a3f9
--- /dev/null
+++ b/files/pt-pt/plugins/ativacao_de_flash_colon__comparacao_de_navegador/index.html
@@ -0,0 +1,146 @@
+---
+title: 'Ativação de Flash: Comparação de Navegador'
+slug: 'Plugins/Ativacao_de_Flash:_comparacao_de_navegador'
+tags:
+  - Como
+  - Flash
+  - Principiante
+  - compatibilidade de navegador
+translation_of: 'Plugins/Flash_Activation:_Browser_Comparison'
+---
+<p>Cada um dos principais navegadores implementou uma funcionalidade onde o conteúdo do Adobe Flash não é executado por predefinição, mas cada um dos navegadores implementou essa funcionalidade e a interface do utilizador de maneiras ligeiramente diferentes. Este guia irá ajudar a descrever as semelhanças e as diferenças entre os navegadores, para que os programadores da Web possam oferecer a melhor experiência ao utilizador. Está disponível outro guia para assistir os autores do site da Web em <a href="/pt-PT/docs/Plugins/Flash_para_HTML5">migrating away from Flash</a>.</p>
+
+<p>In each browser, the decision to enable Flash is made by users on a per-site basis. When a site attempts to use Flash, the browser will prompt the user in some way and give the user an opportunity to enable Flash for that site. Flash-blocking extensions are no longer necessary because this functionality is now built into the browser.</p>
+
+<table class="fullwidth-table">
+ <thead>
+  <tr>
+   <td> </td>
+   <th scope="col">Mozilla Firefox</th>
+   <th scope="col">Google Chrome</th>
+   <th scope="col">Microsoft Edge</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <th scope="row">Setting Name</th>
+   <td>Ask to activate</td>
+   <td>HTML5 by default</td>
+   <td>Click-to-run</td>
+  </tr>
+  <tr>
+   <th scope="row">'application/x-shockwave-flash' in navigator.mimeTypes by default when Flash is inactive</th>
+   <td>yes</td>
+   <td>no</td>
+   <td>no</td>
+  </tr>
+  <tr>
+   <th scope="row">'application/x-shockwave-flash' in navigator.mimeTypes when user enables Flash</th>
+   <td>yes</td>
+   <td>yes</td>
+   <td>yes</td>
+  </tr>
+  <tr>
+   <th scope="row">&lt;object&gt; with fallback content triggers UI</th>
+   <td>yes, with exceptions</td>
+   <td>no</td>
+   <td>yes</td>
+  </tr>
+  <tr>
+   <th scope="row">small/hidden Flash triggers additional UI</th>
+   <td>yes</td>
+   <td>no</td>
+   <td>no</td>
+  </tr>
+  <tr>
+   <th scope="row">Enabling Flash automatically reloads the page</th>
+   <td>no</td>
+   <td>yes</td>
+   <td>yes</td>
+  </tr>
+  <tr>
+   <th scope="row">Other features related to Flash</th>
+   <td><a href="/en-US/docs/Plugins/Blocking_By_Domain">Domain Blocking</a></td>
+   <td><a href="https://sites.google.com/a/chromium.org/dev/flash-roadmap#TOC-Plugin-Power-Savings-Mode-Shipped:-Chrome-42---Sept-2015-">Plugin Power Saver</a></td>
+   <td><a href="https://blogs.windows.com/msedgedev/2016/04/07/putting-users-in-control-of-flash/#fLGW6bYgr4BpSHIr.97">Peripheral Content Pause</a></td>
+  </tr>
+ </tbody>
+</table>
+
+<p>Each of the browser vendors has a roadmap about the future of Flash and changes to the user experience. The <a href="/en-US/docs/Plugins/Roadmap">Firefox Flash roadmap</a> includes links to roadmaps and posts from other vendors.</p>
+
+<h2 id="Caomparação_da_IU">Caomparação da IU</h2>
+
+<h3 id="Mozilla_Firefox">Mozilla Firefox</h3>
+
+<p>In-page UI is displayed when the site attempts to use Flash. An icon also appears on the left side of the location bar. The user can click on the Flash object or the location bar icon to activate Flash:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15127/Firefox-flash-inpage.png" style="height: 389px; width: 674px;"></p>
+
+<p>Users have the choice to allow Flash just for the current session, or to remember their choice:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15131/Firefox-notification.png" style="height: 199px; width: 426px;"></p>
+
+<h3 id="Google_Chrome">Google Chrome</h3>
+
+<p>In-page UI is displayed when the site attempts to use Flash without fallback content:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15141/Chrome-flash-inpage.png" style="height: 412px; width: 635px;"></p>
+
+<p>A user can click the plugin element to show a prompt for allowing Flash:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15161/Chrome-flash-prompt.png" style="height: 182px; width: 516px;"></p>
+
+<p>If the site provides fallback content for an object element, Chrome will display that content and will not prompt the user to enable Flash. If a Flash element is not visible to the user, the user will not get a visible prompt.</p>
+
+<p>A user can click the information icon on the left side of the location bar on any site to open the site information and allow Flash on that site:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15145/Chrome-info-icon.png" style="height: 544px; width: 399px;"></p>
+
+<h3 id="Microsoft_Edge">Microsoft Edge</h3>
+
+<p>In-page UI is displayed when the site attempts to use Flash. An icon also appears on the right side of the location bar. The user can click the Flash object to show activation options:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15135/Edge-flash-inpage.png" style="height: 227px; width: 611px;"></p>
+
+<p>Users have the choice to allow Flash just for the current session, or to remember their choice:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/15139/Edge-flash-inpage.png" style="height: 173px; width: 453px;"></p>
+
+<h2 id="Dicas_de_Elaboração_do_Site">Dicas de Elaboração do Site</h2>
+
+<p>If a Flash element is very small, hidden, or covered by other content, users will probably not notice that Flash is required and will become confused. Even if the plugin element will eventually be hidden, pages should create the plugin element so that it's visible on the page, and should resize or hide it only after the user has activated the plugin. This can be done by calling a JavaScript function when the plugin is activated:</p>
+
+<pre class="brush: js line-numbers  language-js"><code class="language-js"><span class="keyword token">function</span> <span class="function token">pluginCreated</span><span class="punctuation token">(</span><span class="punctuation token">)</span> <span class="punctuation token">{</span>
+  <span class="comment token">// We don't need to see the plugin, so hide it by resizing</span>
+  <span class="keyword token">var</span> plugin <span class="operator token">=</span> document<span class="punctuation token">.</span><span class="function token">getElementById</span><span class="punctuation token">(</span><span class="string token">'myPlugin'</span><span class="punctuation token">)</span><span class="punctuation token">;</span>
+  plugin<span class="punctuation token">.</span>height <span class="operator token">=</span> <span class="number token">0</span><span class="punctuation token">;</span>
+  plugin<span class="punctuation token">.</span>width <span class="operator token">=</span> <span class="number token">0</span><span class="punctuation token">;</span>
+  plugin<span class="punctuation token">.</span><span class="function token">callPluginMethod</span><span class="punctuation token">(</span><span class="punctuation token">)</span><span class="punctuation token">;</span>
+<span class="punctuation token">}</span></code></pre>
+
+<p>The HTML, by default, specifies the Flash object to be a size that makes it visible, like this:</p>
+
+<pre class="brush: html line-numbers  language-html"><code class="language-html"><span class="comment token">&lt;!-- Give the plugin an initial size so it is visible --&gt;</span>
+<span class="tag token"><span class="tag token"><span class="punctuation token">&lt;</span>object</span> <span class="attr-name token">type</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>application/x-shockwave-flash<span class="punctuation token">"</span></span> <span class="attr-name token">data</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>myapp.swf<span class="punctuation token">"</span></span>
+      <span class="attr-name token">id</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>myPlugin<span class="punctuation token">"</span></span> <span class="attr-name token">width</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>300<span class="punctuation token">"</span></span> <span class="attr-name token">height</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>300<span class="punctuation token">"</span></span><span class="punctuation token">&gt;</span></span>
+  <span class="tag token"><span class="tag token"><span class="punctuation token">&lt;</span>param</span> <span class="attr-name token">name</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>callback<span class="punctuation token">"</span></span> <span class="attr-name token">value</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>pluginCreated()<span class="punctuation token">"</span></span><span class="punctuation token">&gt;</span></span>
+<span class="tag token"><span class="tag token"><span class="punctuation token">&lt;/</span>object</span><span class="punctuation token">&gt;</span></span></code></pre>
+
+<p>The <code>callback</code> parameter defined in the HTML can be called in Flash using its <code>flash.external.ExternalInterface</code> API.</p>
+
+<h3 id="Utilizar_um_callback_de_script_para_determinar_quando_um_plug-in_é_ativado">Utilizar um <em>callback</em> de <em>script</em> para determinar quando um plug-in é ativado</h3>
+
+<p>Similarly, a site's script shouldn't attempt to script a plugin immediately upon creation. Instead, the plugin object should call into a JavaScript function upon creation. That function can then issue the call into the plugin, knowing that everything is set up and ready to go.</p>
+
+<p>First, set your up your HTML with a callback that calls the JavaScript function <code>pluginCreated()</code>, like this:</p>
+
+<pre class="brush: html line-numbers  language-html"><code class="language-html"><span class="tag token"><span class="tag token"><span class="punctuation token">&lt;</span>object</span> <span class="attr-name token">type</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>application/x-my-plugin<span class="punctuation token">"</span></span> <span class="attr-name token">data</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>somedata.mytype<span class="punctuation token">"</span></span> <span class="attr-name token">id</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>myPlugin<span class="punctuation token">"</span></span><span class="punctuation token">&gt;</span></span>
+  <span class="tag token"><span class="tag token"><span class="punctuation token">&lt;</span>param</span> <span class="attr-name token">name</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>callback<span class="punctuation token">"</span></span> <span class="attr-name token">value</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>pluginCreated()<span class="punctuation token">"</span></span><span class="punctuation token">&gt;</span></span>
+<span class="tag token"><span class="tag token"><span class="punctuation token">&lt;/</span>object</span><span class="punctuation token">&gt;</span></span></code></pre>
+
+<p>The <code>pluginCreated()</code> function is then responsible for the setup of your script and any calls back into the plugin that you need to make:</p>
+
+<pre class="brush: js line-numbers  language-js"><code class="language-js"><span class="keyword token">function</span> <span class="function token">pluginCreated</span><span class="punctuation token">(</span><span class="punctuation token">)</span> <span class="punctuation token">{</span>
+  document<span class="punctuation token">.</span><span class="function token">getElementById</span><span class="punctuation token">(</span><span class="string token">'myPlugin'</span><span class="punctuation token">)</span><span class="punctuation token">.</span><span class="function token">callPluginMethod</span><span class="punctuation token">(</span><span class="punctuation token">)</span><span class="punctuation token">;</span>
+<span class="punctuation token">}</span></code></pre>
diff --git a/files/pt-pt/plugins/flash_para_html5/index.html b/files/pt-pt/plugins/flash_para_html5/index.html
new file mode 100644
index 0000000000..b17f365038
--- /dev/null
+++ b/files/pt-pt/plugins/flash_para_html5/index.html
@@ -0,0 +1,82 @@
+---
+title: Guia de migração de Flash para HTML5
+slug: Plugins/Flash_para_HTML5
+tags:
+  - Complementos
+  - Flash
+  - HTML5
+  - Jogos
+  - Plug-ins
+  - Publicidade
+  - Sockets
+  - Video
+  - anuncios
+  - Área de transferência
+translation_of: Plugins/Flash_to_HTML5
+---
+<p class="summary">Este conjunto de artigos fornece informação sobre como migrar o conteúdo e a funcionalidade do Flash existente para HTML e JavaScript.</p>
+
+<h2 id="Background">Background</h2>
+
+<p>Flash became very popular in the late 1990s to early 2000s because it provided an effective way to create rich content on the web — such as animations, games, and video players. However, it has a number of issues; the Flash Player causes security and performance problems, and leads to bloated pages. In addition, the modern web platform has feature parity with Flash, so you no longer need to rely on plugins to implement rich content.</p>
+
+<p>Browsers are working together to move carefully towards a plugin-free web (see our <a href="/en-US/docs/Plugins/Roadmap">Plugin Roadmap</a>), so developers should start migrating their Flash-based functionality to open web technologies as soon as possible.</p>
+
+<div class="row topicpage-table">
+<div class="section">
+<h2 id="Vídeo">Vídeo</h2>
+
+<p>All you need to know to move your video requirements over from Flash to HTML5 (see the <a href="/en-US/docs/Plugins/Flash_to_HTML5/Video">Flash video to HTML5 video</a> landing page also).</p>
+
+<h3 dir="ltr" id="Planeamento">Planeamento</h3>
+
+<dl>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Planning">Planning your transition from Flash video to HTML5 video</a></dt>
+ <dd>Transitioning from Flash to HTML5 can take several months and may require new skills and software. This guide shows you how to plan for that transition, and contains two main parts, <a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Planning#Auditing_What_You_Have">Content audit</a> and <a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Planning#Decision_Points">Decision points</a>.</dd>
+</dl>
+
+<h3 id="Processo">Processo</h3>
+
+<dl>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Converting_File_Formats">File format conversion</a></dt>
+ <dd>Once you've planned out what you want to do, the first step is to convert your video files into formats compatible with HTML embedding.</dd>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/DRM_and_authentication">DRM and authentication</a></dt>
+ <dd>If your media requires authentication/rights to access, you'll need to work out how to hook up the necessary DRM and authentication mechanisms.</dd>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Advertising">Video advertising</a></dt>
+ <dd>You may also want to incorporate advertising into your video delivery system, via an ad network.</dd>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Distribution">Distribution</a></dt>
+ <dd>A CDN is a popular choice for effective delivery of media content.</dd>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Players">Video and audio players</a></dt>
+ <dd>There are a number of ways to play back web media depending on the scale of your needs and whether you need ad integration and digital rights management.</dd>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Video/Subtitles_captions">Subtitles and captions</a></dt>
+ <dd>Just as audio and video may need transcoding for the web, subtitles and captions may also need to be converted and made available.</dd>
+</dl>
+</div>
+
+<div class="section">
+<h2 id="Outros_tópicos">Outros tópicos</h2>
+
+<p>Other common Flash use cases that should now be migrated to HTML5.</p>
+
+<dl>
+ <dt><a href="/en-US/docs/Games">Open web games</a></dt>
+ <dd>Flash games used to be very common, but the open web is now a viable platform for creating and distibuting games.</dd>
+ <dt><a href="/en-US/docs/Web/API/WebSockets_API">Real-time apps with WebSockets</a></dt>
+ <dd>Flash TCP sockets have been commonly used to create real-time multiuser apps such as chat apps, but they can be replaced with WebSockets.</dd>
+ <dt><a href="/en-US/docs/Plugins/Flash_to_HTML5/Clipboard">Clipboard access</a></dt>
+ <dd>Flash's clipboard API used to be the only available means for creating advanced clipboard functionality, but this is now available in web standards.</dd>
+ <dt><a href="/en-US/docs/Web/API/Intersection_Observer_API">Content and advertising visibility with Intersection Observer</a></dt>
+ <dd>Flash used to be a simple but slow way to detect content and advertising visibility on the page. The web platfom now has the Intersection Observer API to do this better and faster.</dd>
+ <dt><a href="/en-US/docs/Learn/CSS/CSS_layout">Flexible user interfaces with CSS</a></dt>
+ <dd>Adobe Flex used to provide a way to effectively create flexible user interfaces on the web, but the open web platform now boasts powerful CSS layout systems like Grid and Flexbox to close the gap.</dd>
+ <dt><a href="/en-US/docs/Web/API/WebRTC_API">Camera/Microphone access with WebRTC</a></dt>
+ <dd>Developers used to rely exclusively on Flash for accessing the user's camera and microphone, but this can now be achieved with WebRTC and related technologies. See also <a href="/en-US/docs/Web/API/Media_Streams_API">Media Capture and Streams API</a> and <a href="/en-US/docs/Web/API/MediaDevices/getUserMedia">getUserMedia</a> for useful starting points.</dd>
+ <dt><a href="https://developer.mozilla.org/en-US/docs/Web/API/File">File selection using the File API</a></dt>
+ <dd>The web platform has functionality accessing files on the user's file system, e.g. for upload or display. See <a href="/en-US/docs/Web/HTML/Element/input/file">&lt;input type="file"&gt;</a> and <a href="/en-US/docs/Using_files_from_web_applications">Using files from web applications</a> for useful resources.</dd>
+</dl>
+</div>
+</div>
+
+<h2 id="Obter_ajuda">Obter ajuda</h2>
+
+<p>If you find that our migration guide leaves you with any questions unanswered, please don't hesitate to visit our <a href="https://discourse.mozilla-community.org/c/mdn">MDN Discourse page</a> and ask them there.</p>
diff --git a/files/pt-pt/plugins/index.html b/files/pt-pt/plugins/index.html
new file mode 100644
index 0000000000..361926e555
--- /dev/null
+++ b/files/pt-pt/plugins/index.html
@@ -0,0 +1,63 @@
+---
+title: Plugins
+slug: Plugins
+tags:
+  - Plugins
+  - Todas_as_Categorias
+translation_of: Archive/Plugins
+---
+<div>
+<p><strong>Plugins</strong> (ou plug-ins) no contexto de aplicações baseadas no Mozilla são componentes binários que, quando registrados com uma aplicação, podem mostrar conteúdo que a aplicação por si mesma não pode exibir nativamente. Por exemplo, o plugin Adobe Reader permite ao usuário abrir arquivos PDF diretamente dentro do navegador, e os plugins Quicktime e Real Player são usados para exibir formatos especiais de vídeo em uma página web.</p>
+
+<p>Plugins podem ser úteis quando se está construindo uma aplicação usando a estrutura Mozilla. Por exemplo {{ interwiki('wikipedia', 'ActiveState_Komodo', 'ActiveState Komodo') }} usa plugins para encaixar o {{ interwiki('wikipedia', 'Scintilla_(editing_component)', 'editor Scintilla') }} em sua interface de usuário XUL.</p>
+
+<p>Plugins são escritos usando <strong>NPAPI</strong>, a API multi-navegadores para plugins. O código principal da documentação para NPAPI é a <a href="/pt-PT/docs/Gecko_Plugin_API_Reference" title="Gecko_Plugin_API_Reference">Gecko Plugin API Reference</a>. Para fazer seu plugin <em>scriptable</em> para páginas web, use <a href="/pt-PT/docs/Gecko_Plugin_API_Reference/Scripting_plugins" title="Gecko_Plugin_API_Reference/Scripting_plugins">npruntime</a>. O antigo <a href="/pt-PT/docs/XPCOM" title="XPCOM">XPCOM</a>- e <a href="/pt-PT/docs/LiveConnect" title="LiveConnect">LiveConnect</a>- APIs baseadas para plugins não devem ser usadas. As tecnologias continuam a ser utilizadas, só não para plugins.</p>
+
+<p>Você pode usar <a href="/pt-PT/docs/SVG" title="SVG">SVG</a> ou <a href="/pt-PT/docs/HTML/Canvas" title="HTML/Canvas">canvas</a> para simples tarefas de direção de <em>scripts</em> gráficos e animação.</p>
+
+<p>Plugins são diferentes de <a href="/pt-PT/docs/Extensões" title="Extensões">extensões</a>, que modificam ou melhoram a funcionalidade do próprio navegador. Plugins também são diferentes de <a href="/pt-PT/docs/Creating_OpenSearch_plugins_for_Firefox" title="Creating_OpenSearch_plugins_for_Firefox">plugins de busca</a>, que plugam adicionais motores de busca na barra de pesquisa.</p>
+</div>
+
+<table class="topicpage-table">
+ <tbody>
+  <tr>
+   <td>
+    <h2 class="Documentation" id="Documenta.C3.A7.C3.A3o" name="Documenta.C3.A7.C3.A3o">Documentação</h2>
+
+    <dl>
+     <dt><a href="/pt-PT/docs/Using_the_Right_Markup_to_Invoke_Plugins" title="Using_the_Right_Markup_to_Invoke_Plugins">Using the Right Markup to Invoke Plugins</a></dt>
+     <dd>Este artigo descreve como chamar um plugin com o uso correto do HTML. Ele discute o elemento objeto e o elemento embutido também com detalhes de como usar o mais apto HTML para chamar Java numa página web .</dd>
+     <dt><a href="/pt-PT/docs/Using_XPInstall_to_Install_Plugins" title="Using_XPInstall_to_Install_Plugins">Usando o XPInstall para instalar Plugins</a></dt>
+     <dd><a href="/pt-PT/docs/XPInstall" title="XPInstall">XPInstall</a> é um instalador baseado em tecnologia JavaScript que funciona em todas as plataformas que <a class="external" href="http://mozilla.org">Mozilla</a> e navegadores Netscape baseados no Mozilla (como o Netscape 7) usam. Pode ser um caminho para garantir uma bela experiência de obter plugins sem forçar o usuário a sair do navegador para usar um instalador binário (o clássico setup.exe do Windows) ou obrigando-o a reiniciar o navegador.</dd>
+     <dt><a class="external" href="http://developer.apple.com/internet/webcontent/detectplugins.html">Detectando Plugins</a></dt>
+     <dd>"Desde que tenha horas certas, quando faz sentido usar um plugin, surge a questão de como tratar os que não tenham o plugin necessário instalado.."</dd>
+    </dl>
+
+    <p><span class="alllinks"><a href="/pt-PT/docs/tag/Plugins" title="tag/Plugins">Veja todos...</a></span></p>
+   </td>
+   <td>
+    <h2 class="Community" id="Comunidade" name="Comunidade">Comunidade</h2>
+
+    <ul>
+     <li><a href="/pt-PT/docs/Plugins/Comunidade" title="Plugins/Comunidade">Outros links para comunidades...</a></li>
+    </ul>
+
+    <h2 class="Tools" id="Ferramentas" name="Ferramentas">Ferramentas</h2>
+
+    <ul>
+     <li><a href="/pt-PT/docs/Referência_da_API_do_Plugin_Gecko" title="Referência_da_API_do_Plugin_Gecko">Referência da API do Plugin Gecko</a></li>
+     <li><a href="/pt-PT/docs/Usar_o_XPInstall_para_instalar_Plugins" title="Usar_o_XPInstall_para_instalar_Plugins">Usar o XPInstall para instalar Plugins</a></li>
+     <li><a href="/pt-PT/docs/Scripting_Plugins/Macromedia_Flash" title="Scripting_Plugins/Macromedia_Flash">Scripting Plugins: Macromedia Flash</a></li>
+    </ul>
+
+    <p><span class="alllinks"><a href="/pt-PT/docs/tag/Plugins:Ferramentas" title="tag/Plugins:Ferramentas">Veja todas...</a></span></p>
+
+    <h2 class="Related_Topics" id="T.C3.B3picos_relacionados" name="T.C3.B3picos_relacionados">Tópicos relacionados</h2>
+
+    <ul>
+     <li><a href="/pt-PT/docs/Extensões" title="Extensões">Extensões</a>, <a href="/pt-PT/docs/SVG" title="SVG">SVG</a>, <span class="comment"><a href="/pt-PT/docs/HTML/Canvas" title="HTML/Canvas">Canvas</a></span></li>
+    </ul>
+   </td>
+  </tr>
+ </tbody>
+</table>