A claim about importance and position rather than a fetch mechanism, which
is why it is the description’s to make: only the app knows whether a picture
is the first thing on the screen or the fortieth thing down a list.
§Eager is the default, and that is a correctness choice
0.21.0 emitted the webview’s loading="lazy" for every picture, on the
evidence that the one consumer measured wrote it. That was reading a habit
as a rule. Deferring a picture that is on screen at first paint does not
save anything – it is needed immediately either way – and it delays the
arrival, so the space it eventually takes is claimed later and the shift is
more visible, not less.
So the safe answer is the default and the optimisation is opted into. A
carousel is the case that proves the two cannot be one setting for the
renderer to choose: its first frame is on screen and its other frames are
not, in the same widget, at the same moment.
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.