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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Apr 27 13:33:10 PDT 2017


Brian Burg <bburg at apple.com> changed:

           What    |Removed                     |Added
                 CC|                            |bburg at apple.com

--- Comment #1 from Brian Burg <bburg at apple.com> ---
(In reply to Alexander Romanovich from comment #0)
> The reload policy used when the web inspector is both open and foregrounded
> (i.e. all subresources revalidated) does not match the (new) reload policy
> used when the web inspector is open and backgrounded, or not open at all
> (i.e. only expired subresources revalidated).

It doesn't have to do with foreground vs background. It's whether you are sending Cmd-R to Safari or Web Inspector, which use different APIs. Currently, Web Inspector does this in the backend:

    OptionSet<ReloadOption> reloadOptions;
    if (optionalIgnoreCache && *optionalIgnoreCache)
        reloadOptions |= ReloadOption::FromOrigin;

So I believe we just need to use ReloadOption::ExpiredOnly in the normal case.

> This could be confusing to developers who would expect the web inspector to
> reflect what's actually happening under normal conditions. It would be
> preferable if the foregrounded web inspector used the default reload policy.
> If the developer needs to force revalidation, they can do so by reloading
> from origin via shift-refresh.
> See original context here: https://bugs.webkit.org/show_bug.cgi?id=171264#c16

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/20170427/234e3d1f/attachment-0001.html>

More information about the webkit-unassigned mailing list