stylelint-no-unsupported-browser-features
ua-client-hints
Our great sponsors
| stylelint-no-unsupported-browser-features | ua-client-hints | |
|---|---|---|
| 2 | 13 | |
| 374 | 538 | |
| - | 0.4% | |
| 7.6 | 2.7 | |
| 23 days ago | 2 months ago | |
| JavaScript | Bikeshed | |
| - | 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.
stylelint-no-unsupported-browser-features
-
Browserslist: building modern web apps for diverse global audience
Of course, we have great tooling for that: Autoprefixer, PostCSS and Stylelint for CSS transformation, Babel and Webpack for JavaScript transpilation and bundling, ESLint for code analysis, and many others.
- JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
ua-client-hints
- Példátlan leállás jöhet a neten, és nem is lesz egyszerű megoldani
-
Version 100 in Chrome and Firefox
I encourage you to review the decision making and engage in the discussion here: https://github.com/WICG/ua-client-hints
-
Google Chrome Update will cause Big Issue For 2 Billion Users
chrome is starting to implement UA-CH, which splits up user agent info into individual headers sent by the client: https://wicg.github.io/ua-client-hints/
-
JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
As a Firefox/FreeBSD user occasionally annoyed by this nonsense, but not being knowledgeable about modern web standards evolution, I wonder if https://wicg.github.io/ua-client-hints/ will fix this by killing User-Agent headers.
-
Mozilla alters stance on User-Agent Client Hints from “non-harmful” to “harmful”
There is a JS companion to this proposal that splits up the information in a similar way
-
User-Agent Client-Hints, take 2
First, the JavaScript API is widely open and does not require any delegation or even opt-in. IMO this is a privacy issue, and Apple seems to agree with me 🙂
- Firefox 85 Cracks Down on Supercookies
What are some alternatives?
eslint-plugin-compat - Check the browser compatibility of your code
stylelint-scss - A collection of SCSS specific linting rules for Stylelint
chromium-legacy - Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+
AdminLTE - Pi-hole Dashboard for stats and more
stylelint-no-unsupported-browser-fe
notrack-blocklists
evercookie - Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
hosts-blocklists - Automatically updated, moderated and optimized lists for blocking ads, trackers, malware and other garbage
stylelint-config-recommended - The recommended shareable config for Stylelint
webappsec-permissions-policy - A mechanism to selectively enable and disable browser features and APIs
webcompat-addon - Hotfixing the web, one Intervention at a time.