| • Niedzielski | |
| Jul 11 2018, 5:27 PM |
| F23621355: Screenshot from 2018-07-11 12-26-03.png | |
| Jul 11 2018, 5:27 PM |
Browser Version
OS Version
Device Model
Device Language
What does "eagerly loaded" mean in this context? I'm not understanding the bug here.
Right now images will be lazily load as soon as they are scrolled into view. Are you saying that they should be loaded by some other heuristic?
Also, note that usually sections are collapsed by default. I'm only seeing flags downloaded when the sections they are in are expanded and scroll past them, but that seems expected behaviour to me.
We do have wgMFLazyLoadSkipSmallImages which will not lazy load small icons, but at some point we decided not to use this (see declined T128897), as there is evidence that these additional HTTP requests can throttle first paint and we didn't have the time or resources to investigate. Note, there is also evidence that loading them can cause performance issues (T185835). Is this what you are suggesting we do?
By "eager" I meant simply the opposite of "lazy." I was mistakenly thinking that small images were meant to be omitted and wasn't aware of the tickets you referenced.
Okay got it. Is there some way in the code/project page we can document this so it's more obvious? It has come up a few times before as unexpected.
@Jdlrobson, nope. In my mind, this was a longstanding bug that I had just never gotten around to filing a ticket for so I probably wouldn't have checked said page! D: