28575 2015-04-28 00:05:17 +0000 Shouldn't `ping` be readonly? 2015-08-28 05:23:54 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED https://html.spec.whatwg.org/#htmlanchorelement P3 normal Unsorted 1 contributor ian annevk ian mike n.oxyde zcorpan contributor oldest_to_newest 119966 0 contributor 2015-04-28 00:05:17 +0000 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 120107 1 ian 2015-05-05 21:40:07 +0000 Why would it be readonly? Wouldn't that mean you couldn't set it (using the [PutForwards] facility)? 120141 2 zcorpan 2015-05-06 17:59:36 +0000 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 122689 3 n.oxyde 2015-08-20 23:34:20 +0000 Is there anything blocking the change here? 122691 4 mike 2015-08-21 00:05:49 +0000 (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. 122819 5 annevk 2015-08-28 05:23:54 +0000 Thank you, fixed. https://github.com/whatwg/html/commit/29578b4cb3f79aaaa3401b5f7e800867edba0ee8