Lighthouse reporting numerous failed passive listeners on other hosts

[OdinsHat]

Issue

When testing for passive listeners according to the documentation for Lighthouse on this audit test (point 4 under More Information) all failures from other hosts are ignored. Which makes sense as I can't affect the JS of a 3rd party scripts source.

However on my site that is not the case. They are included and stated as failures bringing the score down.

Example

As an example I've run the report on a page of my clients website and I get failures for issues on 3rd party hosted scripts (Google Maps in this case) which you can see in the screenshot. Something specifically stated shouldn't happen in the docs - see point 4 under More Information.

If any more information is required please ask.

Operating Environment

Operating Systems Tested: Arch Linux & Windows 10
Browsers Tested: Chrome 64 & Vivaldi 1.13
Lighthouse Version: 2.8.0

[patrickhulce]

Thanks for filing @OdinsHat!

The docs are out of date since we have now switched to Chrome's native warnings of passive event listeners which handles things a little differently. We could still add in a same-origin check if we need to, but all recent audits have moved away from this policy. Either way the docs need to be updated.

[laukstein]

Does Lighthouse fallows the spec proposal WICG/interventions#18 on defaulting touch passive listener?

Chrome 56 and Firefox 61 expecting already to fallow this spec.

[paulirish]

@laukstein yup we do

duping this into #4516