I am using the literacy widget in a large evaluation and it renders appropriately in my browser (see first screenshot). However, when other colleagues load it on their computers, it doesn’t render appropriately (see second screenshot). I share the XLSForm extracted code as well in attachment. I had my colleagues clear their caches and it still loads incorrectly.
ReAL_ReadingPassage_KoboSupport.xlsx (14.7 KB)
Welcome back to the community, @claywestrope! I can confirm that it works with Chrome and Brave at my end. See screenshot below:
Consider recommending that your team utilize one of these browsers. However, please ensure that they are using the most up-to-date version for optimal performance.
Hi @Kal_Lam thank you for testing on your end. I have had colleagues update their browsers and they are using Chrome. The problem persists. I have sent it to other colleagues as well and it’s the same outcome. I am using the EU server (with success only for me) but uploaded it to the KF server as well to test and it did not render appropriately for me there. I’m wondering if there’s a setting that could be affecting this?
@claywestrope, if it’s functioning well on both your side and mine, it stands to reason that it should also be operational for the enumerators as well. You might consider asking your team to gather this data in online mode to observe its performance.
@Kal_Lam unfortunately, the issue persists on the enumerators’ tablets. I uploaded the form to https://validate.enketo.org/ to see if there were any coding bugs and it did provide the following output. I am uploading the full form here. I couldn’t translate the output result to target the issue. Are you able to identify the issue? I don’t know if this issue is causing the idiosyncratic issue of the literacy widget rendering correctly on some devices and not others, but it’s possible …
@claywestrope, please note that the ODK Validate tool is not designed to identify issues related to the literacy widget, as this widget is specifically used with KoboToolbox and is not applicable to other platforms where ODK Validate typically assesses XLSForm-related issues. Therefore, if the literacy widget functions correctly on one device, it should also work seamlessly on all other devices.
I would like to highlight that the tool functioned perfectly in my KoboToolbox account without any issues. Therefore, I believe your team should encounter similar results when using the same tool. I kindly urge you and your team to try using a different device, browser, or even consider upgrading the browser as previously suggested, to see if that resolves the issue.
@Kal_Lam understood on the ODK Validate tool.
What I’m trying to communicate is that the literacy widget works on about 50% of the devices that it’s tested on. We’ve tried multiple browsers and devices - all updated, as you’ve suggested. It only works on my device and a handful of others (including yours).
@Kal_Lam I think this may be a cache issue. The form works on devices that have previously loaded the literacy widget on previous form deployments for different projects (e.g., mine, yours, a couple others). However, it doesn’t work on devices that have never loaded the literacy widget. When I look at the elements of each in the screenshots below, we can see that the literacy widget doesn’t seem to load as a style for the device/browser that has never loaded the literacy widget. Could the widget asset be broken but because it’s cached on some machines it works correctly on those?
Literacy widget not working (look at the div class):
Literacy widget working (look at the div class):
Hi @Kal_Lam, I am having the same issue. Using an updated version of Chrome on my laptop and on my tablet, the literacy wigit is no longer functioning.
Welcome to the communtiy, @dzaas! @claywestrope, @dzaas kindly please be informed that I have brought this issue to the attention of our development team for further investigation to determine if it is related to our codebase. I will keep you updated on any progress.
Puede ser problemas de navegador, o problema de responsive
FYI this is now a known regression (in Enketo) and a fix is being worked and should be forthcoming soon.
Correct.
Hi @claywestrope & @dzaas , thank you for helping us investigating this issue. Our team has just deployed a fix to this issue and it should be working well now. Apologize for the inconveniences this may have caused.
