Content.max.tokenizing.time
From MozillaZine Knowledge Base
Jump to navigationJump to search
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.
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)
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.
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]
First checked in
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)
