Method to uniquely identify Pages/Targets?

When using browser.pages() or browser.targets() is there a way to uniquely identify each Page object? I.e. is there some property of the Page object that I can compare with those returned by browser.pages() to identify if they’re both referencing the same browser tab?

[Khady]

Can you please share if there are other tools besides lighthouse that you use? I’d love to take a look.

For now, I’m using puppeteer, lighthouse, chrome-launcher and handmade requests using CDP or the /json,/json/version,/new,/close commands. Trying to unify all this. I’m happy using page._client.targetId for now.

I created an issue and a PR on lighthouse repository while trying to find a nice way to mix puppeteer and lighthouse. But the story doesn’t seem to be as easy as expected. I would be very happy to see a conversation/guideline about the interop between those two tools.

This specific PR is relying on the targetId. But I’m not a CDP/Chrome expert. So there is maybe a better way to achieve this rather than to pass an id everywhere.

[aslushnikov]

I still think it would be interesting to have the targetId exposed. I use it while debugging (checking the number of pages opened, which ones are opened, etc) from outside of puppeteer.

@Khady would it help if we give you a nicer toString() for target/page objects?

And to pass it to other tools like lighthouse.

Can you please share if there are other tools besides lighthouse that you use? I’d love to take a look.

The lighthouse has been mentioned a few times already; we’d probably need to do a better interop. cc @paulirish