GraphiteEditor/Graphite

Hiding layer on new document can lead to incorrect saved state

Open

#3381 opened on Nov 14, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (25,662 stars) (1,176 forks)batch import
Good First IssuePaper Cut

Description

Steps to reproduce

open demo artwork (saved)

hide one layer in the node graph (saved !)

unhide (unsaved !)

hide (saved !)

Contributor guide

Tech stack
rust
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RustLayer visibility logic
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the save/load state logic for layer visibility. The bug triggers when hiding a layer on a new document; the saved state becomes inconsistent after unhide/hide cycle. Look in the document serialization code (likely in src/document/ or similar) to understand how visibility flags are stored and restored. Check if there's a missing or incorrect update to the 'is saved' flag after layer visibility changes. Reproduce the steps in the issue and add debugging to trace the state changes.