51–60 of 140 posts
Might as well link to the original / "stolen from" author's equivalent demo with Three.js (open this in multiple overlapping windows) - https://bgstaal.github.io/multipleWindow3dScene/ - and repo - https://github.com/bgstaal/multipleWindow3dScene/
Am I the only one that's horrified that window.screenX and window.screenY exist? This is not information that I want to provide.
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.
More like this: - https://twitter.com/steveruizok/status/1727625036159234555 - https://twitter.com/_nonfigurativ_/status/172732259457002734... - https://twitter.com/wesbos/status/1727755227766350031 - https://twitter.com/wesbos/status/1727722358465523721
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.
Earlier quoted context omitted.
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?
Because fingerprinting. Shit like this is the reason you are supposed to use the Tor browser only with a tiny window.
I hadn't ever heard of this. Here is a statement from the Tor project for anyone else wondering what this is about:
> We automatically resize new browser windows to a 200x100 pixel multiple based on desktop resolution which is provided by a Firefox patch. To minimize the effect of the long tail of large monitor sizes, we also cap the window size at 1000 pixels in each direction. In addition to that we set privacy.resistFingerprinting to true to use the client content window size for window.screen, and to report a window.devicePixelRatio of 1.0. Similarly, we use that preference to return content window relative points for DOM events. We also force popups to open in new tabs to avoid full-screen popups inferring information about the browser resolution. In addition, we prevent auto-maximizing on browser start, and inform users that maximized windows are detrimental to privacy in this mode
But… why does it lag? Shouldn’t this be trivial enough to be instant?