when I saved my Opensesame experiment as JATOS study, it detected no problems. But when I opened it in another browser, command like “Retrieving required webfonts” always appears. Can anybody help me to solve this problem? Thanks!
Osweb does not work reliably in all browsers yet. Mainly Internet Explorer and (older versions of) Edge cause some problems. Probably there is an error printed it in your browser's Javascript console. Can you open this is report back here what it says?
I'm new to Open Sesame, just followed a basic tutorial to set up a task (https://www.youtube.com/watch?v=FCXcnAv9aMA), which runs fine, exported it as JATOS study (no compatibility error flagged out; at least once I got rid of the form_text_display objects and replaced them with text objects on sketchpads), uploaded it on the JATOS try out server, and I too the same initial screen with the "Retrieving required webfonts" message. It gets stuck there. I changed the font "mono" to "arial" throughout the task, just in case, but to no avail. I tried the task in Chrome and in Edge. Same error. I'm attaching the Javascript console messages in case this helps working out what is happening. Also attach the task and its JATOS version.
Managed to solve it... Turns out it had to do with my navigator's blocking of potential trackers. I'm using Privacy Badger on my navigators. Once I disabled Privacy Badger for the cortex.jatos.org website, it ran fine (see video attached).
Is there a way to be able to detect whether the task gets stuck on the participant's computer in order to redirect them to an information page? I imagine that some participants might use privacy or anti-tracking software or plugins. Would be handy to be able to detect if the task fails to launch and display a message asking them to disable such feature for the experiment's site.
Nicole_, you might want to check whether your browser is using some sort of protection software or if you have some real time web safety software (antivirus etc.) that does something similar in your case.
I'm not too familiar with all the ways in which extensions such as Privacy Badger (which I use myself too, actually) interfere with loading of remote sources and/ or with JavaScript execution. I suspect that there is no single foolproof way to deal with this (because an extension can basically do whatever it wants), and for now the most pragmatic workaround is to simply instruct participants clearly which browsers are supported and inform them that browser extensions can break the experiment.
In the future, it might be useful to have OSWeb give more informative error messages in situations such as these. But for now, clear instructions are probably the way to go!
Comments
Hi @Nicole_
Osweb does not work reliably in all browsers yet. Mainly Internet Explorer and (older versions of) Edge cause some problems. Probably there is an error printed it in your browser's Javascript console. Can you open this is report back here what it says?
Hi there,
I'm new to Open Sesame, just followed a basic tutorial to set up a task (https://www.youtube.com/watch?v=FCXcnAv9aMA), which runs fine, exported it as JATOS study (no compatibility error flagged out; at least once I got rid of the form_text_display objects and replaced them with text objects on sketchpads), uploaded it on the JATOS try out server, and I too the same initial screen with the "Retrieving required webfonts" message. It gets stuck there. I changed the font "mono" to "arial" throughout the task, just in case, but to no avail. I tried the task in Chrome and in Edge. Same error. I'm attaching the Javascript console messages in case this helps working out what is happening. Also attach the task and its JATOS version.
Thanks!
Fabrice.
Hi there,
Managed to solve it... Turns out it had to do with my navigator's blocking of potential trackers. I'm using Privacy Badger on my navigators. Once I disabled Privacy Badger for the cortex.jatos.org website, it ran fine (see video attached).
Is there a way to be able to detect whether the task gets stuck on the participant's computer in order to redirect them to an information page? I imagine that some participants might use privacy or anti-tracking software or plugins. Would be handy to be able to detect if the task fails to launch and display a message asking them to disable such feature for the experiment's site.
Nicole_, you might want to check whether your browser is using some sort of protection software or if you have some real time web safety software (antivirus etc.) that does something similar in your case.
Best,
Fabrice.
PS: the video...
Hi @Fab ,
Thank you so much!
Regarding the warning message, I actually don't know whether this is possible. Perhaps @sebastiaan knows?
Cheers,
Lotje
Did you like my answer? Feel free to

Hi @Fab and @lvanderlinden ,
I'm not too familiar with all the ways in which extensions such as Privacy Badger (which I use myself too, actually) interfere with loading of remote sources and/ or with JavaScript execution. I suspect that there is no single foolproof way to deal with this (because an extension can basically do whatever it wants), and for now the most pragmatic workaround is to simply instruct participants clearly which browsers are supported and inform them that browser extensions can break the experiment.
In the future, it might be useful to have OSWeb give more informative error messages in situations such as these. But for now, clear instructions are probably the way to go!
— Sebastiaan
Check out SigmundAI.eu for our OpenSesame AI assistant!