W3C home > Mailing lists > Public > public-html-admin@w3.org > March 2013

[Bug 21439] New: Update the MAY-section with algorithm for how to turn invalid URL into text

From: <bugzilla@jessica.w3.org>
Date: Fri, 29 Mar 2013 21:55:16 +0000
To: public-html-admin@w3.org
Message-ID: <bug-21439-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21439

            Bug ID: 21439
           Summary: Update the MAY-section with algorithm for how to turn
                    invalid URL into text
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
               URL: http://www.w3.org/TR/2013/WD-html-longdesc-20130312/#l
                    ongdesc
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML Image Description Extension
          Assignee: chaals@yandex-team.ru
          Reporter: xn--mlform-iua@xn--mlform-iua.no
        QA Contact: public-html-bugzilla@w3.org
                CC: public-html-admin@w3.org,
                    xn--mlform-iua@xn--mlform-iua.no

The current permission to interpret the longdesc attribute content as text when
it is an invalid URL, does not tell how to do this. 

]] user agents may make that content available to the user. This is because a
common authoring error is to include the text of a description, instead of the
URL of a description, as the value of the attribute. [[

I believe this should follow a specified algorithm which FIRST checks if the
string can reasonably (e.g. if there are many unescaped spaces etc) be
interpreted as text and SECOND runs a transformation which turns the text into
a data URI which the user agent then opens as an external page (external URL -
URL to external page).

When generating the data URI, the data URI should contain a HTML document which
should be UTF-8 encoded and which should inherit the language tags of the
current page, if any. The title element of the data URI document should say
'long image description' or something like that.

Justification: To define the MAY option like this, would undescore that
longdesc is never the less an URL. It would also point out that longdesc can
contain a data URI.  On the opposit side, as the spec stands, I find that the
fact that longdesc is an URL is underminded - it is "kindness" in the wrong
way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 29 March 2013 21:55:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:57:22 UTC