home.social

#openui — Public Fediverse posts

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

  1. Open UI, a W3C Community Group, aims to establish a standard process for developing high-quality UI controls suitable for addition to the open web platform.

    open-ui.org/ h/t @adactio

    Not to be confused with openui.com/, an AI design service.

#w3c #OpenWeb #WebStandards #openUI

  2. Open UI, a W3C Community Group, aims to establish a standard process for developing high-quality UI controls suitable for addition to the open web platform. open-ui.org h/t @[email protected] Not to be confused with www.openui.com, an AI design service. #w3c #OpenWeb #WebStandards #openUI

    Home | Open UI

  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

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