Re: [csswg-drafts] [web-animations-2] Should AnimationTrigger properties be readonly? (#11918)

The CSS Working Group just discussed `[web-animations-2] Should AnimationTrigger properties be readonly?`, and agreed to the following:

* `RESOLVED: Make Animation Trigger related things readonly`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> flackr: If we make the objects you get from JS for AnimationTrigger writeable, then it requires introducing complexity of knowing when to take changed values from style vs when author has overwritten and need to take that.<br>
&lt;fantasai> flackr: So proposal is to make them readonly<br>
&lt;fantasai> flackr: This way if you get a CSS trigger, we will always track updates to style<br>
&lt;fantasai> flackr: and don't need to track whether developer has changed behavior through JS object<br>
&lt;fantasai> flackr: Follow conventions for modifications to animations<br>
&lt;kbabbitt> +1<br>
&lt;ydaniv> SGTM<br>
&lt;fantasai> astearns: Seeing agreement in the issue. Anyone with concerns?<br>
&lt;TabAtkins> +1<br>
&lt;fantasai> astearns: Proposed to make these properties readonly<br>
&lt;fantasai> flackr: applies to class of trigger-related things<br>
&lt;fantasai> RESOLVED: Make Animation Trigger related things readonly<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11918#issuecomment-3160849568 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 August 2025 16:38:14 UTC