17:15
<domfarolino>
annevk: Do you think you’ll have time this week for another pass on the lazyload PR?
17:15
<annevk>
domfarolino: for sure, didn't realize it was blocking on me
17:16
<annevk>
domfarolino: do we have tests?
17:16
<annevk>
domfarolino: I put a reminder in for tomorrow
17:16
<domfarolino>
annevk: np. Some, not all. Rob is writing some, I may be able to write others soonish
17:17
<domfarolino>
Cool thank you
17:17
<annevk>
domfarolino: I guess part of the question is if we now have unambiguous wording for the various tests we imagined
17:18
<annevk>
domfarolino: including constructing the image outside the tree and such
17:21
<domfarolino>
annevk: Yeah, I believe we do but I also want to take another look. RE outside-the-tree, I believe said image is not considered intersecting the viewport, but I also don’t know much about “CSS boxes”
17:22
<annevk>
domfarolino: ah yeah, that algorithm (if generalized from video) would return false so lazyload would kick in I guess, which is nice
17:22
<annevk>
anyway, tomorrow 🙂
17:23
<domfarolino>
(for explicitly loading=lazy adorned images, that is)
17:23
<domfarolino>
Sg!
18:45
<annevk>
Heh, MDN didn't care to document ProcessingInstruction
18:45
<annevk>
Or at least not in a way that MikeSmith's annotator picked up
21:35
<domfarolino>
annevk: Could a visibility:hidden image "intersect" with the viewport? from reading around, I believe the answer is yes.
21:42
<astearns>
domfarolino: I expect it should - it's still taking up a defined space
21:43
<domfarolino>
astearns: That is what I think too, thanks. I think display:none would never "intersect" the viewport however
21:45
<astearns>
that's my expectation, too
21:45
<astearns>
(standard caveat about applying logic)
21:54
<MikeSmith>
annevk: if the annotator didn't pick it up, that's either because there's no MDN article for it, or else because there is an MDN article, but it has no link to the DOM spec