@@ -858,15 +858,6 @@ specify a <dfn>position fallback list</dfn>,
858858where each entry consists of the properties specified by each ''@try'' ,
859859in order.
860860
861- Issue: If you have a bunch of elements
862- that all use the same positioning and fallback,
863- just relative to different anchor elements
864- (like a bunch of tooltips),
865- there's no way to have them share @position-fallback rules;
866- they each need a unique set.
867- This sucks!
868- Should figure out some way to address this.
869-
870861Issue: Would be useful to be able to detect
871862when your anchor(s) are fully off-screen
872863and suppress your display entirely.
@@ -876,6 +867,21 @@ don't want to just hover over arbitrary parts of the page
876867because their anchor happens to have that position
877868relative to the scrollport.
878869
870+ Note: If multiple elements using different anchors
871+ want to use the same fallback positioning,
872+ just relative to their own anchor elements,
873+ omit the <<anchor-element>> in ''anchor()''
874+ and specify each element's anchor in 'anchor-default' instead.
875+
876+ Note: The most common types of fallback positioning
877+ (putting the positioned element on one side of the anchor normally,
878+ but flipping to the opposite side if needed)
879+ can be done automatically,
880+ without using ''@position-fallback'' at all,
881+ by using ''anchor()/auto'' or ''anchor()/auto-side''
882+ side values in the ''anchor()'' function.
883+
884+
879885Applying Position Fallback {#fallback-apply}
880886--------------------------
881887
0 commit comments