annotated PreFigure diagrams in tabbed tasks

11 views
Skip to first unread message

David Austin

unread,
Mar 9, 2026, 3:41:07 PMMar 9
to prete...@googlegroups.com
Chrissy has an annotated PreFigure diagram in a tabbed #task (part c of that exercise) and the diagcess library is not working.  The specific #task also contains a #response element, which would appear in a Runestone build.  

The HTML source looks fine to me, and diagcess recognizes the diagram because it is appropriately modifying the source, as seen in the inspector.  I can get everything working if I do both of the following:

-- modify the publication file so that tasks are not tabbed
-- remove the #response element

Either of those changes alone is not enough.  I know this is complicated because diagcess is doing its own thing, but it seems that something about the PreTeXt build is also interfering.  In particular, the caret that should appear next to the Diagram Exploration Keyboard Controls is missing.  (A working example is here.)  That caret appears, when viewed in the inspector, as ::marker, but it appears that it is being removed in the same instances that diagcess is not working.

Chrissy's source for the diagram in the tabbed task

Andrew Scholer

unread,
Mar 9, 2026, 9:50:37 PMMar 9
to prete...@googlegroups.com
I don't know that tasks have anything to do with it. The response element seems to be the cause. It turns the exercise into a Runestone Shortanswer. The HTML for rendering that ripped out the existing contents of the statement and then pasted them into a new container.  That transplantation was deleting the event handlers responsible for allowing interaction.

The lack of handle on the Keyboard Controls summary was unrelated but due to styling applied to all summaries in Runestone.

Both fixed here:

https://github.com/RunestoneInteractive/rs/pull/1174




--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/CANXmVMArUfKViNP5Y%3Dd1R%2B4qqP-9fyYSE_ne2po7%2BJzfYfj--g%40mail.gmail.com.

David Austin

unread,
Mar 10, 2026, 7:29:43 AMMar 10
to prete...@googlegroups.com
Thanks for looking into this and for the fix, Andrew!

Reply all
Reply to author
Forward
0 new messages