From 28b935d9dca4bb27b8f53b4f211c004e233f52e4 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Mon, 2 Aug 2021 10:43:09 -0400 Subject: remove link 'title' attributes that's just the 'href' (pt-br, part 2) (#1841) --- files/pt-br/learn/forms/basic_native_form_controls/index.html | 2 +- .../learn/forms/how_to_build_custom_form_controls/index.html | 8 ++++---- .../pt-br/learn/forms/sending_and_retrieving_form_data/index.html | 2 +- files/pt-br/learn/forms/your_first_form/index.html | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) (limited to 'files/pt-br/learn/forms') 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 3696cd736b..e3940bb427 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 @@ -678,7 +678,7 @@ beans.oninput = function() {

{{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 e0291b80a7..cce6e0dd78 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 @@ -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):

    @@ -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):

    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 7aab162da9..65911fe514 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

    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 f025cb7601..8c58cedef6 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.

    -- cgit v1.2.3-54-g00ecf