ua-client-hints
stylelint-no-unsupported-browser-fe
Our great sponsors
| ua-client-hints | stylelint-no-unsupported-browser-fe | |
|---|---|---|
| 13 | 1 | |
| 570 | - | |
| 1.4% | - | |
| 4.2 | - | |
| 18 days ago | - | |
| 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.
ua-client-hints
-
Website Fidelity
The Client Hints specification covers a lot of this already - https://wicg.github.io/ua-client-hints/#content-adaptation-u... ... DPR, width, and viewport-width are already available in some browsers. Hopefully other hints will be available soon.
- UA Gotta Be Kidding
- 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
- W3C User Agent 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.
- W3C User-Agent Client Hints ( SEC-CH-UA-* HTTP Headers)
-
Mozilla tests if 'Firefox/100.0' user agent breaks websites
ua-ch might reduce the amount of data browsers send, though it's gonna take a while to move away from regular user agents: https://wicg.github.io/ua-client-hints/
-
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
stylelint-no-unsupported-browser-fe
What are some alternatives?
web - Pi-hole Dashboard for stats and more
eslint-plugin-compat - Check the browser compatibility of your code
chromium-legacy - Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+
stylelint-no-unsupported-browser-features - Disallow features that aren't supported by your target browser audience.
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.
ethical-ad-client - Ethical Ads JavaScript client
hosts-blocklists - Automatically updated, moderated and optimized lists for blocking ads, trackers, malware and other garbage
notrack-blocklists
webappsec-permissions-policy - A mechanism to selectively enable and disable browser features and APIs
webcompat-addon - Hotfixing the web, one Intervention at a time.