- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Apr 2024 09:32:04 +0000
- To: public-css-archive@w3.org
@LeaVerou Oh. I thought the point of the resolution was to focus the discussion and hopefully converge on something. Unfortunately I can't make a move on `@nest` until this issue is resolved. I will likely not be able to ship a breaking change with the intent to break it again later, especially when there's no consensus on what the follow-up change would be. > It is far, far easier to change the details of that than to change the current behavior of nesting later. The specific changes we're discussing here can not necessarily be made later at all. It is sometimes very hard to understand the risk of changing CSSOM APIs. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10234#issuecomment-2068928760 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 April 2024 09:32:05 UTC