24238 2014-01-08 14:13:54 +0000 Should the tokens in HTMLAnchorElement.ping be resolved? 2014-01-16 18:58:51 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#reflecting-content-attributes-in-idl-attributes P3 normal Unsorted 1 contributor ian ian mike Ms2ger contributor oldest_to_newest 98131 0 contributor 2014-01-08 14:13:54 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html Multipage: http://www.whatwg.org/C#reflecting-content-attributes-in-idl-attributes Complete: http://www.whatwg.org/c#reflecting-content-attributes-in-idl-attributes Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Should the tokens in HTMLAnchorElement.ping be resolved? Posted from: 91.180.161.203 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 98143 1 ian 2014-01-08 19:21:22 +0000 If we resolved them, the underlying attribute would change all the tokens as soon as you did anything. That seems like it'd be bad. We could have a readonly interface that exposed the resolved URLs, I guess? I don't really understand the use cases here. The use case for editing the ping="" attribute is to add new values when you find out you should notify someone (e.g. when you're adding something dynamically and have two things to notify); what's the use case for reading the values?