[Webkit-unassigned] [Bug 30862] Dynamically inserted subresources aren't revalidated even when the containing document is reloaded

[bugzilla-daemon at webkit.org]

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





--- Comment #52 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2011-09-20 15:46:25 PST ---
(In reply to comment #51)
> Darin, in previous comments it was discussed that the sticky nature of lazy loaded requests implementing a refresh be given a timer, so that only those requested immediately during page load would be refreshed. It would not happen forever. Check your comment #35 for example.

Right, I forgot about that, but I still agree with my earlier comment.  Actually, I feel a bit stronger about it.  Using a timeout for this sort of thing will likely add to confusion.  It creates a flaky / unreliable behavior, and that just doesn't seem like a good thing for the web platform.


> The idea is that developers might have to load in a required JS file, etc. at page load time, but conditionally on a cookie or something. So from the developer's point of view, it's helpful to have those immediately-lazy-loaded resources be considered packaged with the page and able to be refreshed. Given the timer suggestion, I think it's a suggestion that produces a big benefit for developers (and even end users, who will get changes to lazy-loaded resources in sync with changes to the page) without causing undue load for resources requested much later.

It is a very bad idea to have end-user observed behavior depend on a timer.  What value of a timer is good?  5 seconds?  30 seconds?  None of those are good choices.  The subresources requested after page load can be delayed a long time.  This would create a flaky / unreliable web platform.

I believe the best solution here would be to provide some special option for developers to use.  I should also remind people that it is really easy to clear browsing data in Chrome and Firefox.  Just type Ctrl+Shift+Del.

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