Since years ago (2019) we had the Chrome version pinned to 79 @ CIs. Since then, we have been examining new versions and attempting to bump to them here and there, always delaying it or reverting back to version 79.

You can see more details about this @ MDL-71108

Finally, because staying with that old version was causing real problems:

• Unconsistent results between CIs and local executions.
• Hard to trace problems with such old versions.
• ...

We have decided to finally unpin the Chrome version and that has been done @ MDL-71108.

As an immediate result of such unpin, we started getting a bunch (10-15) expected errors of type:

element not interactable: element has zero size

This issue is about to apply the following plan, that has been agreed:

1. Create the following new tag: @skip_chrome_zerosize.
2. Add that tag to all the zero-size failing scenarios/fatures.
3. MR 32 - Make it default @ nightlyjobs so, every run with Chrome will always exclude those "zerosize" scenarios.
4. Create a new job on every branch to run only the @skip_chrome_zerosize tag with Chrome, so we have them well present @ CIs, failing, while normal runs will pass. Headed and headless.
5. Document it @ moodledocs (link).
6. Comment about it in dev channel and in integration exposed.

The plan will allow us to use current Chrome (93 right now) version, keeping the "zerosize" errors under control and see how that affects to other errors that we were getting with the old Chrome 79 version.