LGTM3
/Daniel
On 2023-05-10 11:39, Mike West wrote:
LGTM2.
-mike
On Wed, May 10, 2023 at 1:10 AM 'Loko Kung' via blink-dev
wrote:
Thanks Yoav for taking a look! Bumping this again since M115
branch point is coming soon (May 23) and we still need 2 more
LGTMs before I can
LGTM2.
-mike
On Wed, May 10, 2023 at 1:10 AM 'Loko Kung' via blink-dev <
blink-dev@chromium.org> wrote:
> Thanks Yoav for taking a look! Bumping this again since M115 branch point
> is coming soon (May 23) and we still need 2 more LGTMs before I can land
> the changes!
>
> On Tuesday, May 9,
Thanks Yoav for taking a look! Bumping this again since M115 branch point
is coming soon (May 23) and we still need 2 more LGTMs before I can land
the changes!
On Tuesday, May 9, 2023 at 7:31:33 AM UTC-7 Yoav Weiss wrote:
> LGTM1
>
> On Wed, May 3, 2023 at 9:52 PM Loko Kung wrote:
>
>> Thanks
LGTM1
On Wed, May 3, 2023 at 9:52 PM Loko Kung wrote:
> Thanks Kai for replying! To add on top of that:
>
> For the signals: Positive
> https://github.com/WebKit/standards-positions/issues/107
> https://mozilla.github.io/standards-positions/#webgpu
>
\o/
>
>
> For the web-platform-tests, on
Thanks Kai for replying! To add on top of that:
For the signals: Positive
https://github.com/WebKit/standards-positions/issues/107
https://mozilla.github.io/standards-positions/#webgpu
For the web-platform-tests, on top of the CTS Kai mentioned, the change in
Thank you for the questions, replies inline!
I actually ran into the same problem when I filed an I2S recently with a
lot of gaps in the generated email. The chromestatus tool hides most of the
fields used to generate emails behind various stages of shipment, which
makes it hard to set them
On Wed, May 3, 2023 at 12:04 AM Ken Russell wrote:
> Could more Blink owners please provide their input? This is a feature the
> WebGPU CG has standardized, and we would like to get it in our
> implementation ASAP so the associated tests can start running correctly in
> Chrome.
>
> Thanks,
>
>
Could more Blink owners please provide their input? This is a feature the
WebGPU CG has standardized, and we would like to get it in our
implementation ASAP so the associated tests can start running correctly in
Chrome.
Thanks,
-Ken
On Tue, May 2, 2023 at 9:56 AM Caleb Raitto wrote:
>
Thanks, I thought so, but wanted to confirm :)
-Caleb
On Tue, May 2, 2023 at 12:54 PM Ken Russell wrote:
> These are essentially GPU-independent, syntactic-sugar-like, language
> extensions that it's expected all browsers will eventually implement. Since
> browser updates roll out at different
These are essentially GPU-independent, syntactic-sugar-like, language
extensions that it's expected all browsers will eventually implement. Since
browser updates roll out at different times, it's important that the
application be able to query their support status so they can know which
versions
Are these language extensions specific to certain GPUs (could this be used
to fingerprint the GPU)? Or are the language extensions something that some
browsers will implement, but others won't?
Thanks,
-Caleb
On Wednesday, April 26, 2023 at 3:36:27 PM UTC-4 Mike Taylor wrote:
> All good -
All good - I've flagged it in our chromestatus tool so it doesn't fall
off our radar.
(and updating the email title just in case)
On 4/26/23 2:42 PM, 'Loko Kung' via blink-dev wrote:
Ah, sorry for the misleading title. This is actually an Intent to
Ship! Let me know if I should resend with
12 matches
Mail list logo
