- From: Mason Freed <notifications@github.com>
- Date: Mon, 13 May 2024 16:05:27 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 13 May 2024 23:05:31 UTC
> So now that it's shipping and Google will push back on changes Our position remains the same, and is described in the [blink intent thread](https://groups.google.com/a/chromium.org/g/blink-dev/c/jGTYNuidPRs/m/rxMsvF0UAQAJ): > I'd just like to reiterate that we are open to making well-justified changes to the API shape over the next few months, as concerns arise. I think that the fact that we're shipping this API makes us **more** (not less) likely to **a)** surface the need for these changes, and **b)** prioritize them appropriately. @fantasai beat me to posting it here, but yes we now have a very detailed and up to date blog post about this feature: https://developer.chrome.com/blog/anchor-positioning-api We'd love to hear your thoughts. I just noticed that `anchor-scope` isn't mentioned there (anchor pos is a large feature!!) but as mentioned before, Chrome also hasn't shipped that particular property. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/848#issuecomment-2108948903 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/848/2108948903@github.com>
Received on Monday, 13 May 2024 23:05:31 UTC