Content.notify.backoffcount

From MozillaZine Knowledge Base

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

This article describes the preference content.notify.backoffcount. 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

2.1 -1 2.2 0 2.3 Any positive integer

3 Caveats 4 First checked in 5 Has an effect in 6 Related bugs 7 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 controls the maximum number of times the content will do timer-based reflows. After this number has been reached, the page will only reflow once it is finished downloading.

[edit]

Possible values and their effects

[edit]

-1

No limit on timer-based reflows (Default)

[edit]

0

Don't do any timer-based reflows.

[edit]

Any positive integer

The maximum number of timer-based reflows to perform.

[edit]

Caveats

This preference does not exist by default. content.notify.ontimer must be set to true for this preference to take effect.

[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]