Garris
@felixblaschke -- What's your recommendation? What needs to happen?
Thanks @torbenberger, my question is, will the new image be backwards compatible? If the new assets _will_ be backwards compatible then you would just need to rework the build scripts...
Hi @torbenberger, sorry, my question is, will the new image continue to work on non-M1 hardware?
@torbenberger yes, I am not super knowledgeable about docker or M1 -- I don't want to break existing implementations so I just need someone to explain how this would work.
@apswak no progress here. I am a high-level docker user -- so I would need help to understand the most compatible way I can add support for this. (This is...
@cdeutsch what error did you get with v5.4.4?
@cdeutsch as a forward fix, maybe a newer version of puppeteer might address this issue?
@cdeutsch thank you for this workaround! I'd like to see if the puppeteer team has any response to your request before making an official BackstopJS patch (the rendering difference will...
Wow -- great progress! If we make this change would this break anything for puppeteer+docker users? Maybe just rendering differences?
Hi @klodoma, this ability is not built-in -- although, many engineers have asked for this. The 2 approaches to do this would be ### A) create a new command for...