[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 #50 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2011-09-20 13:33:03 PST ---
(In reply to comment #49)
> Britt, previously of Twitter here.
> 
> I agree with Kyle that the behavior is confusing.
> I think the answer lies in the question: "Is shift-reload different from 
> regular-reload?"
> 
> If yes, than we need to design based on that principal.

Yes, they are different.  The shift modifier causes the browser to disregard any locally cached copy of resources requested for the page load.


> It is a unique method that is well known by developers to revalidate all 
> resources, including those l loaded dynamically after the page.

I don't think it is well known or expected that shift+reload should impact the
behavior of resources requested after the page finishes loading.  Think about
what this does to an AJAX site, which rarely performs a page load.  If the
reload behavior becomes sticky, then you would end up requesting resources
end-to-end forever on an AJAX site.  This is most likely not what developers
intend.  (WebKit used to have this bug actually.)


> If no, then we make reload ubiquitous and have no shift-reload keyboard 
> shortcut, in order to not confuse users or developers, and develop 
> alternative means for developers to clear the asset cache while working.

This doesn't make sense to me.  There is a clear difference between reload and
shift-reload, which seems valuable to me.  Reload also does not impact 
resources loaded after the page has finished loading.

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