Toronto election pages: ward silence, the split panel, and the survey link

[mikaalnaik]

Four commits across the Toronto election pages. The first is the original subject of this PR; the rest were added after.

---

1. A ward where nobody answered says so

A ward where not one candidate answered printed all thirty-odd questions with nobody's answers on them. The argument was that a ward of non-respondents still deserved to see what it was they did not answer. Eight of Toronto's twenty-five wards are in that state, and what it gave them was nine screens of questions burying the one thing the section had to report.

The questions are not the ward's news; the silence is.

• The questionnaire body is a single statement — "No candidate has responded" — with How the whole city answered beneath it for a reader who wants the questions with answers on them.
• The lead-in "Nobody in this ward has answered yet. These are the questions we asked." is gone; its second half was a promise the page no longer keeps. The "no one has registered" case keeps its own sentence.
• The roster above is labelled "On the ballot" rather than "Also on the ballot, yet to answer our questionnaire" — "also" needs something to be also to.

Wards with answers are untouched. QuestionnaireOutline was rendered from this one branch and goes with it, along with the shape plumbing that fed it (surveyShape through WardDetail, shape off rosterSurvey). questionnaireShape stays — /issues, /mayor and the survey results still call it.

2. The split panel opens on its answer

On /issues, the panel of names behind a pie slice opened on a bare count — "38 candidates" — and nothing else. Which thirty-eight, of the three or four splits on the card, was something the reader had to carry from the row they clicked, and on a pie they may not have come from a row at all: a wedge of colour carries no wording.

The answer the candidates were shown now heads the panel, dotted in the slice's own colour and set the way the legend sets it, with the count under it as the caption. The heading sits outside the scroller, so it stays put while the names move under it.

3. And it is sized to hold the names

The cap was 14rem — about ten names, against a largest slice of fifty-five in the Toronto field, so the rest sat behind a scrollbar inside an overlay. Three changes got the names on screen:

• The ballot line comes off each name. "· Ward 17" after every name was longer than most of the names it trailed and set the width of every column, for a fact the reader is not in the panel for. The ward pages are where a name is matched to a ballot.
• Height is bought with columns, not a taller box: ~110px a column, two or three to a card, so a fifty-five-name slice is nineteen rows rather than twenty-eight. The breakpoints are the panel's own width, since these cards run one, two and three to a row.
• The panel is exactly the card's width — the figure sits inside the card's padding, so the panel gives that padding back and lands flush inside the card's border. A version that broke out past the card was shorter still and looked wrong: wider than the card it belongs to, it reads as something arriving over the page rather than coming out of the card, and it cannot be caught in a screenshot of that card.

The question heading drops to 1.25rem with it — ninety characters over a card three to a row took three and four lines at 1.45rem, and the page read as a stack of headlines with charts attached.

4. The Toronto compare card links the survey

The landing card sold a signup because the questions were written and the answers were not in. They are now, so it links SURVEY_PATH and the stand-in modal copy comes off.

---

Testing

tsc --noEmit and npm run lint clean (4 pre-existing warnings, 0 errors). Against the local dev server: /toronto, /toronto/vote/2026/issues, and wards 1 and 2 all 200. Wards 2, 3, 5, 6 render the new empty state; wards 1 and 13 still render the full answer grid; /mayor and /issues unchanged by the ward work.

No browser was available in the session, so this is DOM-level verification rather than a look at the rendered pages. Two things want an eyeball before merge: a quiet ward, and the panel open on the fifty-five-name slice on /issues.

🤖 Generated with Claude Code