[Bug 24026] Document that URLs (destinationURL) should/may be validated and/or normalized

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24026

--- Comment #1 from David Dorwin <ddorwin@google.com> ---
As clarified in the telecon, there are 3 levels of proposal:
1) Implementations *may* validate and/or normalize URLs; applications should
not expect the string to be exactly the same across user agents.
  * This is required IMO since implementations will do this internally when
representing URLs by objects.
2) Implementations *should* validate and/or normalize URLs.
  * It would be helpful to have a definition to point to.
  * Even if we don't have a definition and the outcome may differ in some
corner cases, there may be value in all implementations filtering out
commonly-recognized issues or invalid URLs.
  * If/when URL is defined, this could be the implied definition or the spec
could be revised to point to it.
3) Use an explicit URL type in the definition (i.e. URL instead of DOMString).
  * This would implicitly validate and normalize the URL according to that
definition.
  * This is perhaps the most desirable solution, but this may be a ways out as
the URL spec is controversial.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 10 December 2013 17:15:03 UTC