| 1 | # Table column widths through the editor |
| 2 | |
| 3 | `candidate/` is the output of `typed_and_dragged_columns_store_onenote_s_widths` in |
| 4 | `crates/canvas/tests/table_widths.rs`, editing `corpus/table-tags/native`. On "Check a |
| 5 | table" a three-by-three table is typed after the text a keystroke per revision, each |
| 6 | storing its column's fitted width with its text; on "Edit a tagged table" a native cell |
| 7 | is typed into, widening its column; on "Delete and undo" a new table's first column is |
| 8 | dragged to 96 pt, locking it, and a line long enough to reach the outline's width is |
| 9 | typed in the second. |
| 10 | |
| 11 | `cold/` is a fresh OneNote 2010 read: the typed table's columns are the widths OneNote |
| 12 | gives the same table typed in it (60.76, 37.11 and 139.09 pt), the widened native column |
| 13 | keeps its width, the dragged column stays 96 pt and locked, and the long line wraps in |
| 14 | its column at the outline's edge. `tools/test_table_widths.py` checks this without a VM. |
| 15 | Regenerate with `SNOWBOUND_TABLE_WIDTHS_EXPORT` set to a new absolute directory while |
| 16 | running the test, then cold-open it with |
| 17 | `tools/native_runner.py OUTPUT COLD --expected-pages 3 --collect-notebook --screenshots`. |