| 07:59 | <annevk> | mkwst: "I think that it's reasonable that the capture-ability of videos and images is controlled by the document that embeds them." you might wanna chime in at https://github.com/w3c/mediacapture-screen-share/pull/148 |
| 11:33 | <croraf> | Anyone can point me to the chapter how image_element.src and image_element in general works. I was checking HTML spec about <img> tag but does not contain what I need. Is there any other chapter? |
| 11:34 | <croraf> | Specifically I don't know how does image.src=""; image.src=newSource; |
| 11:34 | <croraf> | clear the image source inbetween, even though this is done in a single thread. |
| 11:46 | <annevk> | croraf: did you find "update the image data" and callers? |
| 11:46 | <annevk> | croraf: that's basically it, going from memory |
| 11:55 | <croraf> | I don't see that string "update the image data" |
| 11:55 | <croraf> | annevk, |
| 12:06 | <annevk> | croraf: it's in the single-page version for sure |
| 12:22 | <croraf> | I see. Indeed. When checking the multipage version, you have 4.8 as one page |
| 12:22 | <croraf> | * 4.7 as one page, then you go to 4.8 page |
| 12:22 | <croraf> | But it holds only 4.8.1, 4.8.2 and 4.8.3 |
| 12:22 | <croraf> | 4.8.4 Images is a separate page |
| 15:13 | <croraf> | I notice two things in chrome's behavior. First, when I move through the links on the same site (I'm modifying the history) that sometimes Chrome caches some images and just shows them, doesn't even try to make the request. While most of the time it does the request (but just returns it from its cache immediately). |
| 15:13 | <croraf> | I'm not sure what is this behavior. |