This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#htmlanchorelement Complete: https://html.spec.whatwg.org/#htmlanchorelement Referrer: Comment: Shouldn't `ping` be readonly? Posted from: 88.182.187.128 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/600.1.17 (KHTML, like Gecko) Version/7.1 Safari/537.85.10
Why would it be readonly? Wouldn't that mean you couldn't set it (using the [PutForwards] facility)?
No, in fact you have to use readonly to use [PutForwards]. > The [PutForwards] extended attribute must not be used on an attribute that is not read only. http://heycam.github.io/webidl/#PutForwards
Is there anything blocking the change here?
(In reply to Anthony Ramine from comment #3) > Is there anything blocking the change here? I think there isn’t—it's just that right now the process for getting fixes made in the spec is bit slow. So if this is blocking you on anything, I think the best strategy for the time being is to ask for feedback about in on #whatwg and/or on whatwg@whatwg.org, and then just proceed with what you need to do, based on whatever the prevailing agreement there seems to be from the people you discuss it with there.
Thank you, fixed. https://github.com/whatwg/html/commit/29578b4cb3f79aaaa3401b5f7e800867edba0ee8