28697 2015-05-25 14:43:00 +0000 BarProp.visible can be readonly 2015-09-01 20:28:14 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED https://html.spec.whatwg.org/#browser-interface-elements P3 normal Unsorted 1 contributor ian annevk bzbarsky mike philipj contributor oldest_to_newest 120467 0 contributor 2015-05-25 14:43:00 +0000 Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#browser-interface-elements Complete: https://html.spec.whatwg.org/#browser-interface-elements Referrer: Comment: BarProp.visible can be readonly Posted from: 212.116.72.179 User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2376.0 Safari/537.36 OPR/31.0.1857.0 (Edition developer) 120468 1 philipj 2015-05-25 14:45:45 +0000 The spec says "On setting, the new value must be discarded" but in Blink and WebKit, BarProp.visible is simply readonly. Since this appears to be web compatible, I propose doing the same in the spec. 122967 2 annevk 2015-09-01 10:13:28 +0000 It seems in Gecko the setter only does something in Chrome code. So I guess Firefox could make this readonly too, unless I read http://mxr.mozilla.org/mozilla-central/source/dom/base/BarProps.cpp#68 incorrectly. Copying bz for verification. 122999 3 bzbarsky 2015-09-01 17:29:47 +0000 We could do that, yes. It's a behavior change in strict mode (to throw instead of silently doing nothing), but as long as we're sure that's web compatible... 123000 4 annevk 2015-09-01 17:50:38 +0000 Yeah, that seems like a small risk given that Chrome already implements it this way and this is very old. Thank you. https://github.com/whatwg/html/commit/78f102944f276919251d8a057052edbca4ee1e0c 123004 5 bzbarsky 2015-09-01 20:28:14 +0000 Actually, we'll need to figure out how to implement this in Gecko... it'll take some nontrivial binding surgery to do it right, unfortunately. :(