If someone clicks the "why are we asking this?" link it might be worth stopping/extending the timeout before the popup disappears so that the question is still there when they've read the answer.

In T178006#3679133, @Thryduulf wrote:

If someone clicks the "why are we asking this?" link it might be worth stopping/extending the timeout before the popup disappears so that the question is still there when they've read the answer.

That makes sense, thanks!

@EBernhardson can you add this functionality into your task list, please? :)

I've put up a patch to core that handles this in a slightly different way. Basically the timeouts will only consider time the page is visible, rather than wall time (as in, the time on the clock on your wall). Then the only thing that needs to happen is resetting the timeout back to 60s when the user clicks the link and goes to a different page to read the privacy statement or why we are running the test.

This test can be run at the same time as other tests, as long as we get bucketing separated.

Keeping this ticket here for future tests - all good practices - even if we don't end up running this exact test.