Warren Day
Warren Day
Unfortunately this isn't possible. Chrome exposes no api to listen to the start of a request that we are able to associate to the end of a request.
We only receive an event from the chrome api once the request has finished. There is a way to get events when a request starts, which contains less information, but...
I think that's just in the context of all the events on the webRequest api. Whereas we are mixing webRequest and network.
This is being worked on currently.
Like this idea, would be great in cases the query string is huge.
Could be something to do with regex being triggered. I'll take a look.
Agree @iainmck29 I have the same problem. We could look at jumping to the first match and having a UI to jump to next/prev.
This is currently planned. I'll get to it once subscriptions is finished and released.
This has been released for a while. Currently shows matches in yellow. Jumps to the first match.
Closing this as we do have jump to search. If you're after something more, please feel free to raise a PR. All are welcome!