Support for MHTML Baselines #168
Description
Disclaimer: This is just an idea that popped into my head- very experimental!
We currently store reference images. This approach certainly has its benefits - for example, when opening a PR, it's nice to see which images have changed or been newly added. However, it also has its downsides: we require Git LFS, which can feel a bit like a crutch.
One idea I had was that, instead of storing a reference image in the repository, we could store a reference MHTML file. This might even eliminate the need for Git LFS, since it’s plain text that Git can handle well (although further experiments would be needed). Furthermore, even if we were to support this approach, it would be optional for users to choose between reference images and reference MHTML files.
A significant benefit is that the specific browser version becomes less critical, as the baseline is rendered using the same browser as the actual image. On the other hand, this approach might not capture regressions introduced by browser updates.
I’m not yet sure where I stand on this suggestion - just wanted to dump the idea for now.