On 01/12/2015 11:29 AM, Pavel Grunt wrote: > Problem was in my server, now I am able to test IE so I will send v3 soon. Great, thanks. And yeah, IE support is dicey at best. I think the ideal is that we at least downgrade functionality gracefully, instead of failing. I have been playing with your patches, and they seem to work nicely. I'll try to comment more formally on the v3 set. My remaining comments have less to do with your patches, than with the whole process. I have to confess I'm pretty ignorant of the whole file transfer function. There are some ways it behaves that seem less than ideal. There is no progress bar, I take it? And do we really transmit in that small a chunk size? And we preallocate the whole file before filling in the bytes? I worry that the net result is going to be (and is currently) potentially confusing. I drop a 4G file on my browser. Nothing happens. I drop it again. Now I've started a many hour process that's going to run in the background. Also, on the file preallocation, I worry that I'll go look, think the file is complete (because the size is right), and then copy off a corrupt version... Do I understand correctly, or have I just horribly mis-configured my agent? Cheers, Jeremy > > Pavel >> >> Hi Jeremy, >> >> Thank you. You are right about the MediaSource API, spice-html5 in >> IE11 gets other errors like Channel type 0 unknown, Channel type 177 >> unknown and after that it even kills my VM. >> > _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel