Re: [whatwg/fetch] See if resource exists (#428)

I've opened https://bugs.chromium.org/p/chromium/issues/detail?id=677599 with Chromium. This Chrome behavior is (as you both indicate) unspecified. Firefox, for example, does not log to console. I have not tried Safari or Edge, lacking access to OSes to try whatever it is they implement.

@domenic: I highly disagree with leaving this purely to end-developers to toggle on broad-scale for all resources ("Hide network messages"). I very much think developers should have some ability to mark certain, known to be speculative requests as such, via programmatic means that the browser can pick up and follow. That way start-developers can mark up speculative requests, and end-developers can continue to get the logging they normally would for other resources. It doesn't make sense to me to have Chrome performing an unspecified, misleading, *un-opt-outable* developer-affecting behavior for something as mundane as speculatively trying to fetch resources that might simply not exist yet.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/428#issuecomment-269729730