- From: Philip Jägenstedt <web-platform-tests-notifications@w3.org>
- Date: Fri, 11 Mar 2016 03:30:19 GMT
- To: public-web-platform-tests-notifications@w3.org
@zcorpan, what you quoted is for the internal [track URL](https://html.spec.whatwg.org/multipage/embedded-content.html#track-url) concept, while this is what the spec says about [reflecting](https://html.spec.whatwg.org/multipage/infrastructure.html#reflect): > If a reflecting IDL attribute is a DOMString attribute whose content attribute is defined to contain a URL, then on getting, the IDL attribute must parse the value of the content attribute relative to the element's node document and return the resulting URL string if that was successful, or the empty string otherwise; and on setting, must set the content attribute to the specified literal value. If the content attribute is absent, the IDL attribute must return the default value, if the content attribute has one, or else the empty string. So this looks like a spec bug, it doesn't make any sense to resolve the empty string during reflection if that isn't the URL that will be used. It looks like we have the same problem with `HTMLMediaElement`, which is also `[Reflect, URL] attribute DOMString src` in Blink's IDL. Should we change the spec, or just reflect all URLs in the same way for simplicity, even though it doesn't make sense? View on GitHub: https://github.com/w3c/web-platform-tests/pull/2663#issuecomment-195163416
Received on Friday, 11 March 2016 03:30:29 UTC