Closed Bug 388387 Opened 13 years ago Closed 13 years ago

[FIX]Avoid generating state keys for form restoration if there's no state to get

Categories

(Core :: DOM: Core & HTML, defect)

x86
Linux
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

(Keywords: perf)

Attachments

(1 file)

Attached patch Like soSplinter Review
This is a bit of a hack.... Right now, during initial load of a page, we generate form state keys for form controls, even though there is no state to get.  I'm proposing we add a way to check for this situation and avoid generating the state keys.  It's a hack because it'll only affect initial pageloads.  Non-bfcached history navigation will still suffer from the key generation performance, since there will be a state for the root scrollframe hanging around, if nothing else.

Ideally, the pres state would be subdivided better somehow; I'm sure we have bugs on that.
Attachment #272591 - Flags: superreview?(jonas)
Attachment #272591 - Flags: review?(jonas)
Attachment #272591 - Flags: superreview?(jonas)
Attachment #272591 - Flags: superreview+
Attachment #272591 - Flags: review?(jonas)
Attachment #272591 - Flags: review+
Checked in.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.