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. Oh OpenUI, your responsive design is broken. 😢

    #openui #ai

  4. 🚀A new HTML feature, interestfor, allows for hover-triggered popovers. But how do they work on touch? The article shows different solutions for making them accessible on touch devices, and my thoughts on them. Share your thoughts! #HTML #webdev #accessibility #openui utilitybend.com/blog/html-po...

    HTML popovers shown on interes...

  5. OH: “there are people who put 60,000 <option>s in a select, that's why we now have tests for that“ #OpenUI

  6. Open-UI: 🎨 Let's create yet another "open" standard that no one will read, everyone will ignore, and #GitHub will pretend is the next big thing. 🤖 Meanwhile, AI is busy "writing better code" and solving world hunger... or was it world bugs? 🙄
    github.com/openui/open-ui #OpenUI #OpenStandards #AIandCode #TechHumor #HackerNews #ngated

  7. #til about github.com/aws-samples/bedrock and now I can finally try other models without more subscriptions. Got it to work with #openui too but found out that by doing so, I cannot connect it to #openai anymore. I wonder if there is a gateway that connects to *everything* #ai

  8. The fixation at last week on AI buried the much more interesting talk by @Una on The Latest in Web UI, which highlighted the ton of interesting features arriving in and . youtube.com/watch?v=_-6LgEjEyzE

    I wish the other browser vendors didn't rely so heavily on Google to get the word out. They all do so much work to make these features possible, as do the standards committees, the group, and @igalia, and they all deserve to get more credit.

  9. OH: “you could throw lots of things in a `<select>` that never show up in the DOM tree”

    #OpenUI

  10. The #OpenUI @w3c group has a some great proposals on how to extend #HTML elements to support better styling and flexibility. This could eliminate a lot of #Javascript UI elements.
    Some of them are already available as experimental browser features such as <selectmenu> or the popover attribute

    open-ui.org/

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

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

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

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

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