Forgot to specify but I guess it's pretty obvious: that is a JavaScript error that shows up in the console.

teo8976@ - Thanks for filing the issue...!!

Could you please provide a sample test file/url to test the issue from TE-end. Also please provide detailed manual repro steps which led to the issue. This will help us in triaging the issue further.

Thanks...!!

I can't share the particular URL where I observe this.
However, it should be absolutely trivial for you to recreate one, you most likely just need to trigger the error (which I seem to understand is a matter of calling preventDefault() on those events which are now treated as passive by default) and you certainly know better than me how to do that.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

It doesn't look like this is an issue for the master branch. https://cs.chromium.org/search/?q=%22Unable+to+preventDefault+inside+passive+event%22&sq=package:chromium&type=cs The <URL> part is a static string https://www.google.com/url?q=https://www.chromestatus.com/features/5093566007214080 

As per comment #4, the reporter won't be able to provide any url and it won't be possible from TE-end to recreate a sample url. Hence, requesting someone from 	
Platform>DevTools team to please have a look into the issue. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

I have noticed that, when a single error like this shows up, the expected url is there as expected. When just few more identical errors show up, it still works as expected. (see screenshot 1).

However, when there are more than a few such errors, then the url gets replaced by the literal string "<URL>" in the collapsed error message (see screenshot 2). You can still see the actual url by expanding the repeated error into all its instances: there the url shows up correctly (see screenshot 3), but you shouldn't have to do that.

Deleted: S1.png 13.0 KB

	S1.png 13.0 KB View Download

Deleted: S2.png 8.2 KB

	S2.png 8.2 KB View Download

Deleted: S3.png 155 KB

	S3.png 155 KB View Download

Thanks for the report.  You are correct in #8, the "<URL>" is only added when Console detects several browser messages that can be grouped.  When a ton of messages are equal except for the URL, this cuts down on log spam.  However, we could be less aggressive, and check whether all the URLs are exactly the same.

In the short term, you can un-check the "Group similar" checkbox in the Console toolbar to disable grouping.