You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example 9 in the spec https://www.w3.org/TR/css-anchor-position/#fallback-automatic shows off a "feature" that's super confusing to understand. The code doesn't make sense when you look at it. I understand @xiaochengh's suggestion of having specifying a fallback strategy, but having an implied @try blocks generated as "mirror images" of an existing try block because it happens to have an auto keyword in one particularly magic place is too much magic.
The text was updated successfully, but these errors were encountered:
We've also addressed that in #9196's resolution: we'll get rid of auto and auto-same completely and use a standalone property to generate auto fallbacks.
So I don't think we have any work to do in this issue. Can we close it?
Example 9 in the spec https://www.w3.org/TR/css-anchor-position/#fallback-automatic shows off a "feature" that's super confusing to understand. The code doesn't make sense when you look at it. I understand @xiaochengh's suggestion of having specifying a fallback strategy, but having an implied
@try
blocks generated as "mirror images" of an existing try block because it happens to have anauto
keyword in one particularly magic place is too much magic.The text was updated successfully, but these errors were encountered: