The server locked the scores. The judge’s screen still said “Update.”

Description and use

After publication, Glassbox’s UI still allowed judges to edit scores, causing confusion. A lock notice was added, disabling fields and removing the Update button, aligning the interface with the finalized state.

Problem

Judges could edit scores after publication because the UI still allowed it, even though the backend had already rejected changes.

Outcome

The UI change prevented judges from attempting to edit finalized scores, aligning the front‑end with the back‑end’s state transition and improving the judging workflow’s clarity.

Workflow

• Open the judge’s score page and confirm that the Update button is enabled.
• Publish the event via the organizer API.
• Re‑open the judge’s score page.
• Verify that a locked notice appears, the score fieldset is disabled, and the Update/recusal buttons are absent.
• Confirm that any attempt to submit a score is rejected by the backend.
• Run the regression test to ensure the rendered HTML reflects the locked state.

Evidence

A judge could spend time revising a comment, press Update, and discover that the action had already become impossible.

Source

The fix derives the score form’s locked state from the event phase. Once published, the page displays a locked notice, disables the score fields, and removes the save and recusal actions.

Source

The backend remains responsible for rejecting forbidden writes.

Source

The regression test follows the transition: Open an assigned score page as a judge and confirm that saving is available. Publish the event through the organizer API. Fetch the judge page again. Check for the locked notice and disabled fieldset. Check that save and recusal controls are gone.

Source