A UX pass over the workspace, and two defects it turned up

Walking the site as a student (desktop, a phone-width screen, dark) found
these. Each is small; together they are what got in the way.

Defects:

- Opening a problem in the Bridge saved the generated Mojo over the
  exercise's own program. The workspace fills every pane's editor as it
  opens, the editor reported that as typing, and the Bridge's read-only
  Mojo pane holds the generated text. Developer then showed generated
  Mojo labeled "your edits", and the problem counted as edited. The
  value setter now marks its change as a load, the change listener
  leaves loads out, and a Bridge session refuses a Mojo edit.
- A page opened at #/#problems or #/#reference stopped about 45px past
  the heading: the fonts arrived after the place was computed. A page
  built this moment goes straight to its section and finds it again
  when the fonts are in; a page already on screen still scrolls there.

The workspace:

- With no run to step, the Run view said "Nothing to run yet." It and
  the stepper now give one reason (src/core/norun.ts): how many problems
  the stepped pane has and the first with its line, with a button to the
  line and the Problems list; or that the pane is empty.
- In the Bridge the dock starts at about a quarter of the height (it
  holds a call, a line of output, a short list), so the code and the run
  get the room. Developer keeps a third for the compiler's answer. A
  double-click on a divider returns to the area's default, not to the
  student's last position.
- The reason a pane is not in step wraps instead of ending in an
  ellipsis, and a button in the pane's head keeps its words on one line.
- A problem that does not exist keeps the site's navigation and links
  the problem list.
- Help, the theme switch and the stepper's first, back, step and last
  buttons have names a screen reader can say.

A phone-width screen:

- The toolbar is three rows in every area and on every tab (it was four
  or five): the mark, the area, help and the theme; the problem,
  Versions and Reset; the actions. About 30px more of the code shows.
  An embedded workspace keeps its own toolbar.
- The Share dialog puts each row's name above what it holds (a note had
  been squeezed to a word per line), and the Versions menu opens across
  the screen instead of running off its right edge.
- The stepper's speed label stays with its slider.

Checked by hand, in headless Chromium at 1440x900, 1366x768, 390x844 and
320x640, light and dark: each state above before and after; the editor
has line numbers and highlighting; the stepper steps; embeds
(playground, trace, Developer) are unchanged; 31 smoke scenarios clean
but the ones that err on purpose.
This commit is contained in:
alexm committed 2026-11-13 06:27:00 -05:00
1 parent eb77cf6902
commit 3c5097d9d0
14 files changed
+302 -39

No files matched your search

+9
View File
@@ -14,6 +14,11 @@ No version has been tagged yet. What programs mean is pplus-core's, and its chan
- The copy says what the site holds and no more: what runs in the browser and what does not, that the Hardware area is a model machine, and what "verified" means.
- A shared link never saves over the reader's own work on the same problem.
- Below 700px a workspace shows one part at a time; every page has a main landmark and a heading, and the contrast findings are fixed.
- With no run to step, the Run view and the stepper say why: how many problems the pane has and the first one with its line (and a button to the Problems list), or that the pane is empty. It said "Nothing to run yet."
- In the Bridge the dock starts at about a quarter of the height, not a third, so the code and the run get the room; Developer keeps a third for the compiler's answer. A double-click on a divider returns it to the area's default.
- A phone-width toolbar is three rows in every area (it was four or five): about 30px more of the code on screen. The stepper's speed label stays with its slider.
- A problem that does not exist keeps the site's navigation and links the problem list.
- The icon-only buttons (help, the theme, the stepper's first, back, step and last) have names a screen reader can say.
- The Quarto extension's syntax definitions state their license as Apache-2.0 (they said MIT), and `THIRD_PARTY.md` says that the stylesheets and syntax definitions that came from the course are under this repository's copyright and license.
- The deploy job is light: it runs the site's tests and core's `mojo-status-strict` at the pinned commit, then publishes. It no longer runs core's own tests (15 to 22 minutes on the deploy server, where they also failed for want of a C compiler and for the server's speed, so the site was not published). Core's tests and everything that builds Mojo are core's gate, on a runner of its own; run `pixi run core-test` before moving the pointer. `docs/deploy.md` and the workflow describe the runner as it is, a new container for every job, not a host shell.
@@ -39,6 +44,10 @@ No version has been tagged yet. What programs mean is pplus-core's, and its chan
- With `pplus-strict: true`, a program with `EXPECT` lines that does not run at all stops the render; it was only a warning.
- `quarto/README.md` is corrected against the extension: `follow` belongs to the stepper only, the defaults and limits of `height` and `max`, what a non-HTML format gets, what `check-pages` runs, and what `quarto-export` writes.
- From core: brackets that each hold a long chain are one `too-deep` error in the pseudo pane; they ended in the engine's own stack error.
- Opening a problem in the Bridge saved the generated Mojo over the exercise's own program, so the Developer area then showed the generated text labeled "your edits" and the problem counted as edited. Text the app loads into an editor is no longer reported as typing, and a Bridge session refuses a Mojo edit.
- A page opened at `#/#problems` or `#/#reference` stopped about 45px past the section's heading (the fonts arrived after the place was computed); it now goes straight to the section and finds it again when the fonts are in.
- On a phone-width screen the Share dialog squeezed a note into a column one word wide, and the Versions menu ran off the right edge.
- The reason a pane is not in step was cut off with an ellipsis; it wraps.
## [0.1.0] - 2026-10-06