| 01:12 | <domfarolino> | Is there a way to determine when an image has _started_ to load? My understanding is the loadstart event is gone (and probably wasn't interoperable before removal) |
| 01:15 | <domfarolino> | I'm stepping to XY problem territory. Let me ask the real question: Is there a way, without test.step_timeout or equivalents, to test that a resource _doesn't load_ on a page (specifically an image)? |
| 01:25 | <Domenic> | P35: meta charset and title are necessary. html and head tags are useless (optional). |
| 01:25 | <Domenic> | domfarolino: I've always used timeouts for such tests |
| 01:29 | <domfarolino> | Gotcha. Wasn't sure how discouraged they were |
| 03:18 | <Domenic> | I mean, they're discouraged if there's a better way, but if there isn't one, what can you do |
| 04:19 | <domfarolino> | True 👍 |
| 09:31 | <annevk> | domfarolino: for lazy loading you want to test that the body load event is dispatched and the image is not loaded |
| 09:31 | <annevk> | domfarolino: don’t think timeouts are needed there per se |
| 13:46 | <domfarolino> | annevk: I believe some of the general tests are doing that yes, however one test I am reviewing right now is testing that if you remove a loading=lazy image from the DOM and scroll to where it was, it won’t start loading. |
| 17:06 | <domfarolino> | annevk: It is true that a request's tainted origin flag is only set for A -> B -> !B requests, right? |
| 17:45 | <annevk> | domfarolino: I think so |