We're evolving to serve you better! This current forum has transitioned to read-only mode. For new discussions, support, and engagement, we've moved to GitHub Discussions.

Problem with lazy loading in Safari using the TechNews v.2.0.0.0 template

November 26, 2019 at 6:00 pm #856

[anonymous]

Hi there,

I tested the Technews template under Chrome, Firefox and Safari. It works fine on Chrome and Firefox but I experienced a problem with lazy loading on Safari (Mac).

It looks like if a script was constantly running as the computer heats up when displaying a TechNews web page on safari. I disabled the lazy loading and the energy consumed by the page decreased to a standard value.

It might come from Safari though, as I know there are incompatibilities with some LL scripts.

I do not have the problem with other templates.

I am using Safari 13.0.3 under macOS Catalina version 10.15.1.

Regards

November 27, 2019 at 2:45 pm #861

Bob

Hi,

I’ve tested it on Safari 12.0.3 and I didn’t notice any symptoms you write about.

November 27, 2019 at 4:12 pm #866

[anonymous]

I’m using the same template with Publii 0.35.3 on a gitlab host and have no issue at all on Safari 13.0.3. Here is a tree of my loading files and you can see that lazy load works really good.

November 27, 2019 at 7:38 pm #882

[anonymous]

Hello,

thanks for your comments.

I am running the template on a dedicated remote server. I only have a couple of test blog items created. One of them has several images.

I drilled down a bit to understand what happened. Not sure it’s the lazy loading per say. It might be a problem with the continuous scroll too.

Below are the energy consumption diagrams on my MacBook Air.

1 and 2 show the energy consumed when displaying the page in safari. “On” means that the Publii tab is selected (when the tab is not selected I select another one displaying a standard web page). These two diagrams are to compare with 4 (Firefox). Note that 2 is consuming twice as much as 1 (the lazy loading makes the difference) and that the level of energy represents a very loaded cpu.

Fig 3 shows a sequence where I refreshed the page without placing the cursor on the page and then moved the cursor in a scroll zone on the page. This triggered the energy consumption which did not disappear at the second display, even without the cursor in the zone.

Regards