feat: improve and refactor screen-shooter and split it into 3 versions

[shadowusr]

What's done?

• There are now 3 types of screen-shooters:
  • Elements screenshooter
  • Page screenshooter
  • Viewport screenshooter
• Elements screenshooter now includes various stability enhancements:
  • It can wait for unstable capture are to settle
  • It can retry if capture area moves or changes its size
  • It can capture elements with unstable sizes

Overall, we have 3 paths in elements screen shooter:

1. "Happy" path, if element position is stable, we start capturing it right away. If element position/size changes, we go to (2).
2. "Unstable" path. Here, we first verify area stability by doing this:
   1. Scroll through the whole area, saving capture area state at each offset, getting "left" checkpoints
   2. Do it again, getting "right" checkpoints
   3. Compare them, if they match, proceed, it means area changes its size, but deterministically
   4. If they don't, throw and try again
3. Finally, there's "best effort" path in the end. If capture area is unstable in size and we can't get 100% correct screenshot, we do what we can and capture what's possible, but this screenshot may contain seams/black stripes. In practice though, it's rare.

These stability checks come with a perf cost. But for now, it's the only guaranteed way to handle highly complex and unstable pages even on exotic browsers like ios safari.

Example:

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 88f77972a9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[DudaGod]

Amazing contribution 🔥
Especially great that there are clear logs with the execution time everywhere.

[shadowusr]

Fixed remaining issues in #1242, to apply them on top of all other changes and reliably test everything at once (though i agree this approach is not ideal)

[github-actions]

❌ Testplane browser-env run failed

Report