It is now possible to get Firefox to display “…” to give a visual clue that a text is longer than the element containing it.
Performance is a key parameter of the user experience on the Web. To help Web developers monitor efficiently the performance of their Web pages, Aurora 7 implements the Navigation Timing specification: using the
window.performance.timing object, developers will be able to know the time when different navigation steps (such as
Complete) happened and deduce how long one step or a sequence of steps took to complete.
Reduced Memory Usage
Our continuous efforts to monitor and reduce memory consumption in Firefox will substantially pay off with Aurora 7:
- All those improvements are reflected in the about:memory page, which is now able to tell how much memory a particular Web page or the browser’s own UI, is using.
More frequent updates and detailed explanations of the memshrink effort are posted on Nicholas Nethercote’s blog.
First Steps of Azure
After the layout engine (Gecko) has computed the visual appearance (position, dimension, colors, …) of all elements in the window, the browser asks the Operating System to actually draw them on the screen. The browser needs an abstraction layer to be able to talk to the different graphics libraries of the different OSes, but this layer has to be as thin and as adaptable as possible to deliver the promises of hardware acceleration.
Azure is the name of the new and better graphics API/abstraction layer that is going to gradually replace Cairo in hardware accelerated environments. In Aurora 7, it is already able to interact with Windows 7’s Direct2D API to render the content of a <canvas> element (in a 2D context). You can read a detailed explanation of the Azure project and its next steps on Joe Drew’s blog.
- Specifying invalid values when calling
arcTo()no longer throws an exception; these calls are now correctly silently ignored.
strokeRectwith a zero width and height now correctly does nothing. (see bug 663190 )
drawImagewith a zero width or height
INVALID_STATE_ERR. (see bug 663194 )
toDataURL()method now accepts a second argument to control JPEG quality (see bug 564388 )
- XLink href has been restored and the MathML3
hrefattribute is now supported. Developers are encouraged to move to the latter syntax.
- Support for the
<mpadded>elements has been added and behavior of
lspaceattribute has been fixed.
- The top-level
<math>element accepts any attributes of the
mediumline thickness of fraction bars in
<mfrac>elements has been corrected to match the default thickness.
- Names for negative spaces are now supported.
Fileinterface’s non-standard methods
getAsText()have been removed as well as the non-standard properties
readAsArrayBuffer()method is now implemented. (see bug 632255 )
document.createEntityReferencehas been removed. It was never properly implemented and is not implemented in most other browsers. (see bug 611983 )
document.normalizeDocumenthas been removed. Use
Node.normalizeinstead. (see bug 641190 )
indexis out of bounds, previously it returned
null. (see bug 529328 )
Node.getFeaturehas been removed. (see bug 659053 )
WebSocketsare now available on Firefox Mobile. (see bug 537787 )
- Message logged with console.log before the WebConsole is opened are now stored and displayed once the WebConsole is opened.
(see the Web Console page in the Wiki)
Developer Relations Team, long time jQuery contributor and Open Web enthusiast. @louis_remi