response element interfering with interactive behavior in print

[Tanaquil18]

I have a desmos interactive in a task of an exercise along with a response element. Everything seems fine in html, but when I build the pdf, the screenshot and qr code are not inserted. When I comment out the response element, then the screenshot and qr code are inserted as I would expect.

[rbeezer]

Can you post source here, with permission to add it to the sample article?

[Tanaquil18]

Sure! The full exercise has a lot going on. Do you want a minimal example that demonstrates this issue?

[rbeezer]

Yes, minimal may be better. Thanks.

[Tanaquil18]

<exercise> <statement> <p> Some text. </p> <figure> <caption>Solutions to the equation <m>15x+6y=15</m></caption> <interactive xml:id="desmos-15xplus6yis15-a" desmos="vvw2yv58qm" width="85%" aspect="4:3" /> </figure> </statement> <response/> </exercise>

[rbeezer]

Can you try a @label on the exercise and on the interactive? Required for the interactive exercise (was there no warning?), and recommended for the interactive.

[Tanaquil18]

Whoops, too minimal! In the actual exercise, I have a label on every task, and the response is inside the task.

No, no warning about missing a label. Adding labels to exercise and the interactive does not change the behavior. With response in, no screenshot or qr code in pdf. Comment out the response, and the screenshot and qr code are inserted where they should be.

[rbeezer]

In pretext-assembly.xsl (the pre-processor), when making a new version of source for consumption by converters to static formats, the conversion of Runestone-powered exercises fails to make other adjustments like dumbing down an interactive to a sidebyside. The LaTeX conversion does nothing with the interactive that bleeds through.

A fix will require a lot of surgery. Need to sleep on it, at a minimium.

[Tanaquil18]

I "fixed" it for the time being using versions. Responses belong to a component that is built for the web target, and not for the print target. I don't think I have any other interactives and Runestone-powered exercises together.

This seems low priority to me, especially if it requires a lot of work. Someone authoring interactives and Runestone-powered exercises together cares that it works in html, not print.