The FileSystemAccessLocal feature has just been enabled for android in M132.
On Thu, Sep 5, 2024 at 7:30 PM Thomas Steiner wrote:
> Very excited for this feature to come, it's a frequently requested gap so
> far—frequently enough to link to the FSA for Android bug from our
> developer-facing doc
> This seems like a good change, but I notice that it has no flag
associated with it
Okay, patchset 8.
https://chromium-review.googlesource.com/c/chromium/src/+/5923046
BASE_FEATURE(kIgnoreHSTSForLocalhost,
"IgnoreHSTSForLocalhost",
base::FEATURE_ENABLED_BY_DEFAULT);
LGTM1 - but I do have some comments.
It's good catching up here, but I recommend always to write an
explainer. For a trivial change, it might be a trivial explainer, but
just something for those that are not intimately familiar with the area.
Might just be a one or a few sentences. And it's no
This seems like a good change, but I notice that it has no flag
associated with it. Is there a reason for that (i.e. very hard to
implement) or something similar? If not, we should play it safe and have
one just in case there are unforeseen consequences.
/Daniel
On 2024-10-24 23:56, Mike Tayl
LGTM3
/Danel
On 2024-10-24 19:48, Mike Taylor wrote:
LGTM2
On 10/23/24 12:57 PM, 'Geoff Lang' via blink-dev wrote:
On Wednesday, October 23, 2024 at 8:21:22 AM UTC-7 Yoav Weiss wrote:
Can y'all flip the review bits for
privacy/security/enterprise/testing/debuggability?
Done!
On W
I can confirm that 6 milestones is approved, and either 131-136 or
132-137 (and I will even expand that to 133-138 just in case) will be
fine. Good luck experimenting!
LGTM
/Daniel
On 2024-10-24 05:33, Domenic Denicola wrote:
Thanks Yoav!
Unfortunately there was a slight miscommunication wi
Can we request reviews for Security, Privacy, Enterprise, etc in the
chrome status entry?
thx
On 10/24/24 5:42 PM, Alex Russell wrote:
LGTM1
On Thu, Oct 24, 2024, 11:39 AM Eric Lawrence wrote:
Okay, I've proposed a tweak.
https://github.com/whatwg/fetch/pull/1781
On Thursday,
Contact emails
gabrielbr...@microsoft.com, stev...@microsoft.com
Explainer
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AudioContextInterruptedState/explainer.md
Specification
None
Summary
The current Web Audio API lacks a mechanism for the User Agent (UA) to
interrupt playba
> probably makes sense to start by suggesting a change to
https://fetch.spec.whatwg.org/#concept-main-fetch,
> but the editors there might ask you to write an update to the RFC.
I don't think I understand what change to Fetch would be proposed. The
section you flagged has two relevant clauses r
