[Webkit-unassigned] [Bug 32423] Incorrect cache behavior with dynamic scripts after page-refresh

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=32423





--- Comment #11 from Kyle Simpson <getify at gmail.com>  2012-05-10 12:13:56 PST ---
(In reply to comment #10)
> This still repros at ToT so not a dupe. However, #3 seems like the bug, not #4. 

I designed the test so that the first request for script1 and script2 comes during/before load. When you subsequently request them a second time, by clicking the button, you're pulling from the cache that's already primed from during load, not dynamically loading them after page load.

This is why, I think, #3 is desired and not a bug, because when you refresh the page, and it again goes to load the scripts during page load, it's reloading resources that were previously loaded during a page load.

Or am I misunderstanding?

If I'm correct in that assertion, that's why #4 is the bug, because the assertion should continue to hold true on subsequent page loads where they are always first requested during a page load. Or no?


> When the user presses the browser's refresh button, we are supposed to revalidate all the subresources with the server. The desired heuristic is to revalidate anything which is started prior to the load event. Resources lazily loaded after the page loads shouldn't continue to be revalidated.

I understand that browsers desire that heuristic, but as Bug #30862's discussion thread (and other related ones) shows, I think developers have a more complex heuristic they desire: when they **shift+reload** the page, they want any hard resource that might have changed (like script files they are developing) to be revalidated, regardless of when it got loaded onto the page (race conditions!), whereas some soft resources (like perhaps XHR requests), I can see why those maybe shouldn't be re-validated (just like you don't necessarily want to re-submit form posts, etc).

But anyway, that's a rabbit trail best left for discussion in that other bug.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.