From 6e961125c89cdc8c3f644bff485254b3b4afee67 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Mon, 2 Aug 2021 11:26:13 -0400 Subject: remove link 'title' attributes that's just the 'href' (pt-br, part 3) (#1843) --- files/pt-br/web/api/xmlhttprequest/index.html | 2 +- .../web/api/xmlhttprequest/using_xmlhttprequest/index.html | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) (limited to 'files/pt-br/web/api/xmlhttprequest') diff --git a/files/pt-br/web/api/xmlhttprequest/index.html b/files/pt-br/web/api/xmlhttprequest/index.html index de045c5314..c5d8c7a9d8 100644 --- a/files/pt-br/web/api/xmlhttprequest/index.html +++ b/files/pt-br/web/api/xmlhttprequest/index.html @@ -711,7 +711,7 @@ if (!XMLHttpRequest.prototype.sendAsBinary) {
  • XMLHttpRequest referencias da W3C  e navegador fornecedores: diff --git a/files/pt-br/web/api/xmlhttprequest/using_xmlhttprequest/index.html b/files/pt-br/web/api/xmlhttprequest/using_xmlhttprequest/index.html index 3f5ff0c474..85852efc04 100644 --- a/files/pt-br/web/api/xmlhttprequest/using_xmlhttprequest/index.html +++ b/files/pt-br/web/api/xmlhttprequest/using_xmlhttprequest/index.html @@ -21,7 +21,7 @@ oReq.send();

    Manipulando Respostas

    -

    Existem vários tipos de atributos de resposta definidos pela especificação da W3C para o  XMLHttpRequest.  Eles informam ao cliente que efetuou a requisição XMLHttpRequest informações importantes sobre o status da resposta. Em alguns casos onde se lida com tipos de resposa de não-texto, os tipos de resposta podem envolver alguma manipulação e/ou análise conforme descrito nas seções seguintes.

    +

    Existem vários tipos de atributos de resposta definidos pela especificação da W3C para o  XMLHttpRequest.  Eles informam ao cliente que efetuou a requisição XMLHttpRequest informações importantes sobre o status da resposta. Em alguns casos onde se lida com tipos de resposa de não-texto, os tipos de resposta podem envolver alguma manipulação e/ou análise conforme descrito nas seções seguintes.

    Analisando e manipulando a propriedade responseXML

    @@ -60,7 +60,7 @@ oReq.overrideMimeType("text/plain; charset=x-user-defined"); /* ... */ -

    A especificação XMLHttpRequest Level 2  adiciona novo responseType attributes que tornam o envio e recebimento de dados muito mais fácil.

    +

    A especificação XMLHttpRequest Level 2  adiciona novo responseType attributes que tornam o envio e recebimento de dados muito mais fácil.

    var oReq = new XMLHttpRequest();
 
@@ -79,7 +79,7 @@ oReq.send();
 
 
    XMLHttpRequest fornece a capacidade de ouvir vários eventos que podem ocorrer enquanto o pedido está sendo processado. Isso inclui notificações periódicas de progresso, notificações de erro e assim por diante.
    
 
-
    Suporte para evento de progresso DOM monitorando a conexão XMLHttpRequest transfers siga a Web API specification for progress events: estes eventos implementam a interface {{domxref("ProgressEvent")}} .
    
+
    Suporte para evento de progresso DOM monitorando a conexão XMLHttpRequest transfers siga a Web API specification for progress events: estes eventos implementam a interface {{domxref("ProgressEvent")}} .
    
 
 
    var oReq = new XMLHttpRequest();
 
@@ -657,7 +657,7 @@ oReq.send(null);
    
 
 
    XMLHttpRequests being stopped
    
 
-
    If you end up with an XMLHttpRequest having status=0 and statusText=null, it means that the request was not allowed to be performed. It was UNSENT. A likely cause for this is when the XMLHttpRequest origin (at the creation of the XMLHttpRequest) has changed when the XMLHttpRequest is then open(). This case can happen for example when one has an XMLHttpRequest that gets fired on an onunload event for a window: the XMLHttpRequest gets in fact created when the window to be closed is still there, and then the request is sent (ie open()) when this window has lost its focus and potentially different window has gained focus. The way to avoid this problem is to set a listener on the new window "activate" event that gets set when the old window has its "unload" event fired.
    
+
    If you end up with an XMLHttpRequest having status=0 and statusText=null, it means that the request was not allowed to be performed. It was UNSENT. A likely cause for this is when the XMLHttpRequest origin (at the creation of the XMLHttpRequest) has changed when the XMLHttpRequest is then open(). This case can happen for example when one has an XMLHttpRequest that gets fired on an onunload event for a window: the XMLHttpRequest gets in fact created when the window to be closed is still there, and then the request is sent (ie open()) when this window has lost its focus and potentially different window has gained focus. The way to avoid this problem is to set a listener on the new window "activate" event that gets set when the old window has its "unload" event fired.
    
 
 
    Using XMLHttpRequest from JavaScript modules / XPCOM components
    
 
@@ -685,5 +685,5 @@ var oReq = XMLHttpRequest();
  
  • Apple developers' reference
    • 
  
  • "Using the XMLHttpRequest Object" (jibbering.com)
    • 
  
  • The XMLHttpRequest Object: W3C Specification
    • 
- 
  • Web Progress Events specification
    • 
+ 
  • Web Progress Events specification
    • 
 
-- 
cgit v1.2.3-54-g00ecf