Firefox 50 para desarrolladores

Firefox 50, based on Gecko 50, will ship in November 2016. This article provides information about the changes in this release that will affect developers. Nightly builds of what will become Firefox 50 are currently available on the Beta channel.

Cambios para desarrolladores Web

HTML

• El estilo por defecto <bdo> ahora asigna unicode-bidi con el valor isolate-override (bug 1249497).
• Asignar el atributo src del elemento <track> ahora funciona correctamente (bug 1281418).
• El atributo referrerpolicy en los elementos <area>, <a>, <img>, <iframe> y <link> ahora está disponible por defecto (bug 1223838, bug 1264165).

CSS

• Esquinas con estilos punteados y rayados (dashed, dotted) Border-radiused ahora son mostradas con el estilo especificado en lugar de estilo sólido (bug 382721).
• El selector pseudo-clase no estándar :-moz-full-screen-ancestor fue removido (bug 1199529).
• box-sizing: padding-box fue removido, dado que ya no forma parte de la especificación y Firefox era el unico entre los principales navegadores que lo implementaba (bug 1166728).
• Se removió el prefijo de los tres valores isolate, isolate-override, y plaintext de la propiedad unicode-bidi (bug 1141895).
• En modo de compatibilidad, la etiqueta de un elemento de lista ahora hereda el tamaño de la lista, como en el modo estandar (bug 648331).
• Las pseudo-clases :in-range y :out-of-range cambiaron su comportamiento para no coincidir elementos input deshabilitados o de solo lectura (bug 1264157).
• Se removió el prefijo de la pseudo-clase :any-link(bug 843579).
• El valor space para border-image-repeat fue implementado (bug 720531).

JavaScript

• La propiedad del ES2015 Symbol.hasInstance ha sido implementada (bug 1054906).
• El método de ES2017 Object.getOwnPropertyDescriptors() ha sido implementado (bug 1245024).
• El comportamiento de \W in RegExp con los flags unicode e ignoreCase cambió para estar de acuerdo con el borrador mas reciente de la especificación. Ahora no coincide con K, S, k, s, and KELVIN SIGN (U+212A), y LATIN SMALL LETTER LONG S (U+017F) (bug 1281739).

Herramientas de desarrollador

• El panel de Modelo de caja fue movido al panel lateral Computado (bug 1247729).

HTTP

• El protocolo experimental (y obsoleto) SPDY 3.1 ahora está deshabilitado por defecto bug 1287132.
• Se añadió soporte para X-Content-Type-Options  (bug 471020).
• Los prefijos de cookies __Host- and __Secure- han sido implementados. Ver Set-Cookie y bug 1283368.
• El encabezado Referrer-Policy ha sido implementado bug 1264164.

Seguridad

• El atributo ping del elemento <a> ahora se apega al connect-src CSP 1.1 policy directive (bug 1100181).
• Agregado soporte para la directiva sandbox CSP (bug 671389).
• Ahora es posible indicar una política content security policy for workers (bug 959388).
• El método Navigator.sendBeacon() ya no lanza una excepción si los datos de la baliza (Beacon Data) no pudieron ser enviados devido a una política de restricción consentimiento method Content Security Policy; en su lugar, retorna false como es esperado (bug 1234813).

Redes

• When a error has happened during an asynchronous XMLHttpRequest, the XMLHttpRequest.getAllResponseHeaders() method now returns an empty string (bug 1286744).
• Instead of returning a NetworkError, asynchronous XMLHttpRequest that fails for CORS or other network constraints now raises an error that can be catched like any other error (bug 709991).
• XMLHttpRequest.getResponseHeader() and XMLHttpRequest.getAllResponseHeaders() now also return empty headers by default. This can be controlled via the preference network.http.keep_empty_response_headers_as_empty_string (bug 918721).
• The only-if-cached option has been added to Request.cache (bug 1272436).

DOM

• The once option for EventTarget.addEventListener() is now supported (bug 1287706).
• The interface NodeList are now iterable and the methods forEach(), values(), NodeList.entries() and NodeList.keys() are now available (bug 1290636).
• The interface DOMTokenList are now iterable and the methods forEach(), values(), DOMTokenList.entries() and DOMTokenList.keys() are now available (bug 1290636).
• The methods Document.createElement() and Document.createElementNS() now have an optional options parameter for creating custom elements (bug 1276579).

SVG

• The allowReorder attribute has been dropped and the behavior it was setting is now the default for SVG <switch> elements (bug 1279690).
• The defer keyword for the preserveAspectRatio attribute on SVG <image> elements has been removed to follow the latest SVG2 specification (bug 1280425).

Drag and Drop API

