From 040852a09efb3bade338214269cb816209af5eab Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Sat, 31 Jul 2021 12:18:23 -0400 Subject: remove link 'title' attributes that's just the 'href' (pt-br) (#1738) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 👍🏽 --- .../css/styling_text/styling_lists/index.html | 2 +- .../forms/basic_native_form_controls/index.html | 6 ++-- .../how_to_build_custom_form_controls/index.html | 26 +++++++------- .../forms/how_to_structure_a_web_form/index.html | 2 +- .../sending_and_retrieving_form_data/index.html | 26 +++++++------- files/pt-br/learn/forms/your_first_form/index.html | 2 +- .../author_fast-loading_html_pages/index.html | 6 ++-- .../html/howto/use_data_attributes/index.html | 2 +- .../online_and_offline_events/index.html | 2 +- files/pt-br/tools/3d_view/index.html | 2 +- files/pt-br/tools/debugger/index.html | 6 ++-- .../tools/firefox_os_1.1_simulator/index.html | 6 ++-- files/pt-br/tools/index.html | 2 +- files/pt-br/tools/keyboard_shortcuts/index.html | 2 +- files/pt-br/tools/page_inspector/index.html | 2 +- files/pt-br/web/css/@charset/index.html | 2 +- files/pt-br/web/css/@keyframes/index.html | 4 +-- files/pt-br/web/css/background-size/index.html | 2 +- .../pt-br/web/css/font-feature-settings/index.html | 8 ++--- .../media_queries/using_media_queries/index.html | 4 +-- files/pt-br/web/css/overflow-wrap/index.html | 4 +-- .../index.html | 4 +-- files/pt-br/web/css/reference/index.html | 2 +- files/pt-br/web/css/text-rendering/index.html | 2 +- files/pt-br/web/css/text-shadow/index.html | 4 +-- .../web/css/transition-timing-function/index.html | 2 +- files/pt-br/web/css/transition/index.html | 4 +-- files/pt-br/web/css/used_value/index.html | 4 +-- .../web/guide/ajax/getting_started/index.html | 2 +- files/pt-br/web/guide/ajax/index.html | 2 +- .../web/guide/html/editable_content/index.html | 2 +- .../introduction_to_web_development/index.html | 42 +++++++++++----------- .../guide/mobile/mobile-friendliness/index.html | 2 +- .../web/guide/mobile/separate_sites/index.html | 2 +- files/pt-br/web/mathml/element/math/index.html | 4 +-- files/pt-br/web/mathml/index.html | 14 ++++---- files/pt-br/web/svg/attribute/class/index.html | 2 +- .../web/svg/attribute/contentstyletype/index.html | 2 +- .../web/svg/attribute/stroke-dashoffset/index.html | 2 +- files/pt-br/web/svg/attribute/style/index.html | 2 +- files/pt-br/web/svg/attribute/width/index.html | 16 ++++----- files/pt-br/web/svg/content_type/index.html | 16 ++++----- files/pt-br/web/svg/element/circle/index.html | 2 +- files/pt-br/web/svg/index.html | 10 +++--- files/pt-br/web/svg/tutorial/index.html | 2 +- 45 files changed, 132 insertions(+), 132 deletions(-) diff --git a/files/pt-br/learn/css/styling_text/styling_lists/index.html b/files/pt-br/learn/css/styling_text/styling_lists/index.html index f62387343a..f3295275ca 100644 --- a/files/pt-br/learn/css/styling_text/styling_lists/index.html +++ b/files/pt-br/learn/css/styling_text/styling_lists/index.html @@ -110,7 +110,7 @@ li.closed {list-style: disc;}

Contadores

-

Nota:  Alguns navegadores não suportam contadores. O conteúdo CSS e compatibilidade do navegador página no site de modo Quirks contém um gráfico detalhado de compatibilidade do navegador para este e outros recursos CSS. Páginas individuais na referência CSS neste local também têm tabelas de compatibilidade do navegador.

+

Nota:  Alguns navegadores não suportam contadores. O conteúdo CSS e compatibilidade do navegador página no site de modo Quirks contém um gráfico detalhado de compatibilidade do navegador para este e outros recursos CSS. Páginas individuais na referência CSS neste local também têm tabelas de compatibilidade do navegador.

Você pode usar contadores para numerar quaisquer elementos, não somente itens da lista. Por exemplo, em alguns documentos você pode querer numerar cabeçalhos ou parágrafos.

