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

说明与用途

发布后，Glassbox 的 UI 仍允许评委编辑分数，导致混淆。添加了锁定提示，禁用字段并移除更新按钮，使界面与最终状态保持一致。

问题

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

结果

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.

工作流

• 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.

证据

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

来源

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.

来源

The backend remains responsible for rejecting forbidden writes.

来源

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.

来源