Content.max.tokenizing.time

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is content.max.tokenizing.time.

This article describes the preference content.max.tokenizing.time. 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. This preference controls the maximum amount of time the application will be unresponsive while rendering pages.

[edit]

Possible values and their effects

The maximum number of microseconds (1 second = 1,000,000 microseconds) between reflows. (Default: triple the value of content.notify.interval)

[edit]

Caveats

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

[edit]

Recommended settings

Lowering the interval will make the application more responsive at the expense of page load time. A multiple of the value of content.notify.interval is recommended.[1]

[edit]

First checked in

2001-06-20 by Kevin McCluskey

[edit]

Has an effect in

Netscape (all versions since 6.1) Mozilla Suite (all versions since 0.9.2.1) Phoenix (all versions) Firebird (all versions) Firefox (all versions) Minimo (all versions) SeaMonkey (all versions)

[edit]