Brian Vaughn

I think #20107 is about the best we can do from our end.

>> I think a HEAD request would also log an error. (You can try it yourself and confirm.) > > I found HEAD request won't log error in my console....

That doesn't match expected behavior *or* the behavior I'm seeing when I try it myself: Are you sure you don't have something filtered out? (Do you see "1 hidden" to...

Can you show me what you mean by "the timeout trick"? For me, adding a timeout (even a large one) does not prevent an error from being logged immediately.

#20107 has been merged and will be released with the next DevTools release. That's all I'm going to do with this issue. If you'd like to look into additional potential...

I have just checked and I am unable to reproduce this. Given that this is the first time I've heard this issue being reported, I suspect there's something specific about...

@Guris Just to rule them out, I wonder if you would be willing to disable the other extensions and see if the problem persists? Alternately, and maybe an easier way...

I wonder about [Go Incognito](https://chrome.google.com/webstore/detail/go-incognito/oimfnddepdafdfmammggkfmdepfmipai?hl=en) as a potential suspect. I _doubt_ it would interfere with `localStorage` _in another extension_ but...it does seem related to that.

> as I mentioned in my previous message Sorry. I overlooked that detail. I don't have any ideas at this point. Can you do some debugging? I could send you...

Ah, my apologies for not mentioning this. 1. Open the extension settings in Chrome: `chrome://extensions/?id=fmkadmapgofadopljbjfkapdkoienihi` 2. Under "Inspect views", click the second link: This will open a separate developer tools...