• The DataTransfer.items property has been implemented, allowing access to multiple items being dragged and dropped using the HTML Drag and Drop API. To allow this, the DataTransferItem and DataTransferItemList interfaces are now supported as well (bug 906420). This is enabled by default.
• The old, obsolete Firefox specific drag and drop API events dragdrop and draggesture are no longer supported. Be sure to update any code still using them to use the HTML drag and drop API (bug 1162050.

Pointer Lock API

• The Pointer Lock API is now unprefixed (bug 991899).
• Before Firefox 50, requestPointerLock() asked for permission using a doorhanger, and pointer lock would not be enabled until the user granted permission. From Firefox 50, pointer lock is like the fullscreen API: it's granted immediately, but a notification is displayed explaining to the user how to exit (bug 1273351).

IndexedDB

• Ahora se envía un evento close al objeto IDBDatabase cuando la base de datos respectiva es cerrada de forma inesperada (bug 1151017).

Service Workers

• The WindowClient.navigate() method has been implemented. This method lets you open a specified URL into a client window which is being controlled by the service worker (bug 1218148).

WebGL

• The EXT_shader_texture_lod WebGL extension has been implemented (bug 1111689).
• The texImage methods have been updated for WebGL 2 to implement PBOs (PIXEL_UNPACK_BUFFER) (bug 1280499).

WebRTC

• Adding a track to a MediaStream now generates the addtrack event as described in the specification. The event is of type MediaStreamTrackEvent and is fired on the stream to which the track was added. You can use either MediaStream.addEventListener('addtrack', ...) or the MediaStream.onaddtrack property to handle "addtrack" events.
• The MediaStreamTrack interface now supports the ended event and the MediaStreamTrack.onended event handler.
• Firefox now supports the MediaStreamTrack.readyState property, which indicates whether the track is live or permanently ended.
• The MediaStreamTrack methods getConstraints() and getSettings() have been implemented; these let you get the most recently applied set of customized property constraints and the actual values of all of the track's constrainable properties, respectively. The accompanying data types have been documented as well.
• The RTCDataChannel.stream property has been removed. This was replaced with RTCDataChannel.id in Firefox 24, but was supported for backward compatibility. Please be sure to update your code to use the id property if you haven't done so yet.

Web Audio API

• The PannerNode interface now supports the 3D Cartesian space properties for the position (PannerNode.positionX, PannerNode.positionY, and PannerNode.positionZ) and directionality (PannerNode.orientationX, PannerNode.orientationY, PannerNode.orientationZ) of an audio source.
• The interface IIRFilterNode, which implements a general infinite impulse response (IIR) filter, has been implemented.
• Throttling in background tabs of timers created by Window.setInterval() and Window.setTimeout() no longer occurs if a Web Audio API AudioContext is actively playing sound. This should help prevent issues with timing-sensitive audio playback (such as music players generating individual notes using timers) in the background (bug 1181073).

Audio/Video

• The AlignSetting enum (representing possible values for VTTCue.align) incorrectly previously included the value "middle" instead of "center". This has been corrected (bug 1276130).
• The non-standard and experimental method HTMLMediaElement.seekToNextFrame() now seeks to the next frame in the media asynchronously, rather than synchronously, and returns a Promise which resolves once the seek is complete.
• The implementation of HTMLTrackElement has been corrected to allow <track> elements to load resources even if not in a document (bug 871747).

API de batería

• The navigator.battery property, which has been deprecated since Firefox 43, is now obsolete and has been removed. Use the navigator.getBattery() method instead to get a battery Promise, which will resolve when the BatteryManager is available for use; the BatteryManager is passed into the fulfillment handler for the promise (bug 12593355).

Archivos y directorios

• A subset of the File and Directory Entries API has been implemented, to improve compatibility with sites that were previously only compatible with Google Chrome (bug 1265767).
  • The asynchronous API interfaces have been implemented, with the caveat that only reading of files is supported; for example, the FileSystemFileEntry.createWriter() method is a no-op.
  • These interfaces have been implemented:
    • FileSystem
    • FileSystemEntry (properties only; the methods have not been implemented)
    • FileSystemFileEntry (except for createWriter())
    • FileSystemDirectoryEntry (except for removeRecursively())
    • FileSystemDirectoryReader
  • HTMLInputElement.webkitdirectory as well as the webkitdirectory attribute of the <input> element have been implemented; this lets you configure a file input to accept directories instead of files (bug 1258489).
  • HTMLInputElement.webkitEntries has been implemented; this returns an array of FileSystemEntry-based objects representing the selected items.
  • File.webkitRelativePath has been implemented; this contains the path of the file relative to the root of the containing FileSystemDirectoryEntry that was among the items in the list returned by HTMLInputElement.webkitGetEntries().
  • See File and Directory Entries API support in Firefox for details about what we do and do not support in this API.
  • These APIs are now enabled by default; some were previously available but only behind a preference (bug 1288683).
• We've implemented DataTransferItem.webkitGetAsEntry() as part of the File and Directory Entries API; this lets you obtain a FileSystemEntry representing a dropped file (bug 1289255). This is enabled by default.
• The HTMLInputElement.directory property, part of the Directory Upload API proposal, has been renamed to allowdirs (bug 1288681). This property is hidden behind a preference.

Ver también

• Compatibilidad de sitios para Firefox 50

Versiones anteriores