Release Notes - Version 1.0.0-20260814

New in this release

• Preferences ( menu Edit -> Preferences… ). Sets what a newly created element, text frame or page is given: fill and stroke colour with their tints, stroke weight, and the page size and type. Preferences are kept per browser and survive opening a document; they never change anything a document already contains.
• File -> New now creates a document, and takes its page size, type and colour from the Page tab of the preferences.
• Fixed: on a page that supplies its own markup rather than letting the bundle generate the editor chrome, the fly-out palettes on the toolbar buttons — stroke, opacity/blend, text alignment, columns, drop cap — did not appear. They were being positioned just above the top of the window, so they opened off-screen. Reported by an integrator; only host pages of that shape were affected, and the generated chrome and the viewer were not.
• Undo fix: clicking an element used to record an undo step even though nothing had moved. Pressing undo afterwards then either did nothing and logged an error, or — worse — restored the page as it was at some unrelated earlier edit, discarding everything done since. In the viewer this happened on every interaction with an element, because frames there cannot be moved at all. Selecting something now records nothing, and undo goes back to the last real change.
• Adding, duplicating and deleting a page can now be undone. These changed the document without recording an undo step at all, so there was nothing to go back to — delete a page and it was gone.
• Switching page no longer clears the undo history. Editing a page, looking at another one and coming back left nothing to undo; the history now survives, and undo still reverts the page the edit was made on even while you are looking at a different one.
• New event for embedders: typograph_document_changed, fired whenever the document's content changes — a user edit, an undo, or a redo. event.detail carries { reason: 'edit' | 'undo' | 'redo' }. Both the editor and the viewer fire it, so one listener covers either product. Opening a document is deliberately not a change. Intended for driving an auto-save, a "modified" indicator, or an enabled save button. See the Document Events page in the documentation, which also notes the one case it does not report: changes made through host API calls that bypass undo, such as set_userdata().
• Companion to the above for embedders who would rather ask than listen: document.is_changed() answers whether the document differs from the last saved or loaded state, and document.mark_saved() records a successful save. Undoing back to the saved state reads as unchanged again, which a count of edits could never report. Use the event to drive an auto-save and is_changed() for a Save button, a "modified" marker or a "discard changes?" prompt.

Typograph developers notes

• New documentation page: Document Events.
• The Element Events page has been corrected in three places, all of which described the engine as it used to be:
  • it stated that every custom event passed through a shared throttle of five per second. Throttling has been opt-in since TYP-592 and nothing opts in, so a reader would have assumed the new change event was coalesced for them. It is not;
  • typograph_pageelement_deselected was listed as reserved / never fired. It has been dispatched since TYP-592;
  • typograph_text_edit_start / _change / _stop were listed as reserved. They were deleted in TYP-592 and no longer exist — use typograph_edit_done and typograph_textInput. typograph_pageelement_created and _deleted really are still not dispatched, and the page now says why: the engine cannot yet tell a user creating an element from one appearing because a document was opened, an undo ran, or a spread was duplicated.