| Comment: | landings: no headline where the author wrote none
A record only HAS a headline when its author wrote one — a subject line, a blank line, then the body. Written without that, the whole message is the title, and clipping it to 72 invented a headline the author never wrote, then ended it in an ellipsis that says data is hidden when the same words are in full directly below. The visible heading now goes for that shape: the chips and the message carry the record, and the sr-only h1 keeps the page named. A record that does have a subject line still shows it. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
2dccc0cb5fe994c40bcd68a1b96f1bde |
| User & Date: | dmestas on 2026-08-27 14:12:42.097 |
| Other Links: | manifest | tags |
|
2026-08-27
| ||
| 21:13 | land perm-1 check-in: cff61f323b user: dmestas tags: trunk | |
| 14:12 |
landings: no headline where the author wrote none
A record only HAS a headline when its author wrote one — a subject line, a blank line, then the body. Written without that, the whole message is the title, and clipping it to 72 invented a headline the author never wrote, then ended it in an ellipsis that says data is hidden when the same words are in full directly below. The visible heading now goes for that shape: the chips and the message carry the record, and the sr-only h1 keeps the page named. A record that does have a subject line still shows it. check-in: 2dccc0cb5f user: dmestas tags: trunk | |
| 13:18 |
landings: the record shows its whole message, and the heading shows no markup
Two faults from one cause. A message written with no blank line has no prose under the header at all — zit put the whole thing in the title card. So clipping the heading dropped 290 of 362 characters with nowhere left to read them, and the record rendered no description. The opener now falls back to the title, rendered like any other body, which is also the only way its Markdown ever reaches a reader. The heading drops the marks instead: an h1 is plain text, so *emphasis* arrived as literal asterisks and read as a rendering bug. Asterisks and backticks only — _x_ in prose and my_file_name in a path are the same three characters, and mangling every identifier to italicise a rare one is the worse trade. check-in: db743a90a0 user: dmestas tags: trunk | |