diff --git a/files/pt-br/learn/forms/basic_native_form_controls/index.html b/files/pt-br/learn/forms/basic_native_form_controls/index.html index d0fad5e66a..3696cd736b 100644 --- a/files/pt-br/learn/forms/basic_native_form_controls/index.html +++ b/files/pt-br/learn/forms/basic_native_form_controls/index.html @@ -309,7 +309,7 @@ original_slug: Web/Guide/HTML/Forms/Os_widgets_nativos   <option>Pear</option> </datalist> -
Note: According to the HTML specification, the {{htmlattrxref("list","input")}} attribute and the {{HTMLElement("datalist")}} element can be used with any kind of widget requiring a user input. However, it is unclear how it should work with controls other than text (color or date for example), and different browsers behave differently from case to case. Because of that, be cautious using this feature with anything but text fields.
+
Note: According to the HTML specification, the {{htmlattrxref("list","input")}} attribute and the {{HTMLElement("datalist")}} element can be used with any kind of widget requiring a user input. However, it is unclear how it should work with controls other than text (color or date for example), and different browsers behave differently from case to case. Because of that, be cautious using this feature with anything but text fields.
Screenshots of datalist on several platforms.
@@ -677,8 +677,8 @@ beans.oninput = function() {

To dig into the different form widgets, there are some useful external resources you should check out:

{{PreviousMenuNext("Learn/HTML/Forms/How_to_structure_an_HTML_form", "Learn/HTML/Forms/Sending_and_retrieving_form_data", "Learn/HTML/Forms")}}

diff --git a/files/pt-br/learn/forms/how_to_build_custom_form_controls/index.html b/files/pt-br/learn/forms/how_to_build_custom_form_controls/index.html index 0fdead0ece..e0291b80a7 100644 --- a/files/pt-br/learn/forms/how_to_build_custom_form_controls/index.html +++ b/files/pt-br/learn/forms/how_to_build_custom_form_controls/index.html @@ -36,7 +36,7 @@ original_slug: Web/Guide/HTML/Forms/How_to_build_custom_form_widgets
-

Note: Moving the focus around the page is usually done through hitting the tab key, but this is not standard everywhere. For example cycling through links on a page is done in Safari by default using the Option+Tab combination.

+

Note: Moving the focus around the page is usually done through hitting the tab key, but this is not standard everywhere. For example cycling through links on a page is done in Safari by default using the Option+Tab combination.

The widget is in its active state when:
@@ -78,12 +78,12 @@ original_slug: Web/Guide/HTML/Forms/How_to_build_custom_form_widgets

Another fun example: what will happen if the user hits the up or down arrow keys while the widget is in the open state? This one is a little bit trickier. If you consider that the active state and the open state are completely different, the answer is again "nothing will happen" because we did not define any keyboard interactions for the opened state. On the other hand, if you consider that the active state and the open state overlap a bit, the value may change but the option will definitely not be highlighted accordingly, once again because we did not define any keyboard interactions over options when the widget is in its opened state (we have only defined what should happen when the widget is opened, but nothing after that).

-

In our example, the missing specifications are obvious so we will handle them, but it can be a real problem on exotic new widgets, for which nobody has the slightest idea of what the right behavior is. So it's always good to spend time in this design stage, because if you define a behavior poorly, or forget to define one, it will be very hard to redefine it once the users have gotten used to it. If you have doubts, ask for the opinions of others, and if you have the budget for it, do not hesitate to perform user tests. This process is called UX Design. If you want to learn more about this topic, you should check out the following helpful resources:

+

In our example, the missing specifications are obvious so we will handle them, but it can be a real problem on exotic new widgets, for which nobody has the slightest idea of what the right behavior is. So it's always good to spend time in this design stage, because if you define a behavior poorly, or forget to define one, it will be very hard to redefine it once the users have gotten used to it. If you have doubts, ask for the opinions of others, and if you have the budget for it, do not hesitate to perform user tests. This process is called UX Design. If you want to learn more about this topic, you should check out the following helpful resources:

@@ -311,7 +311,7 @@ original_slug: Web/Guide/HTML/Forms/How_to_build_custom_form_widgets
-

Note: Creating reusable widgets is something that can be a bit tricky. The W3C Web Component draft is one of the answers to this specific issue. The X-Tag project is a test implementation of this specification; we encourage you to take a look at it.

+

Note: Creating reusable widgets is something that can be a bit tricky. The W3C Web Component draft is one of the answers to this specific issue. The X-Tag project is a test implementation of this specification; we encourage you to take a look at it.

Why isn't it working?

@@ -323,7 +323,7 @@ original_slug: Web/Guide/HTML/Forms/How_to_build_custom_form_widgets
  • The script is not loading. This is one of the most common cases, especially in the mobile world where the network is not very reliable.
  • The script is buggy. You should always consider this possibility.
  • The script is in conflict with a third party script. This can happen with tracking scripts or any bookmarklets the user uses.
  • -
  • The script is in conflict with, or is affected by, a browser extension (such as Firefox's NoScript extension or Chrome's NotScripts extension).
  • +
  • The script is in conflict with, or is affected by, a browser extension (such as Firefox's NoScript extension or Chrome's NotScripts extension).
  • The user is using a legacy browser, and one of the features you require is not supported. This will happen frequently when you make use of cutting-edge APIs.
  • @@ -404,7 +404,7 @@ original_slug: Web/Guide/HTML/Forms/How_to_build_custom_form_widgets

    In the code we are about to build, we will use the standard DOM API to do all the work we need. However, although DOM API support has gotten much better in browsers, there are always issues with legacy browsers (especially with good old Internet Explorer).

    -

    If you want to avoid trouble with legacy browsers, there are two ways to do so: using a dedicated framework such as jQuery, $dom, prototype, Dojo, YUI, or the like, or by polyfilling the missing feature you want to use (which can easily be done through conditional loading, with the yepnope library for example).

    +

    If you want to avoid trouble with legacy browsers, there are two ways to do so: using a dedicated framework such as jQuery, $dom, prototype, Dojo, YUI, or the like, or by polyfilling the missing feature you want to use (which can easily be done through conditional loading, with the yepnope library for example).

    The features we plan to use are the following (ordered from the riskiest to the safest):

    @@ -679,7 +679,7 @@ window.addEventListener('load', function () {

    We have built something that works and though we're far from a fully-featured select box, it works nicely. But what we've done is nothing more than fiddle with the DOM. It has no real semantics, and even though it looks like a select box, from the browser's point of view it isn't one, so assistive technologies won't be able to understand it's a select box. In short, this pretty new select box isn't accessible!

    -

    Fortunately, there is a solution and it's called ARIA. ARIA stands for "Accessible Rich Internet Application", and it's a W3C specification specifically designed for what we are doing here: making web applications and custom widgets accessible. It's basically a set of attributes that extend HTML so that we can better describe roles, states and properties as though the element we've just devised was the native element it tries to pass for. Using these attributes is dead simple, so let's do it.

    +

    Fortunately, there is a solution and it's called ARIA. ARIA stands for "Accessible Rich Internet Application", and it's a W3C specification specifically designed for what we are doing here: making web applications and custom widgets accessible. It's basically a set of attributes that extend HTML so that we can better describe roles, states and properties as though the element we've just devised was the native element it tries to pass for. Using these attributes is dead simple, so let's do it.

    The role attribute

    @@ -731,7 +731,7 @@ window.addEventListener('load', function () { highlightOption(select, optionList[index]); }; -

    Here is the final result of all these changes (you'll get a better feel for this by trying it with an assistive technology such as NVDA or VoiceOver):

    +

    Here is the final result of all these changes (you'll get a better feel for this by trying it with an assistive technology such as NVDA or VoiceOver):

    @@ -756,9 +756,9 @@ window.addEventListener('load', function () {

    Here are a few libraries you should consider before coding your own:

    diff --git a/files/pt-br/learn/forms/how_to_structure_a_web_form/index.html b/files/pt-br/learn/forms/how_to_structure_a_web_form/index.html index 2f73baf5e2..ff71e2664e 100644 --- a/files/pt-br/learn/forms/how_to_structure_a_web_form/index.html +++ b/files/pt-br/learn/forms/how_to_structure_a_web_form/index.html @@ -283,7 +283,7 @@ original_slug: Web/Guide/HTML/Forms/How_to_structure_an_HTML_form

    See Also

    {{PreviousMenuNext("Learn/HTML/Forms/Your_first_HTML_form", "Learn/HTML/Forms/The_native_form_widgets", "Learn/HTML/Forms")}}

    diff --git a/files/pt-br/learn/forms/sending_and_retrieving_form_data/index.html b/files/pt-br/learn/forms/sending_and_retrieving_form_data/index.html index 6f83b45aa4..7aab162da9 100644 --- a/files/pt-br/learn/forms/sending_and_retrieving_form_data/index.html +++ b/files/pt-br/learn/forms/sending_and_retrieving_form_data/index.html @@ -12,7 +12,7 @@ original_slug: Web/Guide/HTML/Forms/Sending_and_retrieving_form_data

    Sobre a arquitetura cliente / servidor

    -

    A web é baseada em uma arquitetura cliente / servidor muito básica que pode ser resumida da seguinte forma: um cliente (normalmente um navegador da Web) envia um pedido a um servidor (na maioria das vezes um servidor web como Apache, Nginx, IIS, Tomcat, etc.), usando o HTTP protocol. O servidor responde a solicitação usando o mesmo protocolo.

    +

    A web é baseada em uma arquitetura cliente / servidor muito básica que pode ser resumida da seguinte forma: um cliente (normalmente um navegador da Web) envia um pedido a um servidor (na maioria das vezes um servidor web como Apache, Nginx, IIS, Tomcat, etc.), usando o HTTP protocol. O servidor responde a solicitação usando o mesmo protocolo.

    A basic schema of the Web client/server architecture

    @@ -99,7 +99,7 @@ say=Hi&to=Mom

    O cabeçalho Content-Length indica o tamanho do corpo eo cabeçalho Content-Type indica o tipo de recurso enviado para o servidor. Vamos discutir esses cabeçalhos em um pouco.

    -

    Obviamente, as solicitações HTTP nunca são exibidas para o usuário (se você quiser vê-las, você precisa usar ferramentas como o Firefox Web Console ou o Chrome Developer Tools). A única coisa exibida para o usuário é o URL chamado. Assim, com uma solicitação GET, o usuário verá os dados em sua barra de URL, mas com uma solicitação POST, eles não. Isso pode ser muito importante por duas razões:

    +

    Obviamente, as solicitações HTTP nunca são exibidas para o usuário (se você quiser vê-las, você precisa usar ferramentas como o Firefox Web Console ou o Chrome Developer Tools). A única coisa exibida para o usuário é o URL chamado. Assim, com uma solicitação GET, o usuário verá os dados em sua barra de URL, mas com uma solicitação POST, eles não. Isso pode ser muito importante por duas razões:

    1. Se você precisar enviar uma senha (ou qualquer parte sensível de dados), nunca use o método GET ou corre o risco de exibi-lo na barra de URL.
    2. @@ -128,7 +128,7 @@ say=Hi&to=Mom

      Example: Python Bruto

      -

      This example uses Python to do the same thing--display the provided data on a web page. It uses the CGI Python package to access the form data.

      +

      This example uses Python to do the same thing--display the provided data on a web page. It uses the CGI Python package to access the form data.

      #!/usr/bin/env python
       import html
      @@ -150,13 +150,13 @@ print(say, " ", to)

      Outros idiomas e frameworks

      -

      Há muitas outras tecnologias do lado do servidor que você pode usar para o tratamento de formulários, incluindo Perl, Java, .Net, Ruby, etc. Basta escolher o que você mais gosta. Dito isto, é importante notar que é muito incomum usar essas tecnologias diretamente porque isso pode ser complicado. É mais comum usar um dos muitos frameworks agradáveis que facilitam o manuseio de formulários, como:

      +

      Há muitas outras tecnologias do lado do servidor que você pode usar para o tratamento de formulários, incluindo Perl, Java, .Net, Ruby, etc. Basta escolher o que você mais gosta. Dito isto, é importante notar que é muito incomum usar essas tecnologias diretamente porque isso pode ser complicado. É mais comum usar um dos muitos frameworks agradáveis que facilitam o manuseio de formulários, como:

      @@ -214,15 +214,15 @@ print(say, " ", to)

      SQL injection

      -

      SQL injection is a type of attack that tries to perform actions on a database used by the target web site. This typically involves sending an SQL request in the hope that the server will execute it (many times when the application server tries to store the data). This is actually one of the main vector attacks against web sites.

      +

      SQL injection is a type of attack that tries to perform actions on a database used by the target web site. This typically involves sending an SQL request in the hope that the server will execute it (many times when the application server tries to store the data). This is actually one of the main vector attacks against web sites.

      -

      The consequences can be terrible, ranging from data loss to access to a whole infrastructure by using privilege escalation. This is a very serious threat and you should never store data sent by a user without performing some sanitization (for example, by using mysql_real_escape_string() on a PHP/MySQL infrastructure).

      +

      The consequences can be terrible, ranging from data loss to access to a whole infrastructure by using privilege escalation. This is a very serious threat and you should never store data sent by a user without performing some sanitization (for example, by using mysql_real_escape_string() on a PHP/MySQL infrastructure).

      HTTP header injection and email injection

      These kinds of attacks can occur when your application builds HTTP headers or emails based on the data input by a user on a form. These won't directly damage your server or affect your users, but they are an open door to deeper problems such as session hijacking or phishing attacks.

      -

      These attacks are mostly silent, and can turn your server into a zombie.

      +

      These attacks are mostly silent, and can turn your server into a zombie.

      Be paranoid: Never trust your users

      @@ -247,6 +247,6 @@ print(say, " ", to)

      If you want to learn more about securing a web application, you can dig into these resources:

      diff --git a/files/pt-br/learn/forms/your_first_form/index.html b/files/pt-br/learn/forms/your_first_form/index.html index 8c1339a83a..f025cb7601 100644 --- a/files/pt-br/learn/forms/your_first_form/index.html +++ b/files/pt-br/learn/forms/your_first_form/index.html @@ -16,7 +16,7 @@ original_slug: Web/Guide/HTML/Forms/Meu_primeiro_formulario_HTML

      O que você precisa para trabalhar com formulários?

      -

      Você não precisa de nada mais do que o que é requisitado para trabalhar com HTML: Um editor de texto e um navegador. É claro, que se você esta acostumado a usá-los você pode ter vantagens de uma IDE completa como Visual Studio, Eclipse, Aptana, etc., mas cabe somente a você.

      +

      Você não precisa de nada mais do que o que é requisitado para trabalhar com HTML: Um editor de texto e um navegador. É claro, que se você esta acostumado a usá-los você pode ter vantagens de uma IDE completa como Visual Studio, Eclipse, Aptana, etc., mas cabe somente a você.

      A principal diferença entre um formulário de HTML e um documento regular de HTML é que, maioria das vezes, o dado coletado é enviado ao servidor. Nesse caso, você precisa configurar um servidor web para receber e processar os dados. Como configurar um servidor está além do escopo deste artigo, mas se você quer saber mais, consulte o artigo dedicado a este tema: Envio e recuperação de dados do formulário.

      diff --git a/files/pt-br/learn/html/howto/author_fast-loading_html_pages/index.html b/files/pt-br/learn/html/howto/author_fast-loading_html_pages/index.html index b5bf80270c..02504437b3 100644 --- a/files/pt-br/learn/html/howto/author_fast-loading_html_pages/index.html +++ b/files/pt-br/learn/html/howto/author_fast-loading_html_pages/index.html @@ -58,7 +58,7 @@ original_slug: Web/HTML/Dicas_para_criar_páginas_HTML_de_carregamento_rápido <TABLE>...</TABLE> <TABLE>...</TABLE> -

      Veja também: Especificações do layout multi-colunas CSS3 e layout de caixas flexíveis CSS3

      +

      Veja também: Especificações do layout multi-colunas CSS3 e layout de caixas flexíveis CSS3

      Especifique tamanhos para imagens e tabelas

      Se o browser puder imediatamente determinar a altura e/ou largura de suas imagens e tabelas, ele será capaz de exibir uma página sem ter que recalcular o fluxo do conteúdo. Isso não apenas acelera a exibição da página como previne mudanças irritantes no layout ao finalizar o carregamento. Por essa razão, height e width devem ser especificadas para imagens, sempre que possível.

      Tabelas devem usar a combinação CSS selector:property:

      @@ -121,8 +121,8 @@ original_slug: Web/HTML/Dicas_para_criar_páginas_HTML_de_carregamento_rápido

      Informações do Documento Original

      diff --git a/files/pt-br/learn/html/howto/use_data_attributes/index.html b/files/pt-br/learn/html/howto/use_data_attributes/index.html index d1c6154dc1..588b4b1ef7 100644 --- a/files/pt-br/learn/html/howto/use_data_attributes/index.html +++ b/files/pt-br/learn/html/howto/use_data_attributes/index.html @@ -68,6 +68,6 @@ article[data-columns='4'] {

      Veja também

      diff --git a/files/pt-br/orphaned/web/api/navigatoronline/online_and_offline_events/index.html b/files/pt-br/orphaned/web/api/navigatoronline/online_and_offline_events/index.html index 915b200b01..1644d68dc5 100644 --- a/files/pt-br/orphaned/web/api/navigatoronline/online_and_offline_events/index.html +++ b/files/pt-br/orphaned/web/api/navigatoronline/online_and_offline_events/index.html @@ -92,5 +92,5 @@ original_slug: Web/API/NavigatorOnLine/Online_and_offline_events
    3. The bug tracking online/offline events implementation in Firefox and a follow-up
    4. A simple test case
    5. An explanation of Online/Offline events
    6. -
    7. offline web applications em hacks.mozilla.org - mostra um aplicativo off-line e explica como funciona.
    8. +
    9. offline web applications em hacks.mozilla.org - mostra um aplicativo off-line e explica como funciona.
    10. diff --git a/files/pt-br/tools/3d_view/index.html b/files/pt-br/tools/3d_view/index.html index 82040654a6..13e303675e 100644 --- a/files/pt-br/tools/3d_view/index.html +++ b/files/pt-br/tools/3d_view/index.html @@ -101,7 +101,7 @@ translation_of: Tools/3D_View
    11. Painel HTML
    12. Painel de estilos
    13. Ferramentas
    14. -
    15. New Developer Tools in Firefox 11 Aurora (blog post)
    16. +
    17. New Developer Tools in Firefox 11 Aurora (blog post)
    18. {{ languages( { "ja": "ja/Tools/Page_Inspector/3D_view", "zh-cn": "zh-cn/Tools/Page_Inspector/3D_view"} ) }}

      diff --git a/files/pt-br/tools/debugger/index.html b/files/pt-br/tools/debugger/index.html index 88a7af5785..ce71b77d4a 100644 --- a/files/pt-br/tools/debugger/index.html +++ b/files/pt-br/tools/debugger/index.html @@ -206,7 +206,7 @@ original_slug: Tools/Depurador
    - +
    Show Original SourcesEnabling this option will make the debugger use source maps, if they are available, to display the original source for code which has been combined, minified, or even compiled to JavaScript from a language like CoffeeScript.Enabling this option will make the debugger use source maps, if they are available, to display the original source for code which has been combined, minified, or even compiled to JavaScript from a language like CoffeeScript.
    @@ -356,7 +356,7 @@ original_slug: Tools/Depurador

    Use a source map

    -

    JavaScript sources are often combined and minified to make delivering them from the server more efficient. Increasingly, too, JavaScript running in a page is machine-generated, as when compiled from a language like CoffeeScript. By using source maps, the debugger can map the code being executed to the original source files, making debugging much, much easier.

    +

    JavaScript sources are often combined and minified to make delivering them from the server more efficient. Increasingly, too, JavaScript running in a page is machine-generated, as when compiled from a language like CoffeeScript. By using source maps, the debugger can map the code being executed to the original source files, making debugging much, much easier.

    To tell the Debugger to use source maps if they are available, click the "Debugger settings" button and select "Show original sources" from the list of settings that pops up:

    @@ -438,7 +438,7 @@ original_slug: Tools/Depurador
  • chrome://browser/content/devtools/debugger-panes.js
  • -

    Unfortunately there is not yet any API to evaluate watches/expressions within the debugged scope, or highlight elements on the page that are referenced as variables in the debugged scope. (currently a work in progress, see bug 653545.)

    +

    Unfortunately there is not yet any API to evaluate watches/expressions within the debugged scope, or highlight elements on the page that are referenced as variables in the debugged scope. (currently a work in progress, see bug 653545.)

    Keyboard shortcuts

    diff --git a/files/pt-br/tools/firefox_os_1.1_simulator/index.html b/files/pt-br/tools/firefox_os_1.1_simulator/index.html index 7709cc565b..c9b8e6618e 100644 --- a/files/pt-br/tools/firefox_os_1.1_simulator/index.html +++ b/files/pt-br/tools/firefox_os_1.1_simulator/index.html @@ -56,7 +56,7 @@ original_slug: Tools/Simulador_Firefox_OS_1.1

    The Simulator is packaged and distributed as a Firefox add-on. To install it:

      -
    1. Using Firefox, go to the Simulator's page on addons.mozilla.org.
    2. +
    3. Using Firefox, go to the Simulator's page on addons.mozilla.org.
    4. Click "Add to Firefox".
    5. Once the add-on has downloaded you will be prompted to install it: click "Install Now".
    @@ -258,7 +258,7 @@ original_slug: Tools/Simulador_Firefox_OS_1.1

    Network Monitor

    -

    Thanks to the new Network Monitor, you can analyze the status, headers, content, and timing of all the network requests initiated by the app through a friendly interface. (Learn more about the Network Monitor.)

    +

    Thanks to the new Network Monitor, you can analyze the status, headers, content, and timing of all the network requests initiated by the app through a friendly interface. (Learn more about the Network Monitor.)

    Receipts

    @@ -305,7 +305,7 @@ original_slug: Tools/Simulador_Firefox_OS_1.1

    Troubleshooting on Linux

    -

    If you are unable to connect your device after creating udev rules, please see this bug.

    +

    If you are unable to connect your device after creating udev rules, please see this bug.

    Limitations of the Simulator

    diff --git a/files/pt-br/tools/index.html b/files/pt-br/tools/index.html index 46d40c34ff..3d1c88b090 100644 --- a/files/pt-br/tools/index.html +++ b/files/pt-br/tools/index.html @@ -181,7 +181,7 @@ translation_of: Tools
    Webmaker Tools
    Um conjunto de ferramentas desenvolvidas pela Mozilla, destinada a pessoas que estão começando no desenvolvimento Web.
    W3C Validators
    -
    O site W3C hospeda um número de ferramentas para checar a validação do seu website, incluindo HTML e CSS.
    +
    O site W3C hospeda um número de ferramentas para checar a validação do seu website, incluindo HTML e CSS.
    JSHint
    Ferramenta de análise de código JavaScript.
    diff --git a/files/pt-br/tools/keyboard_shortcuts/index.html b/files/pt-br/tools/keyboard_shortcuts/index.html index 273bb3c263..6d7802b6f0 100644 --- a/files/pt-br/tools/keyboard_shortcuts/index.html +++ b/files/pt-br/tools/keyboard_shortcuts/index.html @@ -616,7 +616,7 @@ translation_of: Tools/Keyboard_shortcuts -

    1. By default, on some Macs, the function key is remapped to use a special feature: for example, to change the screen brightness or the volume. See this guide to using these keys as standard function keys. To use a remapped key as a standard function key, hold the Function key down as well (so to open the Profiler, use Shift + Function + F5).

    +

    1. By default, on some Macs, the function key is remapped to use a special feature: for example, to change the screen brightness or the volume. See this guide to using these keys as standard function keys. To use a remapped key as a standard function key, hold the Function key down as well (so to open the Profiler, use Shift + Function + F5).

    Web Console

    diff --git a/files/pt-br/tools/page_inspector/index.html b/files/pt-br/tools/page_inspector/index.html index 9bb012d40d..dc62ac5b02 100644 --- a/files/pt-br/tools/page_inspector/index.html +++ b/files/pt-br/tools/page_inspector/index.html @@ -236,7 +236,7 @@ translation_of: Tools/Page_Inspector

    window.inspector

    -

    definido em inspector-panel.js. Atributos e funções:

    +

    definido em inspector-panel.js. Atributos e funções:

    -

    For the full specification of IRI references in SVG, see SVG 1.1 (2nd Edition): IRI references.

    +

    For the full specification of IRI references in SVG, see SVG 1.1 (2nd Edition): IRI references.

    @@ -232,7 +232,7 @@ hexdigit ::= [0-9A-Fa-f]
    length ::= number (~"em" | ~"ex" | ~"px" | ~"in" | ~"cm" | ~"mm" | ~"pt" | ~"pc")?
    -

    See the CSS2 specification for the meanings of the unit identifiers.

    +

    See the CSS2 specification for the meanings of the unit identifiers.

    For properties defined in CSS2, a length unit identifier must be provided. For length values in SVG-specific properties and their corresponding presentation attributes, the length unit identifier is optional. If not provided, the length value represents a distance in the current user coordinate system. In presentation attributes for all properties, whether defined in SVG1.1 or in CSS2, the length identifier, if specified, must be in lower case.

    @@ -329,7 +329,7 @@ hexdigit ::= [0-9A-Fa-f]
    <paint>
    -

    Os valores das propriedades {{SVGAttr("fill")}} e {{SVGAttr("stroke")}} são especificações do tipo de pintura a ser utilizada quando o preenchimento ou acariciando um determinado elemento gráfico. As opções disponíveis e sintaxe para <paint> estão descritos na especificação de pintura.

    +

    Os valores das propriedades {{SVGAttr("fill")}} e {{SVGAttr("stroke")}} são especificações do tipo de pintura a ser utilizada quando o preenchimento ou acariciando um determinado elemento gráfico. As opções disponíveis e sintaxe para <paint> estão descritos na especificação de pintura.

    Dentro do DOM do SVG, os valores do <paint> são representados usando objetos {{domxref("SVGPaint")}}.

    diff --git a/files/pt-br/web/svg/element/circle/index.html b/files/pt-br/web/svg/element/circle/index.html index 91eb82171d..b064fa35aa 100644 --- a/files/pt-br/web/svg/element/circle/index.html +++ b/files/pt-br/web/svg/element/circle/index.html @@ -30,7 +30,7 @@ translation_of: Web/SVG/Element/circle

     

    -

    » circle.svg

    +

    » circle.svg

    Atributos

    diff --git a/files/pt-br/web/svg/index.html b/files/pt-br/web/svg/index.html index 2b98ce0b13..ab061e7095 100644 --- a/files/pt-br/web/svg/index.html +++ b/files/pt-br/web/svg/index.html @@ -72,12 +72,12 @@ Este tutorial irá ajudá-lo a começar a trabalhar com SVG.
  • Orientações para autoria SVG
  • Uma visão geral do Projeto SVG da Mozilla
  • Perguntas frequentes sobre SVG e Mozilla
  • -
  • Slides e demos da palestra SVG and Mozilla no SVG Open 2009
  • +
  • Slides e demos da palestra SVG and Mozilla no SVG Open 2009
  • SVG como uma imagem
  • Animação SVG com SMIL
  • -
  • Leão, Borboleta & Tigre
  • +
  • Leão, Borboleta & Tigre
  • Galeria de arte SVG
  • -
  • Mais exemplos (SVG Samples croczilla.com, carto.net)
  • +
  • Mais exemplos (SVG Samples croczilla.com, carto.net)
  • Animação e interações

    @@ -85,7 +85,7 @@ Este tutorial irá ajudá-lo a começar a trabalhar com SVG.

    Assim  como o HTML, o SVG tem um modelo de documento (DOM), eventos e é acessível por JavaScript. Isto permite aos desenvolvedores criar animações e imagens interativas.

    diff --git a/files/pt-br/web/svg/tutorial/index.html b/files/pt-br/web/svg/tutorial/index.html index 80ca35deb9..e666577877 100644 --- a/files/pt-br/web/svg/tutorial/index.html +++ b/files/pt-br/web/svg/tutorial/index.html @@ -5,7 +5,7 @@ translation_of: Web/SVG/Tutorial ---

    Scalable Vector Graphics (Gráficos vetoriais escaláveis), SVG, é uma linguagem W3C XML  para marcação de gráficos. Ela é parcialmente implementada no Firefox, Opera, Navegadores com WebKit , Internet Explorer e outros navegadores.

    -

    Este tutorial tem como objetivo explicar as partes internas de SVG acompanhada de detalhes técnicos. Se você quiser usá-la apenas para desenhar belas imagens, você pode encontrar informações mais uteis na Página de documentação do Inkscape. Outra boa introdução ao SVG é fornecida pelo W3C' SVG Primer.

    +

    Este tutorial tem como objetivo explicar as partes internas de SVG acompanhada de detalhes técnicos. Se você quiser usá-la apenas para desenhar belas imagens, você pode encontrar informações mais uteis na Página de documentação do Inkscape. Outra boa introdução ao SVG é fornecida pelo W3C' SVG Primer.

    O tutorial está em um estágio inicial de desenvolvimento.Se puder, por favor ajude escrevendo um parágrafo ou dois. Pontos extras para quem escrever uma página inteira!
    -- cgit v1.2.3-54-g00ecf