
Suppress unsafe buffer usage on a file-by-file basis. Out of approximately 5850 .cc and .h files only roughly 160 files fail compilation with the unsafe buffers warning. Suppress only, by inserting boilerplate into affected files. Do not re-write any code to work around the issues. Properly fixing each file will be done in follow-up CLs. //content/ is not removed from unsafe_bufers_paths.txt file and will be also done as a follow-up, so it makes potential reverts simpler. Bug: 342213636 Change-Id: I4a936e63dea95a78951f7bfae6d5487708ae3c0b AX-Relnotes: n/a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5608913 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Owners-Override: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/main@{#1312393}
File System Access API
This directory contains part of the browser side implementation of the File System Access API.
This specification for API is split across two repositories:
- https://github.com/whatwg/fs/, which specifies features available within the
Origin Private File System, including the
SyncAccessHandle
API, and - https://wicg.github.io/file-system-access/, which additionally specifies
features allowing users to interact with their local file system, primarily
via the
show*Picker()
APIs.
Related directories
//storage/browser/file_system/
contains the
backend this API is built on top of,
blink/renderer/modules/file_system_access
contains the renderer side implementation and
blink/public/mojom/file_system_access
contains the mojom interfaces for these APIs.