29577 2016-04-19 23:38:34 +0000 "The screenX attribute must return the x-coordin..." 2016-08-28 06:20:56 +0000 1 1 1 Unclassified CSS CSSOM View unspecified PC All RESOLVED FIXED P2 normal --- 1 w3bugs zcorpan public-css-bugzilla oldest_to_newest 125931 0 w3bugs 2016-04-19 23:38:34 +0000 https://drafts.csswg.org/cssom-view/#dom-window-screenx [[ The screenX attribute must return the x-coordinate, relative to the origin of the screen of the output device, of the left of the client window as number of pixels, or zero if there is no such thing. The screenY attribute must return the y-coordinate, relative to the origin of the screen of the output device, of the top of the client window as number of pixels, or zero if there is no such thing. ]] As a user, I don't feel that webpages have any business knowing where their window is located on my screen. I would like the spec to allow privacy-conscious browsers to pretend that all windows are always at the top-left of the screen, thus plugging this information leak. 125932 1 dbaron 2016-04-19 23:48:51 +0000 (This could even be discussed in the "Privacy Considerations" section of the spec that bikeshed keeps telling you to create.) 126146 2 zcorpan 2016-04-26 09:11:48 +0000 Privacy considerations section is https://www.w3.org/Bugs/Public/show_bug.cgi?id=29533 126147 3 zcorpan 2016-04-26 09:30:46 +0000 There's also mouseevent.screenX, screen.availWidth, screen.width (and heights). I agree we should allow browsers to lie about the screen, but we should probably do so across the board; e.g. also the 'device-width' media feature. For window.open()ed windows, where the author has given position and size in the "features" argument, the browser can also adjust the position and size so that the window will fit in the screen, which again would leak the size of the available space of the screen... 126148 4 zcorpan 2016-04-26 09:46:20 +0000 Ah you had filed bugs about those also, thanks! https://www.w3.org/Bugs/Public/show_bug.cgi?id=29578 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29579 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29580 127228 5 zcorpan 2016-08-25 12:23:26 +0000 https://github.com/w3c/csswg-drafts/commit/dc36ecd7a46b173f958dafa736a84eb9753afb7b 127232 6 zcorpan 2016-08-25 12:27:24 +0000 Any thoughts about whether window.open() should use the new concepts? 127233 7 zcorpan 2016-08-25 12:32:12 +0000 (In reply to Simon Pieters from comment #3) > e.g. also the 'device-width' media feature. https://github.com/w3c/csswg-drafts/issues/426 127250 8 w3bugs 2016-08-28 06:20:56 +0000 (In reply to Simon Pieters from comment #6) > Any thoughts about whether window.open() should use the new concepts? Sounds reasonable. Would be less vague than the current "the available space" wording.