Thanks for the feedback - but if you re-read the explainer, you'll note
that preferred languages will continue to work with the proposed
Avail-Language API.
On 8/11/24 1:14 AM, Eli Grey wrote:
Restricting accept-language to 'common combinations' is fundamentally
at odds with personal agency. T
Thanks for the thoughtful article and feedback Yoav - we'll chat about
it internally.
On 8/20/24 11:24 PM, Yoav Weiss (@Shopify) wrote:
I wrote a few words about this proposal and how I think we can avoid
some of the tradeoffs it is making and end up with better user
experience *and* more p
LGTM to experiment 129-134 inclusive, or shifted if you can't start in 129.
That said, I would expect things to change during the experiment,
including the name. Like TAG I find including "ai" in the programmer
visible symbols to be less than optimal. We don't usually put
implementation detail
LGTM1; thanks for the detailed responses to Domenic.
On Sunday, August 18, 2024 at 10:30:50 PM UTC-7 Traian Captan wrote:
> This relates to the interoperability issues discussed below. You say "This
>> change increases interop with Safari and Firefox which already provide a
>> reasonable fallba
LGTM2 - it would be great to add additional tests as mentioned.
On 8/21/24 5:43 PM, Alex Russell wrote:
LGTM1; thanks for the detailed responses to Domenic.
On Sunday, August 18, 2024 at 10:30:50 PM UTC-7 Traian Captan wrote:
This relates to the interoperability issues discussed below.
LGTM1
On Tuesday, August 20, 2024 at 12:05:14 AM UTC-7 Koji Ishii wrote:
> Thank you for pointing this out, Demenic.
>
> Will there be any compatibility issues, i.e. code that means something
>> different before and after the change?
>
>
> You're right, there will be. The `balance` and `pretty`
LGTM2
On 8/21/24 5:52 PM, Alex Russell wrote:
LGTM1
On Tuesday, August 20, 2024 at 12:05:14 AM UTC-7 Koji Ishii wrote:
Thank you for pointing this out, Demenic.
Will there be any compatibility issues, i.e. code that means
something different before and after the change?
LGTM3
/Daniel
On 2024-08-21 17:52, Mike Taylor wrote:
LGTM2
On 8/21/24 5:52 PM, Alex Russell wrote:
LGTM1
On Tuesday, August 20, 2024 at 12:05:14 AM UTC-7 Koji Ishii wrote:
Thank you for pointing this out, Demenic.
Will there be any compatibility issues, i.e. code that means
LGTM2
On Monday, August 19, 2024 at 5:58:15 PM UTC-7 Domenic Denicola wrote:
> Thanks! LGTM1.
>
> On Tue, Aug 20, 2024 at 4:25 AM Frank Liberato
> wrote:
>
>> > It'd be ideal to land this before we approve the intent.
>>
>> Merged, including your suggested change to make the description paragra
LGTM3
/Daniel
On 2024-08-21 17:53, Alex Russell wrote:
LGTM2
On Monday, August 19, 2024 at 5:58:15 PM UTC-7 Domenic Denicola wrote:
Thanks! LGTM1.
On Tue, Aug 20, 2024 at 4:25 AM Frank Liberato
wrote:
> It'd be ideal to land this before we approve the intent.
M
Sorry for the slow response.
Victor: it would be good to see some of that data if and when y'all can
publish it. The API OWNERS aren't generally keen to take breakage risks on
faith.
Best,
Alex
On Wednesday, August 21, 2024 at 1:26:24 AM UTC-7 Mike Taylor wrote:
> Thanks for the thoughtful a
LGTM3
/Daniel
On 2024-08-21 17:44, Mike Taylor wrote:
LGTM2 - it would be great to add additional tests as mentioned.
On 8/21/24 5:43 PM, Alex Russell wrote:
LGTM1; thanks for the detailed responses to Domenic.
On Sunday, August 18, 2024 at 10:30:50 PM UTC-7 Traian Captan wrote:
Th
LGTM2
/Daniel
On 2024-08-16 04:44, Domenic Denicola wrote:
LGTM1!
Please consider updating the explainer a bit to capture where things
ended up, or at least adding a warning of some sort that it's a bit
out of date.
On Fri, Aug 16, 2024 at 12:33 AM Scott Haseley
wrote:
On Wed, Aug
Hi Alex,
I will try to get approval to publish some data if that helps.
Victor
On Wed, Aug 21, 2024 at 11:58 AM Alex Russell
wrote:
> Sorry for the slow response.
>
> Victor: it would be good to see some of that data if and when y'all can
> publish it. The API OWNERS aren't generally keen to ta
LGTM3
On Wednesday, August 21, 2024 at 9:06:12 AM UTC-7 Daniel Bratell wrote:
> LGTM2
>
> /Daniel
> On 2024-08-16 04:44, Domenic Denicola wrote:
>
> LGTM1!
>
> Please consider updating the explainer a bit to capture where things ended
> up, or at least adding a warning of some sort that it's a
LGTM1
On Friday, August 16, 2024 at 6:31:10 AM UTC-7 Rune Lillesveen wrote:
> Contact emailsfuth...@chromium.org
>
> ExplainerNone
>
> Specificationhttps://drafts.csswg.org/css-conditional-5/#container-queries
> Landed PR: https://github.com/w3c/csswg-drafts/pull/10701
>
> Summary
>
> Look up que
Contact emails
nrosent...@chromium.org, vmp...@chromium.org, khushalsa...@chromium.org
Explainer
https://github.com/WICG/view-transitions/blob/main/nested-explainer.md#capture-modes
Specification
None
Summary
In its current form, we capture the view transition into an old&new snapshot
and t
(Unnecessary) LGTM4. Thanks to all your detailed answers, I think the
compat and interop risk is low, and am excited to see this ship.
If you or your team has time to follow up
on https://github.com/whatwg/html/issues/10569 to finish the spec and tests
story, that would be a great help.
On Thu
Contact emailsdome...@chromium.org, fer...@chromium.org,
kenjibah...@chromium.org, h...@chromium.org
Explainer
https://github.com/explainers-by-googlers/writing-assistance-apis/blob/main/README.md
SpecificationNone yet, but looking forward to writing one
Summary
A JavaScript API for writing new
Contact emailsdome...@chromium.org, fer...@chromium.org,
kenjibah...@chromium.org, h...@chromium.org
Explainer
https://github.com/explainers-by-googlers/writing-assistance-apis/blob/main/README.md
SpecificationNone yet, but looking forward to writing one
Summary
A JavaScript API for transformin
20 matches
Mail list logo
