Anchor positioning allows a positioned element to size and position itself relative to one or more "anchor elements" elsewhere on the page, possibly constrained by the container or viewport. A typical use case is to "pin" a popup to the button that opens it.
When building interactive components or applications, authors frequently want to leverage UI elements that can render in a "top-layer", and wish to "pin" or "anchor" such top-layer UI to a point on another element, referred to here as an "anchor element". How the top-layer UI is positioned with respect to its anchor element is further influenced or constrained by the edges of the container. CSS Anchor Positioning provides native support for such use cases.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No.
In addition to the standard CSS & Layout support, DevTools should be able to show which fallback positioning an anchor-positioned element is using.
No milestones specified