08-02-2021, 09:22 AM
You are most welcome!
We have burned some midnight oil and put in a workaround for Chrome 92's odd limitation. We are doing so because Google estimates that the "fix" will only start to be available around Aug 6 to Chrome browsers on Windows/Mac/Linux, and worse, the built-in Chrome in Chromebooks won't get this fix until much later in August.
The workaround should work pretty well, but it also represents a pretty dramatic rewrite of how FF handles audio and video stimuli. To err on the side of caution, we have updated only the testing server with the workaround. Can you help us test our new solution and see if your experiment works under Chrome now? You can go to https://testing.findingfive.com - it'll look identical to the main production server, but it runs on a beta version of FindingFive, and your studies will behave slightly differently.
Thanks!
We have burned some midnight oil and put in a workaround for Chrome 92's odd limitation. We are doing so because Google estimates that the "fix" will only start to be available around Aug 6 to Chrome browsers on Windows/Mac/Linux, and worse, the built-in Chrome in Chromebooks won't get this fix until much later in August.
The workaround should work pretty well, but it also represents a pretty dramatic rewrite of how FF handles audio and video stimuli. To err on the side of caution, we have updated only the testing server with the workaround. Can you help us test our new solution and see if your experiment works under Chrome now? You can go to https://testing.findingfive.com - it'll look identical to the main production server, but it runs on a beta version of FindingFive, and your studies will behave slightly differently.
Thanks!