SaaSHub helps you find the best software and product alternatives Learn more →
Standards-positions Alternatives
Similar projects and alternatives to standards-positions
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
-
-
vial-gui
Vial is an open-source cross-platform (Windows, Linux and Mac) GUI and a QMK fork for configuring your keyboard in real time.
-
-
-
-
-
-
file-system-access
Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
-
-
-
-
standards-positions discussion
standards-positions reviews and mentions
-
App Should Have Been a Website (and Probably Your Game Too)
It’s important to note that it’s not a matter of effort for Firefox. They’ve decided that the it’s not something they want to implement[1]. The reasoning is that they think it allows low enough level access to potentially mess with devices who weren’t made to be resilient to malicious input, and didn’t like that the proposed method of allowing web Bluetooth is based on a default allow policy with a blocklist, which means as new Bluetooth device vulnerabilities are discovered, this blocklist has to be maintained.
[1]: https://mozilla.github.io/standards-positions/#web-bluetooth
-
Is Chrome the New IE?
I stand corrected. It was the absolute legends at Igalia. See links and explainer here: https://github.com/mozilla/standards-positions/issues/528
-
Europeans Spend 575M Hours Clicking Cookie Banners Every Year
I mean is there any movement in getting major browsers to adopt this?
Normally when a spec. like this is written that needs adoption from web browsers, an explainer is written and then the major rendering engines are asked for their feedback. For instance, here’s an explainer:
https://github.com/krgovind/first-party-sets
Here’s where WebKit was asked for their position on it:
https://github.com/WebKit/standards-positions/issues/93
Here’s where Mozilla was asked for their position on it:
https://github.com/mozilla/standards-positions/issues/350
Here’s the process Blink goes through to get a new feature like this going:
https://www.chromium.org/blink/launching-features/
I tried to find where this was done for GPC and couldn’t find anything. Did they just write a spec. and not bother doing any of the work involved in getting it adopted? Or is there progress being made that I didn’t see? Hence my question: Is there any movement on this at all? Or is the process of getting it adopted by Blink and WebKit at absolute zero?
-
Origin private file system – MDN
> kept around for as long as FireFox feels like
I've heard Firefox keep OPFS data in browser as long as there's enough space (which can be checked from JS). Safari has a stricter strategy and removes OPFS data and local storage more aggressively, for example, if a site domain hasn't been visited in 7 days.
On the File System Access API, it seems doubtful that Mozilla will ever implement it in a useful way.
> Mozilla's Position
> There's a subset of this API we're quite enthusiastic about (in particular providing a read/write API for files and directories as alternative storage endpoint), but it is wrapped together with aspects for which we do not think meaningful end user consent is possible to obtain (in particular cross-site access to the end user's local file system). Overall we consider this harmful therefore, but Mozilla could be supportive of parts, provided this were segmented better.
https://mozilla.github.io/standards-positions/#native-file-s...
- Direct Sockets API in Chrome 131
-
Smarter Than 'Ctrl+F': Linking Directly to Web Page Content
I was surprised too, cause initially they had some issues with the proposal [1], resolved it few years later [2], and finally implemented it since last year [3]
[1] https://github.com/mozilla/standards-positions/issues/194#is...
[2] https://github.com/mozilla/standards-positions/issues/194#is...
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1753933
-
JPEG XL in iPhone 16 Pro Yields Results
Sept. 3rd:
> the team at Google has agreed to apply their subject matter expertise to build a safe, performant, compact, and compatible JPEG-XL decoder in Rust
https://github.com/mozilla/standards-positions/pull/1064
-
Mozilla is currently not investing in PWAs
Direct link to the comment on the thread:
https://github.com/mozilla/standards-positions/issues/340#is...
-
Using the Topics API (Chrome Only, Opposed by Firefox/Safari)
Request for positions on the topics API - https://github.com/WebKit/standards-positions/issues/111 also mentioned in https://github.com/mozilla/standards-positions/issues/622
The Register article on the topics api last year https://www.theregister.com/2023/06/27/google_tweaks_topics_...
- Firefox will consider a Rust implementation of JPEG-XL
-
A note from our sponsor - SaaSHub
www.saashub.com | 13 Jan 2025
Stats
mozilla/standards-positions is an open source project licensed under Mozilla Public License 2.0 which is an OSI approved license.
The primary programming language of standards-positions is HTML.
Popular Comparisons
- standards-positions VS webcontainer-core
- standards-positions VS WHATWG HTML Standard
- standards-positions VS wpt
- standards-positions VS firefox-ios
- standards-positions VS storage-foundation-api-explainer
- standards-positions VS Fakeflix
- standards-positions VS uBlock-Safari
- standards-positions VS WebKit
- standards-positions VS web-bugs
- standards-positions VS brave-browser