Maybe it's possible that the `display:none` setter script can run after this microtask (i.e., the decision to lazy load) runs tho?
We could make the test more explicit by creating the image in script, and setting `display: none` synchronously after creation. Then add it to the DOM.
February 14, 2025 at 9:35 PM
Maybe it's possible that the `display:none` setter script can run after this microtask (i.e., the decision to lazy load) runs tho?
We could make the test more explicit by creating the image in script, and setting `display: none` synchronously after creation. Then add it to the DOM.
I don't think it's flaky bc the decision to lazyload (html.spec.whatwg.org#updating-the...) is made *after* this microtask (html.spec.whatwg.org#updating-the...) runs during loading. And I think the script where we set `display:none` always runs before this decision is made. Does that make sense?
I don't think it's flaky bc the decision to lazyload (html.spec.whatwg.org#updating-the...) is made *after* this microtask (html.spec.whatwg.org#updating-the...) runs during loading. And I think the script where we set `display:none` always runs before this decision is made. Does that make sense?
Do you think it’s a defense mechanism so they can preemptively avoid getting “called out” for using AI art (some see it as cheating), or more so people are trying to subtly flash that they’re on the new trend of using AI art?
May 26, 2023 at 1:02 AM
Do you think it’s a defense mechanism so they can preemptively avoid getting “called out” for using AI art (some see it as cheating), or more so people are trying to subtly flash that they’re on the new trend of using AI art?