Rob Dolin at Microsoft and Marcos Caceres at Mozilla (et al) did a ton of work to add things like IARC rating, screenshots, and category to the Web App Manifest spec. https://github.com/w3c/manifest
You already know who owns the site, because they own the domain. You have all the information you need to ingest their app into the app store – no need to make them build a native app wrapper, submit it to the store, redirect their users to the native app, and go through all that hoopla.
Things I like about VoiceOver:
- shows text overlay in addition to speaking
- is built in to macOS
- takes like 10 minutes to learn how to use
Check out https://youtu.be/5R-6WvAihms for a good overview of how to use VoiceOver. I'm only slightly exaggerating to say that I didn't "get" accessibility until I watched this video and learned how to use it.
Work with CSS? Help Mozilla build better developer tools: https://qsurvey.mozilla.com/s3/CSS-Debugging-9dee73102e21T
All about DNS over HTTPS, separating concerns about the protocol from concerns about centralizing it with large cloud providers:
I've just released a Plaudit browser extension! Plaudit is an attempt to simulate #OpenAccess research by influencing the incentive structure for researchers: direct endorsements by their peers, rather than through being published in a paywalled journal.
The Legacy of Firefox OS https://medium.com/@bfrancis/the-legacy-of-firefox-os-c58ec32d94f0
And the prize for "Best Project Name Ever" goes to a Scheme dialect to create Ethereum smart contracts: Pyramid Scheme.
I've been doing some accessibility work recently, and I've been somewhat surprised by how some (I assume) pretty common things do not appear to have come up on StackOverflow before.
Or, well, surprised... Of course a11y is relatively often neglected. Still, I'd presume more people who aren't accessibility experts would have wanted to know whether button elements triggering click events on keypresses is standardised behaviour.
If not zero-config, then TypeScript support often is at most a matter of installing it and flipping a config option. In the spirit of which I should mention the plugin I wrote for React Static last week, that allows you to seamlessly use TypeScript in your React Static projects:
Just found out about npm's tink (thanks @baldur), and the most interesting thing is not so much tink itself, but this:
> it does a lot of neat little things like load Typescript (...) out of the box
Many projects appear to move to zero-config TypeScript support out of the box. As a result, the barrier to entry is getting really low, and TypeScript usage is bound to grow even more.
@juliank Apparently that's not possible:> the intention to withdraw must, first, be submitted in writing to the European Council and, secondly, be unequivocal and unconditional.More extensive quotes and sources here:https://www.reddit.com/r/europe/comments/a4tsy2/bbc_news_uk_can_cancel_brexit_says_eu_court/ebhjvsf/
After mulling over the Edge-Chromium announcement for a couple of days, there are two questions I have about the future:
1. Will web developers keep (?) testing in Firefox?
2. Will Mozilla be able to keep up with the presumably increased pace of Chromium?
If the answer to both of these questions is "yes", then I think the web might be better off, given that Microsoft might be a significant counterweight to Google in the Chromium project, and that Edge will be open source and cross-platform.
I finally gave in a wrote a bespoke blog generator. With excellent performance, thanks to some React-Static preloading magic.Check it out at https://vincenttunru.com.
Firefox is now more important, isolated and vulnerable. Some suggested ways we can support it:
• Set it as your default browser. And if you're back home with family over Christmas, suggest/set as their default too.
• When you hear web devs say "can't everyone just use Chrome", please challenge it.
• Contribute to Mozilla-led projects, e.g. MDN Docs: https://www.smashingmagazine.com/2018/05/contributing-mdn-webdocs/
• Donate to Mozilla if you can: https://donate.mozilla.org
If you really want to help Firefox succeed, file a bug on https://webcompat.com/ when you find a broken website. Don't just switch back to Chrome; let Mozilla know there's a problem so they can try to fix it.
When browsers lose market share, they fall into the "compatibility death spiral." Sites don't bother to test, they break, and users flee to the browser that "just works." Mozilla is fighting this battle every day, and it just got harder.
Front-end developer trying to open up access to academic research and helping out with @ToSDR. My current "boring stack": React+TypeScript.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!