W3C home > Mailing lists > Public > public-web-intents@w3.org > July 2012

[Bug 17792] New: The draft says Intent Markup's type attribute must be space-separated but examples are comma-separated

From: <bugzilla@jessica.w3.org>
Date: Tue, 17 Jul 2012 11:36:51 +0000
To: public-web-intents@w3.org
Message-ID: <bug-17792-5094@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17792

           Summary: The draft says Intent Markup's type attribute must be
                    space-separated but examples are comma-separated
           Product: Web Intents
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Intents specification
        AssignedTo: jhawkins@google.com
        ReportedBy: kinuko@chromium.org
         QAContact: dave.null@w3.org
                CC: mike@w3.org, public-web-intents@w3.org,
                    paulkinlan@google.com, gbillock@google.com


In the latest editor's draft
(https://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview-respec.html#attributes-2)
the type attribute is defined as 'space separated list' as following:

3.5.1 Attributes
type of type DOMString
A string specifying the type of payload data the service can accept. Must be a
space separated list of type specifiers.

But the example 3 in 1.1 Example shows following markup:

<intent action="http://webintents.org/edit"
type="text/uri-list;type=image/*,image/*"></intent>

where the type attribute seems to be separated by a comma (unless the entire
string should be parsed as a single type specifier), which looks confusing.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 17 July 2012 11:37:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 July 2012 11:37:05 GMT