[Webkit-unassigned] [Bug 171385] Web Inspector: webkit reload policy should match default behavior

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 28 12:17:28 PDT 2017


--- Comment #3 from Alexander Romanovich <alex at sirensclef.com> ---
Makes sense.

Another impact of the difference in API between Web Inspector and Safari results in the fact that you can force a reload-from-origin with cmd-shift-r in Web Inspector but not in Safari. It would be helpful to allow cmd-shift-r in Safari as well.

Aside from clearing up the above-mentioned confusion that can arise from a divergence in behavior, allowing cmd-shift-r in Safari, and not just in Web Inspector, would contribute to solving this long standing issue: Safari does not currently support 304s for main resources like all other major browsers do (https://bugs.webkit.org/show_bug.cgi?id=114738).

This is because a cmd-r in Safari currently does a reload-from-origin for the main resource, whereas it should perform revalidation. Resolving that would be a huge performance win, especially on large pages like blogs, and my hope would be that solving this would assist in bringing traction on that very important issue as well.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170428/36f9b6f9/attachment.html>

More information about the webkit-unassigned mailing list