[Bug 21678] i18n-ISSUE-251: Invalid content in longdesc

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

--- Comment #4 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
Perhaps the i18n IG and Charles could consider this:

While I stand on i18n’s side, still, in the 11th comment in bug 21439, I hinted
that fixing could be fully permitted provided that the bar is high enough.

And the URL standard defines such a bar - namely, URL parsing failure. See:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21439#c11

If I understand the URL standard correctly, then, for 

    longdesc="foo bar baz"

the spaces would *not* cause a parsing failure, but would instead pass/parse as
a URL.

By formally allowing such fixing to take place, but only with a very high bar,
we may gain better interoperability with regard to when it (by default) is
permitted as well as with regard to how it is perfomed when it (by default or
by user preference) is performed.

I also think that this bar is so high, that the MAY could be fully justified.

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

Received on Thursday, 2 May 2013 02:37:27 UTC