An alternative to Ubuntu will emerge when competent people have reached the limit of their patience. Personally, I am more and more tempted by Debian. Ubuntu has become a dangerous tool.
We must, one day, realize that .NET will disappear when Microsoft stops supporting it. All work done with this framework is only a prison for future developers. This must end.
First of all, what does it have to do with this particular library?
Second, get a grip, .NET is open source for a while, it's getting more popular again, JetBrains entered the stage with a very competetive IDE, it's easier than ever to use .NET via CLI, days of having to use Visual Studio, or any Microsoft product really, are long gone. I don't like Microsoft either but noone's forcing you to use any of their products anymore.
There are different languages. The jokes are symptomatic of the differences. I'm not Indian but English is laughable for many good reasons. Without damage...
I do this too if I’m trying to play JS payload golf and the stakes are low for users, but I always feel guilty because I know it harms accessibility. JS is actually required to make an expandable/collapsible menu accessible, even if your clever pure-CSS solution seems bulletproof. It’s a shame, there really should be native controls for this kind of thing that don’t require arbitrary executable code.
This is precisely what <details> <summary> is for. No javascript required. It gives the correct semantics for assistive technology, correct interactions with the keyboard, focusability, etc. I recommend you use it over the old checkbox hacks or javascripts.
Yes! This example is a control that toggles the visibility of part of the page. It is neither a link nor a button
And, you know, if you think about this from an assistive technology point of view, does a screenreader user actually need to worry about interacting with a control to make something visible? Isn't it better from their point of view to skip the interaction entirely and just put the list of theme options semantically under a navigable page heading?
A lot of screen reader users are partially blind, in the process of losing their site, or sharing a screen with someone else. So it’s better to give both experiences at the same time
It’s kinda cool but apparently you can’t really be accessible AND script-free because they say you should change some aria attributes and potentially some focus when you open modals like menu and dropdowns.
A #menu href coupled with :target style is technically more accessible because the focus naturally shifts to it. Then the exit button should point to #menu-toggle so that closing the menu brings the focus back to the origin.
I've been using Kubuntu for a few years. There are no snaps, and not too many opinions, everything is option. I only use LTS to avoid breakage. I also avoid Neon to avoid said breakage and the packages are too exotic for my need. Kubuntu LTS is good on its own. Good luck on your journey.
As a Quebecer, I will allow myself to highlight the intention behind this surprising proposal. Quebec's French-speaking artistic community is very rich and very lively. The musical tastes of Quebecers are also very diverse, in both English and French. Only, from a commercial point of view, English-speaking music enjoys a very large exposure and it is very easy to forget that other music also exists. Canada, from a constitutional point of view, officially recognizes 2 languages: English and French. Laws impose on the broadcaster a certain percentage of content in these 2 languages. However, French does not benefit from the strength of attraction of English on the North American continent. The Quebec government has therefore decided to do its part to increase the visibility of French-language music in Quebec, more specifically, Quebec French-language music. It is an action of resilience, one among many others that we feel obliged to do to avoid disappearing like all the other French-speaking populations of America.
