MemoryFootprint

From RuntimeWiki

A Web Browser should be able to master its memory footprint, and could possibly offer several memory management strategies to its users.

Showing a "passive page" (containing only HTML text styled by a CSS stylesheet) has no reason to occupy much more than the total size of the resources needed to display the data displayed in a screen page.

And typically, images, dynamic content (such as Flash, SilverLight, Applets) could be dynamically loaded when the physical screen comes to the region of the HTML page that displays them.

This strategy could typically be named "Lazy Loading", mimicking what we already have in Object/Relational Mapping tools.

Users should also be able to tell their browsers not to exceed a certain limit in RAM (40 Mo would be ideal for me, but one could accept to let browsers occupy 150 Mo... More sounds like a sacrilege), or to have a dedicated limit for each kind of resource.