Content.notify.interval

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is content.notify.interval.

This article describes the preference content.notify.interval. To add, delete, or modify this preference, you will need to edit your configuration — do not edit this article.

1 Background 2 Possible values and their effects 3 Caveats 4 Recommended settings 5 First checked in 6 Has an effect in 7 Related bugs 8 Related preferences

[edit]

Background

Rather than wait until a page has completely downloaded to display it to the user, Mozilla applications will periodically render what has been received to that point. Because reflowing the page every time additional data is received greatly slows down total page load time, a timer was added so that the page would not reflow too often. This preference specfies the minimum amount of time to wait between reflows.

[edit]

Possible values and their effects

The minimum number of microseconds (1 second = 1,000,000 microseconds) between reflows. (Default: 120,000)

[edit]

Caveats

This preference does not exist by default. content.notify.ontimer must be set to true for this preference to take effect. This preference affects the default value of content.max.tokenizing.time.

[edit]

Recommended settings

Lowering the interval will lower the perceived page loading time but increase the total loading time, especially on slower connections. Values below 100,000 have a significant impact on performance and are not recommended.[1]

[edit]

First checked in

1999-12-03 by Vidur Apparao

[edit]

Has an effect in

Netscape (all versions since 6.0) Mozilla Suite (all versions since M11) Phoenix (all versions) Firebird (all versions) Firefox (all versions) Minimo (all versions) SeaMonkey (all versions)

[edit]