08-03-2021, 09:20 AM
The FindingFive team is delighted to announce that effective immediately, studies with audio stimuli, video stimuli, clickable videos in choice responses, and audio responses will function normally even under the problematic Google Chrome v92. We came up with our own workaround that "circumvents" Chrome's current bug (read on for details).
What is this about?
On July 20, Google released Chrome v92 (which remains the most up-to-date version), which unfortunately contains an odd, poorly-communicated, and arbitrary limitation on the max number of audio or video elements on a single web page (as an attempt to address a memory-leak issue). As the limit is set at 75, a fairly low number, it broke many web applications, including some FindingFive's studies.
What will Google do?
Google has regretted this sudden change and agreed to reverse course. However, Google's update/fix will not be available till at least the end of this week. For Chromebooks, the fix may not come until mid-August.
What did FindingFive do?
FindingFive recognized the urgency of this issue due to the huge market share of Google Chrome. We decided that it is not acceptable to wait for Google to fix this problem, because there will always be some participants who may not be able to upgrade from Chrome v92 in the near future. Therefore, we started immediately working on a mitigation solution on July 28.
We are happy to report that we have been successful at implementing a workaround for Chrome v92's odd behavior. This workaround applies automatically to all studies.
What do researchers need to do?
As the workaround results in a fairly major upgrade to FindingFive' Study Grammar system, researchers will need to preview their studies again before being able to launch new sessions that work under Chrome v92. Importantly, please do not select "Launch a new session using a previous version of the Study Grammar", as none of the previous versions will work under Chrome v92.
Buggy? Please let us know!
We burned quite a bit of midnight oil to implement this workaround, so it might be a tad buggy. Existing sessions won't be affected by the workaround, so there's no worry there. But if you notice suboptimal behavior when previewing your study, please feel free to chime in on this post!
What is this about?
On July 20, Google released Chrome v92 (which remains the most up-to-date version), which unfortunately contains an odd, poorly-communicated, and arbitrary limitation on the max number of audio or video elements on a single web page (as an attempt to address a memory-leak issue). As the limit is set at 75, a fairly low number, it broke many web applications, including some FindingFive's studies.
What will Google do?
Google has regretted this sudden change and agreed to reverse course. However, Google's update/fix will not be available till at least the end of this week. For Chromebooks, the fix may not come until mid-August.
What did FindingFive do?
FindingFive recognized the urgency of this issue due to the huge market share of Google Chrome. We decided that it is not acceptable to wait for Google to fix this problem, because there will always be some participants who may not be able to upgrade from Chrome v92 in the near future. Therefore, we started immediately working on a mitigation solution on July 28.
We are happy to report that we have been successful at implementing a workaround for Chrome v92's odd behavior. This workaround applies automatically to all studies.
What do researchers need to do?
As the workaround results in a fairly major upgrade to FindingFive' Study Grammar system, researchers will need to preview their studies again before being able to launch new sessions that work under Chrome v92. Importantly, please do not select "Launch a new session using a previous version of the Study Grammar", as none of the previous versions will work under Chrome v92.
Buggy? Please let us know!
We burned quite a bit of midnight oil to implement this workaround, so it might be a tad buggy. Existing sessions won't be affected by the workaround, so there's no worry there. But if you notice suboptimal behavior when previewing your study, please feel free to chime in on this post!