Thanks for the pings, Marcos. I'll try and have an update for you in the
next week.
On Thu, May 26, 2022 at 8:07 AM Marcos Caceres wrote:
> Just checking in again 👋 I'm wondering if by chance folks here might be
> to ping the YouTube folks one last time? It's been a while, so maybe they
> will r
Since this is an incremental addition to the existing FSA API, my guess is
that the positions there sufficient here:
Gecko: https://mozilla.github.io/standards-positions/#native-file-system
Webkit:
https://lists.webkit.org/pipermail/webkit-dev/2020-August/031362.html
These two engines give a Nega
NOT shipping in 106.
Since this is not a security-motivated removal (there are other APIs that
provide the same data), despite the usage numbers being extremely low we
are holding until we've made our best effort to reach out to partners using
Chrome in scenarios where we may not have usage metric
I2Ps don't need any LGTMs. Was there specific feedback you were looking for?
On Wed, Aug 18, 2021 at 10:10 AM Mike Taylor wrote:
> This I2P seems to have fallen through the cracks (understandably lots of
> vacation happening this month).
> Any thoughts from API owners?
>
> On 8/9/21 2:20 PM, Ari
Drive-by comment on the thread:
There was a question up-thread about whether the 1s user activation was
sufficient time for real-world use cases. Unfortunately it is not - some
apps that do data transcoding - e.g. image editors that need to composite
multiple layers then do an image format encodin
Super low priority question:
We've got WPTs and tooling that slurps Web IDL from specs and validates it
against implementations which in theory should have caught this. This is a
fairly fragile process (requires spec to be just right, jobs to be
configured, tests to exist, integration bots to succ
verloads right they're indistinguishable from the unions, as intended.
But anyway, "simple" things like interface exposure should just work, since
they'll compare the spec IDL and assert that the global contains an
appropriately named property.
> -Ken
>
>
>
&
Hey folks! This is very exciting to see.
I notice the linked explainer is marked Archived, and links to itself as
the current version? The attached design doc is helpful, but *unhelpfully*
forbids copy/paste. Can you fix that?
The explainer calls out that there's no API change, but the design doc
I'm excited to see this!
On Mon, Jun 12, 2023 at 4:13 PM 'Daniel Clark' via blink-dev <
blink-dev@chromium.org> wrote:
> Contact emails
>
> sni...@microsoft.com, shih...@microsoft.com, bemat...@microsoft.com,
> dan...@microsoft.com
>
>
> Explainer
>
> https://github.com/w3c/edit-context/blob/gh-p
Just a quick note on spec maturity: as spec mentor, I did a thorough
review of the spec text, and noted many issues - all small - which have
been addressed. As the feature introduces a privacy boundary between two
documents with very sensitive one-way control, it is non-trivial but the
design is w
On Wed, Apr 20, 2022 at 4:21 AM Yoav Weiss wrote:
>
>
> On Wed, Apr 13, 2022 at 6:46 PM Joshua Bell wrote:
>
>> On Wed, Apr 13, 2022 at 6:36 AM Yoav Weiss
>> wrote:
>>
>>> Also, any learnings/feedback from the Origin Trial?
>>>
>>>
>&
when the OS rendering pipeline isn't at potential risk), and
>>> highlights the way that the current design is isomorphic with local file
>>> access.
>>>
>>> I've LGTM'd it in the tool as a result.
>>>
>>> Thanks to everyone at Google f
On Wed, Apr 13, 2022 at 6:36 AM Yoav Weiss wrote:
> Also, any learnings/feedback from the Origin Trial?
>
>
Not distinct from the dev trial (i.e. developers trying the API behind a
flag). There was a feature request for additional metadata which was
implemented, then the request was withdrawn so
feature detection can
be done.
We'd considered having the API present, but return an empty list, but
thought that could train developers to expect that behavior on mobile
platforms, whereas we do plan to support the API there in the future.
On Wed, Apr 13, 2022 at 9:46 AM Joshua Bell wrote:
14 matches
Mail list logo
