3 ms·

This is very clever, and it’s nice that it’s fully accessible and requires no JS. However, looking at that final CSS just makes me wish that we added new inter

This is very clever, and it’s nice that it’s fully accessible and requires no JS. However, looking at that final CSS just makes me wish that we added new interface elements to HTML far more often. Folks run rings around themselves to implement things that have been in any desktop UI toolkit worth its salt since the 90s.

mhitza 4y ago
There are so many ARIA guidelines on implementing alerts, modals, comboboxes and anything in between. Yet most don't have any equivalent presentational or functional counterparts in the existing browsers. Writing this comment, just as I'm writing an accessible combobox in a project where I'm not using any frontend framework and minimal JavaScript.
- eurasiantiger 4y ago
  Let’s extend this thought a bit deeper. Why are we consuming different brands of fixed-form content through bespoke interfaces? Why is there no standard for navigation of any type of content? I really hope RSS is coming back in force.
marcosdumay 4y ago
On this case, the functionality is there right on the HTML, and the CSS is just customizing the appearance to make it look like a desktop widget. This is not an issue of lack of HTML support. In fact, this is exactly what CSS is for.
Bilal_io 4y ago
Perhaps the the Open UI unitiative is a good place to create a proposal. https://open-ui.org https://open-ui.org
- toastal 4y ago
  They are really bad at first impressions. Do they not think about their own code? Literally the first thing I see when I visit the page is a misused <blockquote> > The blockquote element represents a section that is quoted from another source. — the W3 blocquote specification Their copy isn’t quoted from another source, it’s a janky admonition writers of Markdown use when their tools, Markdown, don’t support the semantics they mean. <blockquote> does not mean “put this in a box”. Click the navigation and the first things you see are links to GitHub and Discord, two very not open platforms—which should go against the philosophy of the project if they want open standards.

mhitza 4y ago

There are so many ARIA guidelines on implementing alerts, modals, comboboxes and anything in between. Yet most don't have any equivalent presentational or functional counterparts in the existing browsers. Writing this comment, just as I'm writing an accessible combobox in a project where I'm not using any frontend framework and minimal JavaScript.

eurasiantiger 4y ago
Let’s extend this thought a bit deeper. Why are we consuming different brands of fixed-form content through bespoke interfaces? Why is there no standard for navigation of any type of content? I really hope RSS is coming back in force.

marcosdumay 4y ago

On this case, the functionality is there right on the HTML, and the CSS is just customizing the appearance to make it look like a desktop widget. This is not an issue of lack of HTML support. In fact, this is exactly what CSS is for.

Bilal_io 4y ago

Perhaps the the Open UI unitiative is a good place to create a proposal. https://open-ui.org https://open-ui.org

toastal 4y ago
They are really bad at first impressions. Do they not think about their own code? Literally the first thing I see when I visit the page is a misused <blockquote> > The blockquote element represents a section that is quoted from another source. — the W3 blocquote specification Their copy isn’t quoted from another source, it’s a janky admonition writers of Markdown use when their tools, Markdown, don’t support the semantics they mean. <blockquote> does not mean “put this in a box”. Click the navigation and the first things you see are links to GitHub and Discord, two very not open platforms—which should go against the philosophy of the project if they want open standards.