Dev tool Network filter doesn't work anymore with negative (name) research

[Marco De Rosa]

Hi all,

until now I have always used a negative filter in network panel in order to exclude by the name, a particular ajax call that was launched every 5 seconds. 

Simply I wrote -loadMess in the filter input and I get all other calls.

Unfortunately today I update Chrome (google-chrome-stable) to the last version 51.0.2704.63 (64-bit) and this filter doesn't work anymore.

Some idea to fix it?

[Blaise Bruer]

This is a known issue that has already been fixed, but will probably be a couple months before it hits stable. You can download Canary for now until the patch hits stable.

Sorry!

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/203a1bf8-53de-4664-adbf-3fe9f1ac007c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marco De Rosa]

Hi,

today I received an update of Chrome (version 51.0.2704.79 64-bit) but this problem has not been resolved.
Who should I contact to fix this issue?

[Jonathan Garbee]

That build won't have the fix as it isn't an issue that causes crashing. It will be fixed in one of the next two major releases. So you're looking for 52 most likely. If you can't wait, a beta channel is available to get earlier access to the latest code.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/4f9e03ca-22b2-4786-b536-fe3997913eb5%40googlegroups.com.

[Marco De Rosa]

after two months of waiting finally today I have received Chrome update 52.0.2743.82 on my Linux Mint OS!

And... 

...and negative filter does not work yet...

Il giorno venerdì 3 giugno 2016 17:19:57 UTC+2, Jonathan Garbee ha scritto:

That build won't have the fix as it isn't an issue that causes crashing. It will be fixed in one of the next two major releases. So you're looking for 52 most likely. If you can't wait, a beta channel is available to get earlier access to the latest code.

On Fri, Jun 3, 2016 at 9:15 AM Marco De Rosa <mder...@gmail.com> wrote:

Hi,

today I received an update of Chrome (version 51.0.2704.79 64-bit) but this problem has not been resolved.
Who should I contact to fix this issue?

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[Marco De Rosa]

Anyway is there any other working way to exclude each call containing a string? 

Enabling regex checkbox, I have a chance to solve this problem?

[Blaise Bruer]

You could do it in regular expressions but it'd be difficult because regular expressions are designed to find things and the program would inverse it if needed.

The best thing you should/could do is use Chrome beta, Chrome dev or Canary. We highly encourage developers to use one of these channels because it will help us find these problems before they hit stable and affect everyone.

[Marco De Rosa]

I understand your need that we, as developers, should use Chrome beta, dev or Canary, but on the other hand a web developer has to test his website with the major browsers in their stable releases.
I wrote on this post again, because in a previous post Jonathan told me that this issue (present inside version 51) would have been solved in the next stable release (52).
Unfortunately it did not happen..

Anyway find the correct way to exclude a string with regex on dev tool is not so easy.
I have done many tests but without success.
And today I asked on stackoverflow (http://stackoverflow.com/questions/38524801/chrome-dev-tool-any-way-to-exclude-each-call-containing-a-string-with-regex) but also the recommended solution seems not to work...

Of course, any suggestion is welcome :)

[PhistucK]

On Fri, Jul 22, 2016 at 10:20 PM, Marco De Rosa <mder...@gmail.com> wrote:

I understand your need that we, as developers, should use Chrome beta, dev or Canary, but on the other hand a web developer has to test his website with the major browsers in their stable releases.

​I second that. Not only that, but if you develop new features with an unstable Chrome build​, you may even not realize that something you are doing that seems to work correctly is really just a bug (sometimes a temporary one, sometimes not) and it is not supposed to work. It is rather problematic.

I understand the need to get bug reports and it is very important, I agree, but advocating and pushing this "use unstable builds" concept is not the best of ideas. Remember that web developers are either on a budget, or on a tight deadline. :(

☆PhistucK