Definitions related to image loading are not precise

[yoavweiss]

In 3.7 step 1.2, "fully decoded" should probably be fully decodable

There are also references to "completely available" which may fire earlier than we would like - when the image dimensions are known, rather than when it's fully decoded.

@npm1 - thoughts?

[npm1]

Oh hmm reading more what fully decodable says I think it implies that the image is ready to be decoded but is not necessarily decoded yet, so I don't think that works for the purposes of Element Timing. Here, we want to know when the image has already been fully decoded.

Regarding the latter part, I do think we could replace completely available with fully decodable since the latter better captures when the image is 'loaded'. I think the main difference is that this would exclude images which having decoding problems from being reported (which I think is pretty reasonable).