RunestoneInteractive / RunestoneInteractive/rs
Runestone Issue: New grading interface, some doenet problems don't expand and get cut off
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 117
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 24
Description
When we try to see student work in the grader and click on a problem in an assignment, we get to see each student's individual version of a randomized problem and all their attempts. This is amazing, and better than we ever had (or still have) with WeBWorK in Runestone!
However, many of the Doenet problems are very long, and the scroll within the grader interface does not expand to show the entire problem, but will instead just cut it off so that it's impossible to see what the student did. I've tried zooming out in case it's a small screen issue, but that doesn't fix it.
Perhaps interestingly, when I tried to find an example in a Preview Activity, which are often very long and are inside of Project-like, I couldn't quickly find one; all the preview problems I checked just now had long enough scroll bars.
But I do see the bug often within an Exercise within Exercises. Other instructors have reported the same things to me on various Doenet exercises, but just for an example, question id ac-single-d_2_doe-int-ex-5-2-1 which is the first exercise in the 5.2 Exercises assignment within the Franciscan_MTH162_F26 course.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the grader interface and reproduce the issue with Doenet problem ac-single-d_2_doe-int-ex-5-2-1 from the 5.2 Exercises assignment. Compare the affected Exercise within Exercises view with a working Preview Activity and investigate the internal scroll behavior. Done means the complete randomized problem and the student's attempts are visible without being cut off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100