Summary: | evalAfterBackForwardNavigation causes hang when page can't be cached | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> | ||||
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | ||||||
Priority: | P4 | ||||||
Version: | 420+ | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.4 | ||||||
Attachments: |
|
Description
Eric Seidel (no email)
2006-01-19 17:18:43 PST
Created attachment 5789 [details]
test case
I didn't consider a page not making it into the cache when I wrote the NavigationController class. The simple solution here is to have evalAfterBackForwardNavigation execute only once per page. In the future, if someone wants to use it more than once on a page, they can dream up a more interesting hashing solution. We could also use something like if (!navigationController.didNavigate) {...} or navigationController.setState(true) if (!navigationController.getState()) to make things arbitrarily extensible. valueForUndefinedKey would be helpful here, but it doesn't work yet. |