[Feature]: Harden playwright against core object manipulation

[hakito]

🚀 Feature Request

We have a situation, where we have to test a System, that replaces the core Map with some other object.

function Map()
{
  // some custom map stuff
}

Map.prototype.customMethod = function ...

Playwright crashes because it also relies on the Map object.

My proposal would be to make copies/references for the core objects and work with them within playwright.

Example

It would be also great to provide the core objects for own javascript calls:

browserContext.ProvideCoreObjectsAs("coreObjects");

And access them in for example in an init script:

myMap = new globalThis.coreObjects.Map()

Motivation

We have no option to get rid of this replacement by the external library. Our current (dirty) workaround is to inject a route, that overwrites the map replacement with another one that is compatible for playwright and the target application.

[yury-s]

Are you using some third-party library that overwrites standard Map or is it you in house solution? If you can point to a public website with the problem or share actual example, that'd be helpful. We've addressed a few similar issues in the past with other web APIs that were broken by some popular libraries. We need to understand the scope of the problem here and which Playwright APIs you call, as many parts of the injected script already run in an isolated world and are immune to these kind issues.