Regarding lazily loading CSS background images, Chromium determines whether
or not to lazily load CSS background images according to the default lazy
loading behavior, and isn't directly controlled by the "loading" attribute.
There are some heuristics involved, e.g. background images inside an
Apologies, it seems I spread some misinformation about CSS background
lazy loading, which Scott rectified.
On 10/29/19 12:36 AM, Maciej Stachowiak wrote:
On Oct 28, 2019, at 3:08 PM, Rob Buis wrote:
On 10/28/19 9:07 PM, Maciej Stachowiak wrote:
Yet another possible task is making lazy
Regarding lazily loading CSS background images, Chromium determines whether
or not to lazily load CSS background images according to the default lazy
loading behavior, and isn't directly controlled by the "loading" attribute.
There are some heuristics involved, e.g. background images inside an
> On Oct 28, 2019, at 3:08 PM, Rob Buis wrote:
>
> On 10/28/19 9:07 PM, Maciej Stachowiak wrote:
>
>>> Yet another possible task is making lazy loading work for CSS backgrounds,
>>> this is implemented in the prototype but I don't think there are many tests
>>> for it.
>> Is there a way for
On 10/28/19 9:07 PM, Maciej Stachowiak wrote:
Yet another possible task is making lazy loading work for CSS backgrounds, this
is implemented in the prototype but I don't think there are many tests for it.
Is there a way for content authors to opt in/out (depending on the default), or
does
> On Oct 28, 2019, at 11:39 AM, Rob Buis wrote:
>
> Hi,
>
> I made a lazy image loading prototype earlier this year
> (https://bugs.webkit.org/show_bug.cgi?id=196698) and have been splitting it
> up into reviewable patches. The main implementation part landed recently so I
> am wondering
On Mon 28. Oct 2019 at 20:02 Simon Fraser wrote:
> > On Oct 28, 2019, at 11:39 AM, Rob Buis wrote:
> >
> > Hi,
> >
> > I made a lazy image loading prototype earlier this year (
> https://bugs.webkit.org/show_bug.cgi?id=196698) and have been splitting
> it up into reviewable patches. The main
> On Oct 28, 2019, at 11:39 AM, Rob Buis wrote:
>
> Hi,
>
> I made a lazy image loading prototype earlier this year
> (https://bugs.webkit.org/show_bug.cgi?id=196698) and have been splitting it
> up into reviewable patches. The main implementation part landed recently so I
> am wondering
I support unprefixing!
Simon
> On Oct 28, 2019, at 11:55 AM, Dirk Schulze wrote:
>
> Hi,
>
> I didn’t hear any objections to unprefix -webkit-clip-path. Unless no new
> concerns get raised, I’ll land the patch later this week.
>
> Greetings,
> Dirk
>
>> On 21. Oct 2019, at 13:01, Dirk
Hi,
I didn’t hear any objections to unprefix -webkit-clip-path. Unless no new
concerns get raised, I’ll land the patch later this week.
Greetings,
Dirk
On 21. Oct 2019, at 13:01, Dirk Schulze
mailto:dschu...@adobe.com>> wrote:
Hi,
I’d like to unprefix the -webkit-clip-path implementation.
Hi,
I made a lazy image loading prototype earlier this year
(https://bugs.webkit.org/show_bug.cgi?id=196698) and have been splitting
it up into reviewable patches. The main implementation part landed
recently so I am wondering about the next steps.
One thing left to do for sure is cleaning
11 matches
Mail list logo