Re: [csswg-drafts] [css-scoping] Handling global name-defining constructs in shadow trees

I chose the current behavior for bare keywords to match what I thought I remembered browser behavior was, or at least Chrome's. Per #715, tho, it looks like Safari does the opposite, and treats @keyframes as local and references to it as referring to the local definition?

If we have to swap the bare keyword to be the local version, that's fine.

GitHub Notification of comment by tabatkins
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 20 February 2018 22:32:50 UTC