home.social

#anchorpositioning — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #anchorpositioning, aggregated by home.social.

  1. Es freut mich so sehr, dass mit 147 meine beiden neuen Lieblings-Features unterstützt!
    und jetzt auch (gerade für ).

    In diesem Artikel gehe ich auf View Transition API ein, erwähne aber auch anfangs Popover API: site.lgk.io/blog/2025-06-01-vi

  2. In the #OpenUI discord @Una (as a follow-up to my answer to @utilitybend) asked if we could use anchor positioning to connect the #PopoverAPI popovers and their anchors (via #CSS #AnchorPositioning) and while we can (codepen.io/kizu/pen/qBJQpjm, hacky but works), I stumbled upon a usage issue and a Chrome bug.

    - I opened a CSSWG issue about using the implicit anchor elements on the nested elements somehow — github.com/w3c/csswg-drafts/is
    - I opened a Chrome bug — bugs.chromium.org/p/chromium/i

  3. In the #OpenUI discord @Una (as a follow-up to my answer to @utilitybend) asked if we could use anchor positioning to connect the #PopoverAPI popovers and their anchors (via #CSS #AnchorPositioning) and while we can (codepen.io/kizu/pen/qBJQpjm, hacky but works), I stumbled upon a usage issue and a Chrome bug.

    - I opened a CSSWG issue about using the implicit anchor elements on the nested elements somehow — github.com/w3c/csswg-drafts/is
    - I opened a Chrome bug — bugs.chromium.org/p/chromium/i

  4. In the #OpenUI discord @Una (as a follow-up to my answer to @utilitybend) asked if we could use anchor positioning to connect the #PopoverAPI popovers and their anchors (via #CSS #AnchorPositioning) and while we can (codepen.io/kizu/pen/qBJQpjm, hacky but works), I stumbled upon a usage issue and a Chrome bug.

    - I opened a CSSWG issue about using the implicit anchor elements on the nested elements somehow — github.com/w3c/csswg-drafts/is
    - I opened a Chrome bug — bugs.chromium.org/p/chromium/i

  5. In the #OpenUI discord @Una (as a follow-up to my answer to @utilitybend) asked if we could use anchor positioning to connect the #PopoverAPI popovers and their anchors (via #CSS #AnchorPositioning) and while we can (codepen.io/kizu/pen/qBJQpjm, hacky but works), I stumbled upon a usage issue and a Chrome bug.

    - I opened a CSSWG issue about using the implicit anchor elements on the nested elements somehow — github.com/w3c/csswg-drafts/is
    - I opened a Chrome bug — bugs.chromium.org/p/chromium/i

  6. In the #OpenUI discord @Una (as a follow-up to my answer to @utilitybend) asked if we could use anchor positioning to connect the #PopoverAPI popovers and their anchors (via #CSS #AnchorPositioning) and while we can (codepen.io/kizu/pen/qBJQpjm, hacky but works), I stumbled upon a usage issue and a Chrome bug.

    - I opened a CSSWG issue about using the implicit anchor elements on the nested elements somehow — github.com/w3c/csswg-drafts/is
    - I opened a Chrome bug — bugs.chromium.org/p/chromium/i