grid: pin the refused color spec at the OSC dispatch layer #216
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis!216
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-201-refused-color-spec"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #201.
Adds two tests in
felis-grid'sosc_dispatch/tests.rsthat pin the documented dispatch-level behavior: a colorimetric (CIELab,TekHVC,CIEXYZ,CIELuv) orrgbi:spec through OSC 4, OSC 5 and OSC 10-12 leaves the previously set slot or override in place and emits no reply. The palette test reads the slot back through the?query path so the preserved value is observed on the wire, not just in the override map.The OSC 13-19 half of the issue was already pinned by
tolerated_osc_families_leave_no_state_and_no_reply(landed in23e50f22), so no new test for it.cargo test -p felis-grid --lib refused_specandcargo clippy -p felis-grid --all-targets -D warningspass.09e41a60527d003722467d00372246e6ac50a0cd