On Tue, Apr 19, 2022 at 10:32 AM Mike Taylor <miketa...@chromium.org> wrote:
> Specification https://tabatkins.github.io/css-toggle/ > > A question came up in Security & Privacy review today. Can you clarify > what "persistent state" means in > https://tabatkins.github.io/css-toggle/#toggles? I suspect we're not > re-inventing cookies in CSS here, but can you help me understand what that > means in the context of CSS toggles? Does it just mean that once set, other > CSS properties can't influence the state? Or "persistent state (for the > lifetime of the page)"? > I think what the "persistent state" bit is saying is that once a toggle is created on an element (by the toggle-root property), the toggle doesn't go away even if the toggle-root property changes. It's definitely not something like cookies, since the state doesn't get transferred to other pages or to fresh loads of the same page. (I haven't thought much about the question yet, but it's *possible* that it might be something like form control state that gets persisted specially during back/forward navigation even when the entire page isn't cached. I suspect that may cause more problems than it fixes, though.) -David -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG0MU3idUeNMQB4L5C3sZt7T1fpPokoHUz5GT%3DpVDwC_6atR-w%40mail.gmail.com.
