- Google is transitioning Chrome’s extension support from the Manifest V2 framework to the V3.
- This means users won’t be able to use uBlock Origin to block ads on Google Chrome.
- However, there’s a new iteration of the app — uBlock Origin Lite, which is Manifest V3 compliant but doesn’t boast the original version’s comprehensive ad-blocking features.
What? They all have W3C specs. Firefox just chose not to implement them.
- https://www.w3.org/Graphics/Color/Workshop/talks.html
- https://www.w3.org/TR/appmanifest/
- https://wicg.github.io/shape-detection-api/#barcode-detection-api
- https://www.w3.org/TR/nfc/
- https://www.w3.org/TR/accname-1.2/#computation-steps
- https://drafts.fxtf.org/css-masking/#the-mask-border
You think you’re trashing Chrome, but you’re trashing Firefox instead.
Even line-height
in CSS3 is draft. Saying no drafts should be implemented is a ridiculous standpoint: a standpoint not even Firefox aligns with:
Standardization requirements for shipping features
What evidence is necessary will vary, but generally this will be:
W3C - the specification is at the Candidate Recommendation maturity level or more advanced; shipping from a Working Draft or a less advanced specification requires evidence of agreement within the working group that shipping is acceptable
https://wiki.mozilla.org/ExposureGuidelines
But keep moving those goal posts.