This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24238 - Should the tokens in HTMLAnchorElement.ping be resolved?
Summary: Should the tokens in HTMLAnchorElement.ping be resolved?
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-08 14:13 UTC by contributor
Modified: 2014-01-16 18:58 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-01-08 14:13:54 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2014-01-08 19:21:22 UTC 
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?