Confirmed users
1,009
edits
Gecko:1.9a2/ReleaseNotes: Difference between revisions
Added textframe and incremental xml information, moved acid2 compliance to reflow refactoring
(→Major Changes: reflow branch, inline-block+inline-table) |
(Added textframe and incremental xml information, moved acid2 compliance to reflow refactoring) |
||
| Line 15: | Line 15: | ||
* '''Known memory leak after prolonged browser usage.''' In order to better handle memory issues, a new garbage collection system has been implemented for native code. However, the process of integrating code into this system is still ongoing, and you may notice excessive memory usage after the browser is used for a long period of time. A restart should fix this problem, which will also be fixed in 1.9a3. | * '''Known memory leak after prolonged browser usage.''' In order to better handle memory issues, a new garbage collection system has been implemented for native code. However, the process of integrating code into this system is still ongoing, and you may notice excessive memory usage after the browser is used for a long period of time. A restart should fix this problem, which will also be fixed in 1.9a3. | ||
* Changes that [http://wiki.mozilla.org/Gecko:Reflow_Refactoring refactored] intrinsic width computation and incremental layout landed. This means that the code for determining intrinsic widths, used for width calculations in tables, floats, and absolutely positioned elements, has been rewritten. The code for handling incremental layout of pages (as the page arrives over the network, as images load, or as other dynamic changes are made) has also been changed extensively. | * '''Some Windows font rendering issues.''' With the partial landing of the new Cairo-based [http://wiki.mozilla.org/Gecko2:NewTextAPI nsTextFrame], some font rendering issues have been discovered on Windows-based platforms. These regressions will be fixed when the new code is fully landed for 1.9a3. | ||
* Changes that [http://wiki.mozilla.org/Gecko:Reflow_Refactoring refactored] intrinsic width computation and incremental layout landed. This means that the code for determining intrinsic widths, used for width calculations in tables, floats, and absolutely positioned elements, has been rewritten. The code for handling incremental layout of pages (as the page arrives over the network, as images load, or as other dynamic changes are made) has also been changed extensively. These changes also resolved all of the remaining issues with ACID2 compliance | |||
* The <code>inline-block</code> and <code>inline-table</code> values of CSS2.1's display property are now implemented. | * The <code>inline-block</code> and <code>inline-table</code> values of CSS2.1's display property are now implemented. | ||
== Minor Changes == | == Minor Changes == | ||
* ''' | * '''Incremental XML rendering.''' XML documents can now be rendered as they're downloaded from the originating server instead of after the full document has been downloaded. | ||
== Bugfixes == | == Bugfixes == | ||