home.social

#popoverapi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #popoverapi, 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 case you are wondering why I’m relatively silent in 2025 (especially compared to last year), no reason.

    At the moment I’m still having “fun” with the Popover API, I’ve just filed a Firefox issue:
    cssence.com/2025/popover-shift

    #WebDev #PopoverAPI #Firefox

  3. In case you are wondering why I’m relatively silent in 2025 (especially compared to last year), no reason.

    At the moment I’m still having “fun” with the Popover API, I’ve just filed a Firefox issue:
    cssence.com/2025/popover-shift

    #WebDev #PopoverAPI #Firefox

  4. In case you are wondering why I’m relatively silent in 2025 (especially compared to last year), no reason.

    At the moment I’m still having “fun” with the Popover API, I’ve just filed a Firefox issue:
    cssence.com/2025/popover-shift

    #WebDev #PopoverAPI #Firefox

  5. In case you are wondering why I’m relatively silent in 2025 (especially compared to last year), no reason.

    At the moment I’m still having “fun” with the Popover API, I’ve just filed a Firefox issue:
    cssence.com/2025/popover-shift

  6. In case you are wondering why I’m relatively silent in 2025 (especially compared to last year), no reason.

    At the moment I’m still having “fun” with the Popover API, I’ve just filed a Firefox issue:
    cssence.com/2025/popover-shift

    #WebDev #PopoverAPI #Firefox

  7. The popover API has been added just recently as Baseline 2024 for all major browsers.
    So you don't have to write all the tricky code for open/close mechanism and accessibility yourself.

    Check it out: web.dev/blog/popover-api

    #webdev #JavaScript #HTML #CSS #PopoverAPI #programming

  8. The popover API has been added just recently as Baseline 2024 for all major browsers.
    So you don't have to write all the tricky code for open/close mechanism and accessibility yourself.

    Check it out: web.dev/blog/popover-api

    #webdev #JavaScript #HTML #CSS #PopoverAPI #programming

  9. The popover API has been added just recently as Baseline 2024 for all major browsers.
    So you don't have to write all the tricky code for open/close mechanism and accessibility yourself.

    Check it out: web.dev/blog/popover-api

    #webdev #JavaScript #HTML #CSS #PopoverAPI #programming

  10. The popover API has been added just recently as Baseline 2024 for all major browsers.
    So you don't have to write all the tricky code for open/close mechanism and accessibility yourself.

    Check it out: web.dev/blog/popover-api

    #webdev #JavaScript #HTML #CSS #PopoverAPI #programming

  11. The popover API has been added just recently as Baseline 2024 for all major browsers.
    So you don't have to write all the tricky code for open/close mechanism and accessibility yourself.

    Check it out: web.dev/blog/popover-api

    #webdev #JavaScript #HTML #CSS #PopoverAPI #programming

  12. お、、おおおおお!!!
    やっぱり!特定の要素の中の子要素でも popover API を使うと、その親要素を飛び出せる(ドキュメントのルートの外に特別なレイヤーに配置できる)のか!! :tony_wee:

    #html #WebDev #popoverAPI

  13. お、、おおおおお!!!
    やっぱり!特定の要素の中の子要素でも popover API を使うと、その親要素を飛び出せる(ドキュメントのルートの外に特別なレイヤーに配置できる)のか!! :tony_wee:

    #html #WebDev #popoverAPI

  14. お、、おおおおお!!!
    やっぱり!特定の要素の中の子要素でも popover API を使うと、その親要素を飛び出せる(ドキュメントのルートの外に特別なレイヤーに配置できる)のか!! :tony_wee:

    #html #WebDev #popoverAPI

  15. お、、おおおおお!!!
    やっぱり!特定の要素の中の子要素でも popover API を使うと、その親要素を飛び出せる(ドキュメントのルートの外に特別なレイヤーに配置できる)のか!! :tony_wee:

    #html #WebDev #popoverAPI

  16. お、、おおおおお!!!
    やっぱり!特定の要素の中の子要素でも popover API を使うと、その親要素を飛び出せる(ドキュメントのルートの外に特別なレイヤーに配置できる)のか!! :tony_wee:

    #html #WebDev #popoverAPI

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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