LGTM3
I think there's some interop risk here if Apple and Mozilla won't add
support for explicit "auto" values and developers would start using them,
but I agree that there's no real incentive for developers to do so.
On Mon, Oct 24, 2022 at 4:47 PM Mike Taylor wrote:
> LGTM2
>
> On 10/19/22
LGTM2
On 10/19/22 8:38 AM, Philip Jägenstedt wrote:
Thanks Munira for the detailed explanation, and thanks for filing the
Gecko and WebKit bugs!
I think that from a web developer's point of view, this won't be a
feature that you actively use, but sensible defaults and the lack of a
Thanks Munira for the detailed explanation, and thanks for filing the Gecko
and WebKit bugs!
I think that from a web developer's point of view, this won't be a feature
that you actively use, but sensible defaults and the lack of a surprising
behavior/bug. Thanks for sorting that out!
LGTM1
On
Hi Yoav,
Thank you for your comments. Here are some of the answers to your questions
from the chat:
> What would Firefox/Safari do when users start using the "auto" value? Are
they planning to add support for it?
When they cannot parse the “auto” value they will use the default value,
which for
Hi Yoav,
On Wed, Oct 19, 2022 at 6:52 AM Yoav Weiss wrote:
>
>
> On Tue, Oct 18, 2022 at 5:27 PM 'Munira Tursunova' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> Contact emails
>>
>> moon...@chromium.org, dr...@chromium.org
>>
>> Explainer
>>
>>
On Tue, Oct 18, 2022 at 5:27 PM 'Munira Tursunova' via blink-dev <
blink-dev@chromium.org> wrote:
> Contact emails
>
> moon...@chromium.org, dr...@chromium.org
>
> Explainer
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=973194
>
That's restricted to Google folks, so not great as a
Contact emails
moon...@chromium.org, dr...@chromium.org
Explainer
https://bugs.chromium.org/p/chromium/issues/detail?id=973194
https://drafts.csswg.org/css-fonts/#font-prop-desc
Specification
https://drafts.csswg.org/css-fonts/#font-prop-desc
Summary
Auto range support for variable fonts
