diff options
Diffstat (limited to 'files/es/web/html')
| -rw-r--r-- | files/es/web/html/attributes/autocomplete/index.html | 181 | ||||
| -rw-r--r-- | files/es/web/html/element/shadow/index.html | 153 |
2 files changed, 0 insertions, 334 deletions
diff --git a/files/es/web/html/attributes/autocomplete/index.html b/files/es/web/html/attributes/autocomplete/index.html deleted file mode 100644 index 553e9a293c..0000000000 --- a/files/es/web/html/attributes/autocomplete/index.html +++ /dev/null @@ -1,181 +0,0 @@ ---- -title: The HTML autocomplete attribute -slug: Web/HTML/Attributes/autocomplete -translation_of: Web/HTML/Attributes/autocomplete -original_slug: Web/HTML/Atributos/autocomplete ---- -<p>El atributo <code>autocomplete</code> está disponible en varios tipos de {{HTMLElement("input")}} aquellos que toman un texto o valor numérico como entrada. <span class="seoSummary"><code>autocomplete</code> </span> permite a los desarrolladores web especificar qué permisos si los hay <span class="seoSummary">{{Glossary("user agent")}} </span> debe proporcionar asistencia automatizada para completar los valores de los campos de formulario, así como una guía para el navegador en cuanto al tipo de información que se espera en el campo.</p> - -<p> </p> - -<p>Los valores sugeridos generalmente depende del navegador. Normalmente, provienen de valores ingresados por el usuario, pero también pueden provenir de valores preconfigurados. Por ejemplo, un navegador puede permitir que el usuario guarde su nombre, dirección, número de teléfono y direcciones de correo electrónico para autocompletar así como también datos de tarjetas de crédito.</p> - -<p>Si un elemento {{HTMLElement("input")}} no tiene el atributo <code>autocomplete</code> , entonces los navegadores usan el atributo <code>autocomplete</code> del {{HTMLElement("form")}} que lo contiene. En otras palabras, el {{HTMLElement("form")}} del que el {{HTMLElement("input")}} desciende. También puede ser especificado en el atributo {{htmlattrxref("form", "input")}} del {{HTMLElement("input")}} en cuestión.</p> - -<p>Para más información vea el atributo {{htmlattrxref("autocomplete", "form")}} del elemento {{HTMLElement("form")}}</p> - -<div class="blockIndicator note"> -<p>Para proveer el autocompletado, el navegador necesita del los elementos <code><input></code>:</p> - -<ol> - <li>Que tengan <code>name</code> y/o <code>id</code></li> - <li>Pertenezcan a un elemento <code><form></code></li> - <li>Que el formulario tenga un botón {{HTMLElement("input/submit", "submit")}}</li> -</ol> -</div> - -<h2 id="Valores">Valores</h2> - -<dl> - <dt><code>"off"</code></dt> - <dd>The browser is not permitted to automatically enter or select a value for this field. It is possible that the document or application provides its own autocomplete feature, or that security concerns require that the field's value not be automatically entered. - <div class="note"><strong>Note:</strong> In most modern browsers, setting <code>autocomplete</code> to <code>"off"</code> will not prevent a password manager from asking the user if they would like to save username and password information, or from automatically filling in those values in a site's login form. See <a href="/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion#The_autocomplete_attribute_and_login_fields">the autocomplete attribute and login fields</a>.</div> - </dd> - <dt><code>"on"</code></dt> - <dd>The browser is allowed to automatically complete the input. No guidance is provided as to the type of data expected in the field, so the browser may use its own judgement.</dd> - <dt><code>"name"</code></dt> - <dd>The field expects the value to be a person's full name. Using <code>"name"</code> rather than breaking the name down into its components is generally preferred because it avoids dealing with the wide diversity of human names and how they are structured; however, you can use the following <code>autocomplete</code> values if you do need to break the name down into its components: - <dl> - <dt><code>"honorific-prefix"</code></dt> - <dd>The prefix or title, such as "Mrs.", "Mr.", "Miss", "Ms.", "Dr.", or "Mlle.".</dd> - <dt><code>"given-name"</code></dt> - <dd>The given (or "first") name.</dd> - <dt><code>"additional-name"</code></dt> - <dd>The middle name.</dd> - <dt><code>"family-name"</code></dt> - <dd>The family (or "last") name.</dd> - <dt><code>"honorific-suffix"</code></dt> - <dd>The suffix, such as "Jr.", "B.Sc.", "PhD.", "MBASW", or "IV".</dd> - <dt><code>"nickname"</code></dt> - <dd>A nickname or handle.</dd> - </dl> - </dd> - <dt><code>"email"</code></dt> - <dd>An email address.</dd> - <dt><code>"username"</code></dt> - <dd>A username or account name.</dd> - <dt><code>"new-password"</code></dt> - <dd>A new password. When creating a new account or changing passwords, this is the "Enter your new password" field, as opposed to any "Enter your current password" field that might be present. This may be used by the browser both to avoid accidentally filling in an existing password and to offer assistance in creating a secure password.</dd> - <dt><code>"current-password"</code></dt> - <dd>The user's current password.</dd> - <dt><code>"organization-title"</code></dt> - <dd>A job title, or the title a person has within an organization, such as "Senior Technical Writer", "President", or "Assistant Troop Leader".</dd> - <dt><code>"organization"</code></dt> - <dd>A company or organization name, such as "Acme Widget Company" or "Girl Scouts of America".</dd> - <dt><code>"street-address"</code></dt> - <dd>A street address. This can be multiple lines of text, and should fully identify the location of the address within its second administrative level (typically a city or town), but should not include the city name, ZIP or postal code, or country name.</dd> - <dt><code>"address-line1"</code>, <code>"address-line2"</code>, <code>"address-line3"</code></dt> - <dd>Each individual line of the street address. These should only be present if the <code>"street-address"</code> is also present.</dd> - <dt><code>"address-level4"</code></dt> - <dd>The finest-grained {{anch("Administrative levels in addresses", "administrative level")}}, in addresses which have four levels.</dd> - <dt><code>"address-level3"</code></dt> - <dd>The third {{anch("Administrative levels in addresses", "administrative level")}}, in addresses with at least three administrative levels.</dd> - <dt><code>"address-level2"</code></dt> - <dd>The second {{anch("Administrative levels in addresses", "administrative level")}}, in addresses with at least two of them. In countries with two administrative levels, this would typically be the city, town, village, or other locality in which the address is located.</dd> - <dt><code>"address-level1"</code></dt> - <dd>The first {{anch("Administrative levels in addresses", "administrative level")}} in the address. This is typically the province in which the address is located. In the United States, this would be the state. In Switzerland, the canton. In the United Kingdom, the post town.</dd> - <dt><code>"country"</code></dt> - <dd>A country code.</dd> - <dt><code>"country-name"</code></dt> - <dd>A country name.</dd> - <dt><code>"postal-code"</code></dt> - <dd>A postal code (in the United States, this is the ZIP code).</dd> - <dt><code>"cc-name"</code></dt> - <dd>The full name as printed on or associated with a payment instrument such as a credit card. Using a full name field is preferred, typically, over breaking the name into pieces.</dd> - <dt><code>"cc-given-name"</code></dt> - <dd>A given (first) name as given on a payment instrument like a credit card.</dd> - <dt><code>"cc-additional-name"</code></dt> - <dd>A middle name as given on a payment instrument or credit card.</dd> - <dt><code>"cc-family-name"</code></dt> - <dd>A family name, as given on a credit card.</dd> - <dt><code>"cc-number"</code></dt> - <dd>A credit card number or other number identifying a payment method, such as an account number.</dd> - <dt><code>"cc-exp"</code></dt> - <dd>A payment method expiration date, typically in the form "MM/YY" or "MM/YYYY".</dd> - <dt><code>"cc-exp-month"</code></dt> - <dd>The month in which the payment method expires.</dd> - <dt><code>"cc-exp-year"</code></dt> - <dd>The year in which the payment method expires.</dd> - <dt><code>"cc-csc"</code></dt> - <dd>The security code for the payment instrument; on credit cards, this is the 3-digit verification number on the back of the card.</dd> - <dt><code>"cc-type"</code></dt> - <dd>The type of payment instrument (such as "Visa" or "Master Card").</dd> - <dt><code>"transaction-currency"</code></dt> - <dd>The currency in which the transaction is to take place.</dd> - <dt><code>"transaction-amount"</code></dt> - <dd>The amount, given in the currency specified by <code>"transaction-currency"</code>, of the transaction, for a payment form.</dd> - <dt><code>"language"</code></dt> - <dd>A preferred language, given as a valid <a href="https://en.wikipedia.org/wiki/IETF_language_tag">BCP 47 language tag</a>.</dd> - <dt><code>"bday"</code></dt> - <dd>A birth date, as a full date.</dd> - <dt><code>"bday-day"</code></dt> - <dd>The day of the month of a birth date.</dd> - <dt><code>"bday-month"</code></dt> - <dd>The month of the year of a birth date.</dd> - <dt><code>"bday-year"</code></dt> - <dd>The year of a birth date.</dd> - <dt><code>"sex"</code></dt> - <dd>A gender identity (such as "Female", "Fa'afafine", "Male"), as freeform text without newlines.</dd> - <dt><code>"tel"</code></dt> - <dd>A full telephone number, including the country code. If you need to break the phone number up into its components, you can use these values for those fields: - <dl> - <dt><code>"tel-country-code"</code></dt> - <dd>The country code, such as "1" for the United States, Canada, and other areas in North America and parts of the Caribbean.</dd> - <dt><code>"tel-national"</code></dt> - <dd>The entire phone number without the country code component, including a country-internal prefix. For the phone number "1-855-555-6502", this field's value would be "855-555-6502".</dd> - <dt><code>"tel-area-code"</code></dt> - <dd>The area code, with any country-internal prefix applied if appropriate.</dd> - <dt><code>"tel-local"</code></dt> - <dd>The phone number without the country or area code. This can be split further into two parts, for phone numbers which have an exchange number and then a number within the exchange. For the phone number "555-6502", use <code>"tel-local-prefix"</code> for "555" and <code>"tel-local-suffix"</code> for "6502".</dd> - </dl> - </dd> - <dt><code>"tel-extension"</code></dt> - <dd>A telephone extension code within the phone number, such as a room or suite number in a hotel or an office extension in a company.</dd> - <dt><code>"impp"</code></dt> - <dd>A URL for an instant messaging protocol endpoint, such as "xmpp:username@example.net".</dd> - <dt><code>"url"</code></dt> - <dd>A URL, such as a home page or company web site address as appropriate given the context of the other fields in the form.</dd> - <dt><code>"photo"</code></dt> - <dd>The URL of an image representing the person, company, or contact information given in the other fields in the form.</dd> -</dl> - -<p>See the <a href="https://html.spec.whatwg.org/multipage/forms.html#autofill">WHATWG Standard</a> for more detailed information.</p> - -<div class="note"> -<p><strong>Note:</strong> The <code>autocomplete</code> attribute also controls whether Firefox will — unlike other browsers — <a href="https://stackoverflow.com/questions/5985839/bug-with-firefox-disabled-attribute-of-input-not-resetting-when-refreshing">persist the dynamic disabled state and (if applicable) dynamic checkedness</a> of an <code><input></code> across page loads. The persistence feature is enabled by default. Setting the value of the <code>autocomplete</code> attribute to <code>off</code> disables this feature. This works even when the <code>autocomplete</code> attribute would normally not apply to the <code><input></code> by virtue of its <code>type</code>. See {{bug(654072)}}.</p> -</div> - -<h2 id="Administrative_levels_in_addresses">Administrative levels in addresses</h2> - -<p>The four administrative level fields (<code>"address-level1"</code> through <code>"address-level4"</code>) describe the address in terms of increasing levels of precision within the country in which the address is located. Each country has its own system of administrative levels, and may arrange the levels in different orders when addresses are written.</p> - -<p><code>"address-level1"</code> always represents the broadest administrative division; it is the least-specific portion of the address short of the country name.</p> - -<h3 id="Form_layout_flexibility">Form layout flexibility</h3> - -<p>Given that different countries write their address in different ways, with each field in different places within the address, and even different sets and numbers of fields entirely, it can be helpful if, when possible, your site is able to switch to the layout expected by your users when presenting an address entry form, given the country the address is located within.</p> - -<h3 id="Variations">Variations</h3> - -<p>The way each administrative level is used will vary from country to country. Below are some examples; this is not meant to be an exhaustive list.</p> - -<h4 id="United_States">United States</h4> - -<p>A typical home address within the United States looks like this:</p> - -<p>432 Anywhere St<br> - Exampleville CA 95555</p> - -<p>In the United States, the least-specific portion of the address is the state, in this case "CA" (the official US Postal Service shorthand for "California"). Thus <code>"address-level1"</code> is the state, or "CA" in this case.</p> - -<p>The second-least specific portion of the address is the city or town name, so <code>"address-level2"</code> is "Exampleville" in this example address.</p> - -<p>United States addresses do not use levels 3 and up.</p> - -<h4 id="United_Kingdom">United Kingdom</h4> - -<p>The UK uses one or two address levels, depending on the address. These are the post town and, in some instances, the locality.</p> - -<h4 id="China">China</h4> - -<p>China can use as many as three administrative levels: the province, the city, and the district.</p> diff --git a/files/es/web/html/element/shadow/index.html b/files/es/web/html/element/shadow/index.html deleted file mode 100644 index 7c5720124f..0000000000 --- a/files/es/web/html/element/shadow/index.html +++ /dev/null @@ -1,153 +0,0 @@ ---- -title: <shadow> -slug: Web/HTML/Element/shadow -translation_of: Web/HTML/Element/shadow -original_slug: Web/HTML/Elemento/Shadow ---- -<p>{{obsolete_header}}</p> - -<p><span class="seoSummary">El <strong>HTML <code><shadow></code> element</strong>—es una parte absoluta de la suite tecnológica de <a href="/en-US/docs/Web/Web_Components">Web Components</a> —estaba destinado a ser utilizado como un shadow DOM {{glossary("insertion point")}}. Es posible que lo hayas usado si has creado varias root shadow bajo un shadow host. No es útil en HTML ordinario.</span></p> - -<table class="properties"> - <tbody> - <tr> - <th scope="row"><a href="/en-US/docs/Web/HTML/Content_categories">Content categories</a></th> - <td><a href="/en-US/docs/Web/HTML/Content_categories#Transparent_content_model">Transparent content</a>.</td> - </tr> - <tr> - <th scope="row">Permitted content</th> - <td><a href="/en-US/docs/Web/HTML/Content_categories#Flow_content">Flow content</a>.</td> - </tr> - <tr> - <th scope="row">Tag omission</th> - <td>{{no_tag_omission}}</td> - </tr> - <tr> - <th scope="row">Permitted parents</th> - <td>Any element that accepts flow content.</td> - </tr> - <tr> - <th scope="row">Permitted ARIA roles</th> - <td>None</td> - </tr> - <tr> - <th scope="row">DOM interface</th> - <td>{{domxref("HTMLShadowElement")}}</td> - </tr> - </tbody> -</table> - -<h2 id="Attributes">Attributes</h2> - -<p>This element includes the <a href="/en-US/docs/Web/HTML/Global_attributes">global attributes</a>.</p> - -<h2 id="Example">Example</h2> - -<p>Aquí está un ejemplo simple usando el <code><shadow></code> element. Es un archivo HTML con todo lo necesario en él.</p> - -<div class="note"> -<p><strong>Note:</strong> This is an experimental technology. For this code to work, the browser you display it in must support Web Components. See <a href="/en-US/docs/Web/Web_Components#Enabling_Web_Components_in_Firefox">Enabling Web Components in Firefox</a>.</p> -</div> - -<pre class="brush: html"><html> - <head></head> - <body> - - <!-- This <div> will hold the shadow roots. --> - <div> - <!-- This heading will not be displayed --> - <h4>My Original Heading</h4> - </div> - - <script> - // Get the <div> above with its content - var origContent = document.querySelector('div'); - // Create the first shadow root - var shadowroot1 = origContent.createShadowRoot(); - // Create the second shadow root - var shadowroot2 = origContent.createShadowRoot(); - - // Insert something into the older shadow root - shadowroot1.innerHTML = - '<p>Older shadow root inserted by - &lt;shadow&gt;</p>'; - // Insert into younger shadow root, including <shadow>. - // The previous markup will not be displayed unless - // <shadow> is used below. - shadowroot2.innerHTML = - '<shadow></shadow> <p>Younger shadow - root, displayed because it is the youngest.</p>'; - </script> - - </body> -</html> -</pre> - -<p>If you display this in a web browser it should look like the following.</p> - -<p><img alt="shadow example" src="https://mdn.mozillademos.org/files/10083/shadow-example.png" style="height: 343px; width: 641px;"></p> - -<h2 id="Specifications">Specifications</h2> - -<p>This element is no longer defined by any specifications.</p> - -<h2 id="Browser_compatibility">Browser compatibility</h2> - -<p>{{CompatibilityTable}}</p> - -<div id="compat-desktop"> -<table class="compat-table"> - <tbody> - <tr> - <th>Feature</th> - <th>Chrome</th> - <th>Firefox (Gecko)</th> - <th>Internet Explorer</th> - <th>Opera</th> - <th>Safari (WebKit)</th> - </tr> - <tr> - <td>Basic support</td> - <td>35</td> - <td>{{CompatGeckoDesktop("28")}}<sup>[1]</sup></td> - <td>{{CompatNo}}</td> - <td>26</td> - <td>{{CompatNo}}</td> - </tr> - </tbody> -</table> -</div> - -<div id="compat-mobile"> -<table class="compat-table"> - <tbody> - <tr> - <th>Feature</th> - <th>Android</th> - <th>Firefox Mobile (Gecko)</th> - <th>IE Phone</th> - <th>Opera Mobile</th> - <th>Safari Mobile</th> - </tr> - <tr> - <td>Basic support</td> - <td>37</td> - <td>{{CompatGeckoMobile("28")}}<sup>[1]</sup></td> - <td>{{CompatNo}}</td> - <td>{{CompatUnknown}}</td> - <td>{{CompatUnknown}}</td> - </tr> - </tbody> -</table> -</div> - -<p>[1] If Shadow DOM is not enabled in Firefox, <code><shadow></code> elements will behave like {{domxref("HTMLUnknownElement")}}. Shadow DOM was first implemented in Firefox 33 and is behind a preference, <code>dom.webcomponents.enabled</code>, which is disabled by default.</p> - -<h2 id="See_also">See also</h2> - -<ul> - <li><a href="/en-US/docs/Web/Web_Components">Web Components</a></li> - <li>{{HTMLElement("content")}}, {{HTMLElement("slot")}}, {{HTMLElement("template")}}, {{HTMLElement("element")}}</li> -</ul> - -<div>{{HTMLRef}}</div> |