browser-compat-data
i3
browser-compat-data | i3 | |
---|---|---|
45 | 200 | |
4,793 | 9,079 | |
0.7% | 1.4% | |
10.0 | 7.6 | |
about 23 hours ago | 6 days ago | |
JSON | C | |
Creative Commons Zero v1.0 Universal | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
browser-compat-data
- Here are the 10 projects I am contributing to over the next 6 months. Share yours
-
Why Isn't the <HTML> Element 100% Supported on CanIUse.com?
> a lot of the data on the site actually comes from MDN
Eh... not really.
The feature support matrix (as linked on CanIUse) comes from the browser-compat-data repo. Here's the HTML element's source data: https://github.com/mdn/browser-compat-data/blob/main/html/el...
This doesn't contain the testing and usage info that CanIUse cites for support, though, just which browser versions included which features.
CanIUse also points to their own repo, which contains a lot of data: https://github.com/fyrd/caniuse
But I can't find an easy entry point to find where they're getting the numbers for a specific element. The data on there seems to be primarily for features.
So the more precise question is, where is CanIUse getting HTML element testing and usage numbers from? Because that seems to be the issue.
-
Starting to write CSS in 2023 will be different
The key factor for web development to stop new CSS features is cross-platform compatibility. If you want to know the compatibility data of a new feature, you can get it through platforms such as Can I Use , Browser Compat Data and Time to Stable .
-
A new home for the Project Fugu API Showcase
Yes, Mozzila’s browser-compat-data (https://github.com/mdn/browser-compat-data) is the authoritative source.
-
New Patterns for Apps
Just noting that the browser support matrix is right here: https://web.dev/patterns/advanced-apps/contacts/#:~:text=con...
It's an Eleventy widget powered by MDN's browser-compat-data: https://github.com/mdn/browser-compat-data.
-
includes() method
https://developer.mozilla.org Is your best friend, they even have an examples how to use it
- Aprender fazendo engenharia reversa nos projetos, buscando e lendo documentação, é uma boa ideia?
- front end utdannelse
-
Browser Extension with Blazor WASM - Cross-Browser Compatibility
Visit any website on https://developer.chrome.com, https://developer.mozilla.org or https://docs.microsoft.com.
-
how do i build an aesthetic website (with css) WITHOUT prior html experience?
W3Schools and MDN Web Docs are two great resources to learn about elements and all about HTML and CSS. Kevin Powell has a great YouTube channel which explains everything you search for. If you want to incline in your HTML and CSS skills pretty quickly, think of your objective, maybe even sketch it out, then search absolutely everything on Google and it will give you the answer. If not, this subreddit is always open. Bon voyage
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
https://github.com/i3/i3/issues/4353
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
What are some alternatives?
horizon-ui-chakra - Horizon UI JavaScript ⭐️ The trendiest & innovative Open Source Admin Template for Chakra UI & React!
sway - i3-compatible Wayland compositor
cppreference-doc - C++ standard library reference
awesome - awesome window manager
awesome-ada - A curated list of awesome resources related to the Ada and SPARK programming language
bspwm - A tiling window manager based on binary space partitioning
curriculum - The open curriculum for learning web development
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
postman-app-support - Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
devdocs - API Documentation Browser
tmux - tmux source code