Any plans to bring this feature in Pale moon?
https://bugzilla.mozilla.org/show_bug.cgi?id=1535749
https://chromestatus.com/feature/5645767347798016
https://github.com/whatwg/html/issues/2 ... -378831265
https://addyosmani.com/blog/lazy-loading/
Lazy Loading in Pale Moon Topic is solved
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Re: Lazy Loading in Pale Moon
Sorry no. There's no reason to spend time on this non-feature.
We already don't decode/render images that aren't "almost in view" for optimal resource use.
We also offer plenty of JS features for websites to use to lazy-load any element, including the recently-added IntersectionObservers and e.g. srcset for images.
Additionally, this would provide yet another way to track user's movements within pages without scripting.
I also think this may cause severe page performance and reflow issues because intrinsic image sizes aren't known before loading.
We already don't decode/render images that aren't "almost in view" for optimal resource use.
We also offer plenty of JS features for websites to use to lazy-load any element, including the recently-added IntersectionObservers and e.g. srcset for images.
Additionally, this would provide yet another way to track user's movements within pages without scripting.
I also think this may cause severe page performance and reflow issues because intrinsic image sizes aren't known before loading.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite