- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Aug 2022 21:08:16 +0000
- To: public-css-archive@w3.org
Let me try to clarify the details for the explicit proposal: * Each keyframe declaration in the UA stylesheet will have a CSS function to scope it: ```css @keyframes ua(fade-in) { from { opacity: 0; } } div { animation: ua(fade-in); } ``` > I'd be fine with reserving the single-dash set of names (already used for vendor prefixes) I think you meant -fade-in instead of ua(fade-in) but turns out that a [single dash is valid syntax](https://jsbin.com/motulamesa/edit?html,output) for custom idents today. I thought we could do --fade-in but double dash is for custom properties. Open to other suggestions though. * If the same keyframe declaration is used in any stylesheet other than user-agent origin it will rejected at parsing time. This includes both @keyframe and when applying the keyframe to the animation-name property. I'm flexible on the last one though. The limitation avoids the keyframes being used for cases other than what the UA generated them for. I'm ok with this option too. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7560#issuecomment-1232170110 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 August 2022 21:08:17 UTC