W3C home > Mailing lists > Public > public-wicg@w3.org > March 2023

Re: [EXTERNAL] Updated site wicg.io

From: Tom Jones <thomasclinganjones@gmail.com>
Date: Wed, 8 Mar 2023 09:01:34 -0800
Message-ID: <CAK2Cwb48ZSuodG0QesgZRs80jq9mXenPPSYN1YxcKgPqbRH_Nw@mail.gmail.com>
To: Thomas Steiner <tomac@google.com>
Cc: Alex Russell <alexrussell@microsoft.com>, Marcos Caceres <caceres_m@apple.com>, "public-wicg@w3.org" <public-wicg@w3.org>
Something's really wrong here. Chromium is supposed to be open source and
lots of forks exist. But this group sounds like an internal Google thing.
If Google wants it, it MUST happen. And only 2 forks matter, Chrome and
Edge. I work on an incubating fork and expect that there will be some of
the features that are not allowed as they are considered not safe. That
process is likely to accelerate.


On Wed, Mar 8, 2023 at 1:42 AM Thomas Steiner <tomac@google.com> wrote:

> On Wed, Mar 8, 2023 at 6:47 AM Alex Russell <alexrussell@microsoft.com>
> wrote:
>> We might also add Samsung Internet (who configure runtime flags
>> differently based on Samsung policies) and Opera?
> So does Brave (they disable the show*Picker() methods
> <https://github.com/brave/brave-browser/issues/11407> for the File System
> Access API), which caused enough developer confusion that I saw myself
> forced to call Brave out in our article
> <https://developer.chrome.com/articles/file-system-access/#:~:text=A%20notable%20exception%20is%20Brave%20where%20it%20is%20currently%20only%20available%20behind%20a%20flag.>.
Received on Wednesday, 8 March 2023 17:02:00 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 8 March 2023 17:02:01 UTC