aria-practices
gecko-dev
| aria-practices | gecko-dev | |
|---|---|---|
| 4 | 78 | |
| 1,160 | 3,142 | |
| 1.0% | 1.7% | |
| 8.0 | 10.0 | |
| about 12 hours ago | 5 days ago | |
| HTML | ||
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
aria-practices
-
Here are the 10 projects I am contributing to over the next 6 months. Share yours
W3C Aria Practices
-
React Arborist – A full-featured tree component for React
I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility?
W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are:
https://w3c.github.io/aria-practices/#TreeView
https://w3c.github.io/aria-practices/examples/treeview/treev...
I ask because I've tried to implement a [TreeGrid](https://w3c.github.io/aria-practices/#treegrid) myself before and... it's a lot of work. I'd love an accessible, keyboard-friendly React tree :).
-
Custom JavaScript controls can't capture the nuance of form fields (2021)
Yep I totally agree with this.
There are however a bunch of ARIA tags & best practices etc (https://w3c.github.io/aria-practices/) that exist to make popups and dialogs (and other things e.g. tree views or "email-inbox-style" "treegrids" etc) accessible (if implemented correctly).
I am conflicted about these - it is nice that there are ARIA tags for this, but it would also be nice if browsers "understood" aria tags and added some default behaviors (e.g. keyboard navigation). As it is, ARIA tags are essentially "pointless" to anyone who doesn't use an assistive technology, and so non-assitive-technology users nor developers benefit from using ARIA tags so they are often forgotten. If the browsers saw that there was an A11y-tree that matched a treeview or a treegrid, it would be really really nice if they applied some default common keyboard navigation implementation, rather than do nothing and leave it up to the developer to decide what keys do what on each and every site. .... Or on the other hand, is that too prescriptive and should we give developers and UX designers more leeway to design something better, rather than rely on browser-enforced defaults? I guess we are happy with browser defaults for basic inputs, but would we be for a treegrid?
-
4 takeaways from axe-con 2021
The ARIA practices GitHub is a good resource to see where certain patterns fall short.
gecko-dev
-
Making Web Component properties behave closer to the platform
You can see how Mozilla tests the compliance of their built-in elements in the Gecko repository (the ok and is assertions are defined in their SimpleTest testing framework). And here's the Web Platform Tests' reflection harness, with data for each built-in element in sibling files, that almost every browser pass.
- Widevine Content Decryption Module provided by Google Inc -- Never installs on any fresh Linux distro (see comments)
-
Firefox tooltip bug fixed after 22 years
The source is mirrored on GitHub here: https://github.com/mozilla/gecko-dev
Code search is here: https://searchfox.org/mozilla-central/
-
Firefox 113.0, New Features, Updates and Fixes
Yes. https://github.com/mozilla/gecko-dev/tree/32c74afbb24dce4b5d...
- -moz-box and -moz-inline-box removed at v113
-
Pinch Zoom with Mouse Wheel is too Slow = How to Adjust Zoom Increments?
aWheelInput.mDeltaY looks like the increment setting used for this https://github.com/mozilla/gecko-dev/commit/9033e3e1200acfd4b8f8ae024c215b99d12b97bdTried "mousewheel.default.delta_multiplier_y" and "mousewheel.with_control.delta_multiplier_y" without much luck.It may have something to do with https://bugzilla.mozilla.org/show_bug.cgi?id=1138704 although this case is about pinch zoom emulation.
-
Why does firefox (at least waterfox) not support H.265?
You could add the feature by writing code to support is - https://firefox-source-docs.mozilla.org/setup/index.html
- A Quarter Century of Mozilla
-
Why is building a UI in Rust so hard?
I checked Firefox monorepo, it has over 4x more C++ than Rust.
-
Fetched and build the code of the "release" but it's produced Nightly version
Are you leaving steps out or is your OP exhaustive? If you just straight up cloned release and that's it, start all over and follow https://firefox-source-docs.mozilla.org/setup/index.html for your OS
What are some alternatives?
react-arborist - The complete tree view component for React
chromium - The official GitHub mirror of the Chromium source
react-table-library - :bento: React Table Library
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
bootstrap-select - :rocket: The jQuery plugin that brings select elements into the 21st century with intuitive multiselection, searching, and much more.
Skia - Skia is a complete 2D graphic library for drawing Text, Geometries, and Images.
standards-support - Contains documentation for Vispero software support of Web standards
brave-core - Core engine for the Brave browser for mobile and desktop. For issues https://github.com/brave/brave-browser/issues
monaco-tree - Curiosity hacks with Monaco Editor's tree component
nyxt - Nyxt - the hacker's browser.
aktenkoffer - 💼 Personal document management made easy.
datastation - App to easily query, script, and visualize data from every database, file, and API.