This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Or should they have a no-op setter? The difference is that readonly throws an exception on set in strict mode. This testcase: <script> "use strict"; try { window.innerWidth = 0; alert("REACHED"); } catch (e) { alert(e); } </script> alerts "REACHED" for me in IE9, Gecko, Presto, Blink, and WebKit, so it seems a bit worrisome to suddenly make this case throw... esp in quirks mode.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3483 Gecko has a no-op setter WebKit/Blink/Presto have [Replaceable] IE11 throws. Rossen, have you found Web compat problems for throwing here? Test for all attributes on Window in CSSOM View: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3484
Hmm, now I get no-op setter for everything in IE11 (except scrollX/scrollY which are not supported.) http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3486 Feature Gecko Blink WebKit IE11 Presto screen T N R N R innerWidth N R R N R innerHeight N R R N R scrollX R R R S R pageXOffset T N T N R scrollY R R R S R pageYOffset T N T N R screenX N R R N N screenY N R R N N outerWidth N R R N N outerHeight N R R N N devicePixelRatio T R R N N T = TypeError N = no-op setter R = [Replaceable] S = not supported
Does it seem OK to make all of these [Replaceable] ? That's closest to WebKit and seems like it has the least potential of breaking scripts that set these to something and then expect to get the value they set it to.
I could probably live with that.
https://github.com/w3c/csswg-drafts/commit/6a4f24fe558bb3e76d77a499575ac81ba2a5c369