LGTM3
I will mostly repeat what I said for the Summarizer here because I think
the two APIs share similar challenges.
This is a non-deterministic API and as such presents specific challenges
for both users (web developers) and maintainers (browser developers).
Current implementations also ru
Friendly ping on this thread, any other input regarding shipping the
Translator API? Thanks!
On Thu, Jun 5, 2025 at 9:54 AM Yoav Weiss (@Shopify)
wrote:
> LGTM2
>
> There's some risk here with developers persisting the output of the API,
> which quality may vary depending on the current browser
LGTM2
There's some risk here with developers persisting the output of the API,
which quality may vary depending on the current browser implementation.
At the same time, it does seem like a useful feature for in-line instant
translations to languages the content author hasn't predicted.
It'd be goo
LGTM1 - the team has demonstrated a clear demand for this type of
feature. I look forward to Mozilla shipping an alternate proposal - it
seems to me that it's complementary and not in conflict with us shipping
Translator now.
On 6/3/25 10:27 AM, Mike Taylor wrote:
On 6/3/25 9:27 AM, 'Kagami
On 6/3/25 9:27 AM, 'Kagami Rosylight' via blink-dev wrote:
> They haven’t given any negative signals on our proposed Translator
API (nor official positive ones).
You can consider Mozilla to be negative here. We plan to make it more
clear in our counterproposal why we think it's better.
If you
> They haven’t given any negative signals on our proposed Translator API
(nor official positive ones).
You can consider Mozilla to be negative here. We plan to make it more clear
in our counterproposal why we think it's better.
On Tuesday, June 3, 2025 at 12:07:35 AM UTC+2 dbo...@chromium.org w
