Garris

FWIW — I usually do a LinkedIn article when we do something cool... Eg. https://www.linkedin.com/pulse/backstopjs-version-30-chrome-headless-support-has-landed-shipon https://www.linkedin.com/pulse/backstopjs-version-31-new-ui-usability-features-docker-garris-shipon https://www.linkedin.com/pulse/backstopjs-v32-has-arrived-puppeteer-support-garris-shipon These are also tweeted out etc.

I am sorry about the confusion. I have not been able to keep up with the project the way I used to.

Thank you @chrimesdev for the kind words! I was thinking about this -- what the project really needs is release support. If someone would like to take on a release...

Thanks so much all. I just added a basic changelog and will keep this updated. Feel free to decorate or format it in any way. Cheers!

This is an important pattern. Would be a good idea to add this to the examples. Unfortunately -- I suspect that `await` is going to be problematic for many older...

I solved my immediate need with this... ``` chromyChain .rect() .result(function (rect) { chromyChain.mouseMoved(rect.left, rect.top) }); ``` But I highly recommend enabling this pattern for all the "mouse" methods... `.mouseMoved(,...

Thanks for the reply, just to be clear -- the issue is happening with the `screenshotMultipleSelectors()` use-case. I like your first idea. Perhaps adding a method to force the necessary...

@shanemcgraw this looks like it might work -- but did you try manipulating DOM as opposed to using console.log ? I am not sure console.log works in this context? Just...

I have an idea. How about passing in a new chromy object into the evaluate.()? .evaluate(\`window._parentChromy = ${new Chromy().chain()}\`) Then do another .evaluate() with your form manipulation.

Don't know if that will work -- evaluate might have to be primative .