Samuel Mannehed (ThinLinc team)
Samuel Mannehed (ThinLinc team)
My thoughts were option 1, I actually have a prototype that works for ESound which uses Web Audio API, but that's quite an outdated protocol..
Nope, i meant Web Audio API. I made it last year. I used ESound since it is a very simple protocol and I was mostly after a PoC.
@ikreymer I'm afraid it's not open source, but I don't think the EsounD solution is worth much. I'm currently not working on this however. One issue I see with implementing...
@ikreymer I had a discussion with my boss about the EsounD solution. We decided to make the client-side open. You can find the patch attached to the following bug: https://www.cendio.com/bugzilla/show_bug.cgi?id=4822...
:+1: Microsoft Edge on Windows 10 also complains in a similar way.
Well, unless I'm missing something here - the obvious reason for witching to getBoundingClientRect() would be to get the actual rendered screen size as one would expect from that function?...
Looking at the commit that made the change ab1ace38, I'd guess that offsetWidth/offsetHeight can't handle fractional sizes. Is that so @CendioOssman? If that's the case, we're somewhat stuck with that...
Same issue exists with v1.2.0, this is not a regression.
We have noticed this issue in normal use cases, that did not involve iframes, on two of our devices. We saw it in Edge on Windows 10, and in Safari...
No, the only way is to either alter the javascript or to use fragment or query parameters.