Possible Quest 2.0 issue with MOMCANC/DADCANC in Module 1

[boyd-mj]

@Davinkjohnson @anthonypetersen We encountered issues with MOMCANC/DADCANC not displaying when it should while testing converted Module 1 in the dev renderer (https://episphere.github.io/quest-dev/). This was not reproducible with either the converted or not converted markup in the main renderer (https://episphere.github.io/quest/), but it did occur when testing in the PWA on Stage. No markup issues have been found.

This is a change in behavior from when we last tested Module 1 for the January production release and the code in this section hasn't changed. For all of these reasons and because of the other issues we've reported with testing in the dev renderer, we suspect an issue with Quest 2.0.

English Module 1 executive order changes are otherwise ready for production.

The markup we are testing can be found here: https://app.box.com/file/1776038852655

Thanks,
Jen

[cunnaneaq]

I passed this issue on to @JoeArmani to take a look. @boyd-mj did your team encounter this issue if MOM = 0/77/NR and MOM = 1? Or for one response in particular?

[cunnaneaq]

I was able to reproduce this error in dev and stage when I skipped [MOM], but not when I responded 0,1,or 77

[boyd-mj]

This fix has been delivered