[3.0] Theme split (wave 4, part 10) — make the report picker a list of labelled choices - #9404
Merged
live627 merged 1 commit intoAug 9, 2026
Conversation
template_report_type() built its list of reports as a dl.settings, which is the label-and-control pattern used for settings forms. It does not fit here: the <dt> held the report's description rather than its label, and the <dd> held the radio together with the label it belongs to. So the definition list paired every report's description with the report after it, and the actual label was inside the definition rather than the term. Each report is now one <label> wrapping its radio, title and description, which is the shape template_maintain_options() already uses for the forum maintenance picker, and the .option_form rules that came with it lay this out with no new CSS. The form still posts, and still carries the session token. Signed-off-by: Mathias Papenbrock <mathiaspapealbert@hotmail.com> Signed-off-by: albertlast <mathiaspapealbert@hotmail.com>
Closed
live627
approved these changes
Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
template_report_type()built the list of reports as adl.settings, which is the label-and-control pattern used for settings forms. It does not fit a list of choices, and it was assembled the wrong way round:So the
<dt>carried the description and the<dd>carried the radio together with the label that belongs to it. Read as a definition list, each report's description is the term for the report that follows, and the title — the thing that names the choice — sits inside the definition. A report with no description drops its<dt>and shifts everything after it.Each report is now one
<label>wrapping its radio, title and description:This is the shape
template_maintain_options()already uses for the forum maintenance picker, landed in #9333, and the.option_formrules that came with it lay it out with no new CSS. A missing description now just leaves the<p>out of that one label.The
id="rt_…"/for="rt_…"pairing goes with it — the input is inside its label, so the association no longer needs an id, and nothing else referenced those ids.What I did not change
The #7933 branch also turns this into a
method="get"form with hiddenactionandareafields and drops the session token. That is a separate decision about the request, not about the markup, so this keeps the POST and the token exactly as they were.Checked
Rendered on the running forum, then submitted: Admin → Reports still produces "Reports - Boards" with the board list in it.
Part of the #7933 split. Numbering restarts each wave.
Issues References (Fixes|Related|Closes)
Related to #7933