file-system-access
standards-positions
file-system-access | standards-positions | |
---|---|---|
16 | 16 | |
641 | 231 | |
0.6% | 0.9% | |
5.0 | 7.0 | |
about 1 month ago | 3 months ago | |
Bikeshed | Python | |
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.
file-system-access
-
The web just gets better with Interop 2024
You can read about the privacy concerts the community group published [1].
[1]: https://wicg.github.io/file-system-access/#privacy-considera...
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
WHATWG File System Standard provides a means to write directories and files to the private origin storage associated with a Web page origin. If you want you can use WICG File System Access API to write data directly to your filesystem in the browser. WHATWG File System Standard uses the same FileSystemDirectoryHandle and FileSystemFileHandle defined by File System Access API.
-
How to execute arbitrary dynamic shell scripts from and read output in the browser
Chromium-based browsers support File Systeam Access API.
-
"Can't open files in this folder because it contains system files"
We have stopped using the file system access API: https://github.com/WICG/file-system-access/issues/401
-
SQLite WASM in the Browser Backed by the Origin Private File System
Where file handling is concerned, there are at least
- File System Access API, https://wicg.github.io/file-system-access/
- File Handling, https://github.com/WICG/file-handling/blob/master/explainer....
- Origin Private File System, https://github.com/WICG/file-system-access/blob/main/AccessH...
There was also Storage Foundation API to which the reaction was "I don't think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.
-
Learn Postgres at the Playground
Huh. Disregard what I wrote entirely, then. Reading through https://github.com/WICG/file-system-access/blob/main/AccessH..., I can see how they’ve bypassed most of the problems I saw—I was making unnecessary assumptions.
Thank you for correcting me.
-
The State of WebAssembly 2022
> Browsers have never let anything (not even JS) have raw access to the host FS
I'm not sure what you mean by "raw access", but the File System Access API certainly allows web applications to do a lot of things.
> The File System Access API (formerly known as Native File System API and prior to that it was called Writeable Files API) enables developers to build powerful web apps that interact with files on the user's local device, like IDEs, photo and video editors, text editors, and more.
https://web.dev/file-system-access/
> After a user grants a web app access, this API allows the app to read or save changes directly to files and folders on the user’s device. Beyond reading and writing files, this API provides the ability to open a directory and enumerate its contents. Additionally, web apps can use this API to store references to files and directories they’ve been given access to, allowing the web apps to later regain access to the same content without requiring the user to select the same file again.
> Additionally this API also makes it possible for websites to get access to some directory without having to first prompt the user for access.
https://wicg.github.io/file-system-access/
It's not just a draft, it's been part of Chrome since version 78 in 2019.
> After a user grants access, this API allows web apps to read or save changes directly to files and folders on the user's device. It does all this by invoking the platform's own open and save dialog boxes.
https://blog.chromium.org/2019/09/chrome-78-beta-new-houdini...
Discussion at the time:
https://news.ycombinator.com/item?id=21032537
-
How to Persist Web App Data in the User File System?
In the post, the Vite webserver is only used to serve the HTML and JS static files to the browser. When the user saves or opens text files, the code uses the web File System Access API (https://wicg.github.io/file-system-access/) to interact with the user file system.
-
The road to universal JavaScript
Have you heard of Project Fugu and their idea of a File System Access API in the browser? https://wicg.github.io/file-system-access/
-
What's your prefered way to allow end user to rename multiple text files?
I don't know a C++ equivalent of HTML , prompt(), or File System Access API (https://wicg.github.io/file-system-access/; https://web.dev/file-system-access/) using JavaScript in the browser window.
standards-positions
-
iOS404
You can check why Mozilla and Apple have opted to not support this.
https://github.com/mozilla/standards-positions/issues/154
https://github.com/WebKit/standards-positions/issues/28
Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.
-
Show HN: Tiniest Web Component
Nope, was marked as WONTFIX: https://bugs.webkit.org/show_bug.cgi?id=182671
There was some more discussion in the webkit standards but looks like the answer is still unchanged: https://github.com/WebKit/standards-positions/issues/97
-
The web just gets better with Interop 2024
The new scrollbar styling properties are actually pretty consistent with native platforms. There's not that much flexibility with them - e.g. you can't define width in pixels, you just chose between thick, thin, or none, which match the existing native controls:
https://github.com/WebKit/standards-positions/issues/133#iss...
> To add more information to this issue. This property supports three values, auto, thin and none. These match nicely to WebKit's ScrollbarControlSize::Regular and ScrollbarControlSize::Thin and not rendering the scrollbar.
-
Mozilla thinks Apple, Google, Microsoft should play fair
Apple puts their policy positions on GitHub too. It's just where this is done for some reason: https://github.com/WebKit/standards-positions
-
Quic.video
Not yet but one day: https://github.com/WebKit/standards-positions/issues/18#issu...
- WebKit Web Environment Integrity API
-
Mozilla Standards Positions Opposes Web Integrity API
Worth also noting is WebKit's standards positions at
https://webkit.org/standards-positions/
(this one has not landed yet, likely to be opposed as well)
- WebKit Standards Positions
- WebKit is going to support WebTransport
What are some alternatives?
datasette-lite - Datasette running in your browser using WebAssembly and Pyodide
interop - web-platform-tests Interop project
brave-browser - Brave browser for Android, iOS, Linux, macOS, Windows.
standards-positions
webusb - Connecting hardware to the web.
caniuse - Raw browser/feature support data from caniuse.com
fs - File System Standard
popover-polyfill - Polyfills the HTML popover attribute and showPopover/hidePopover/togglePopover methods onto HTMLElement, as well as the popovertarget and popovertargetaction attributes on <button> elements.
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
construct-stylesheets - API for constructing CSS stylesheet objects
enhance.dev - Docs website for Enhance!