81–90 of 140 posts
Earlier quoted context omitted.
Probably because of websocket network lag and also, in my anecdotal experience, window position updates are sometimes strangely jittery
Why is it over a websocket? Can't it just share local data?
Could someone explain what this means ? ( I’m not even sure I understand the gif on the GitHub page ) I just see windows seemingly sharing data.
I'm wondering about practical application of this demo...
This maybe be something that can achieve that.
That's a great demo! I'd be curious to see how this would work with multiple monitors. Also, thank you for voluntarily acknowledging that you were directly inspired by somebody else and giving them credit - the software industry could use more people like you.
What, thieves? Make your stuff from zero, like the rest of us!
Earlier quoted context omitted.
Using the demo in https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/... it seems Firefox pretends the window is always at (0,0). So that's nice.
You likely have `privacy.resistFingerprinting` set to true.
people forget lesson from recent past. i don't know when google strong armed w3c to include this back... but we had this since ie4 days and then disabled everywhere since it was abused left and right for click jacking attacks.
Am I the only one that's horrified that window.screenX and window.screenY exist? This is not information that I want to provide.
Sorry, i'm a little lost. I tried thinking about it, but I can't think of any nefarious attacks someone could do with screenX/Y. Why is that such a risk? What could they possibly learn from that other than screen size?
click jacking is always fun.
But… why does it lag? Shouldn’t this be trivial enough to be instant?
I wonder if it would be more instant if they used postMessage api instead of going over network.
My personal theory about the lag is that positioning the window is not synchronized to the JS thread, so the window moves before the JS thread is aware, which means you see the square move after the window has already moved.
Earlier quoted context omitted.
Probably because of websocket network lag and also, in my anecdotal experience, window position updates are sometimes strangely jittery
Why is it over a websocket? Can't it just share local data?
> The original work by Bjorn Staal used localStorage, but I found sockets more fun, because if tweaked a bit, this can be shared with friends.