This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13496 - How about "if the type contains a SLASH (/) it should be treated as a MIME type. Otherwise, if it contains a FULL STOP (.) it should be treated as a UTI, otherwise it is invalid.
Summary: How about "if the type contains a SLASH (/) it should be treated as a MIME ty...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-01 09:33 UTC by contributor
Modified: 2011-08-16 01:30 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-08-01 09:33:02 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html
Multipage: http://www.whatwg.org/C#attr-hyperlink-type
Complete: http://www.whatwg.org/c#attr-hyperlink-type

Comment:
How about "if the type contains a SLASH (/) it should be treated as a MIME
type. Otherwise, if it contains a FULL STOP (.) it should be treated as a UTI,
otherwise it is invalid.

Posted from: 213.120.126.47
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.50 (KHTML, like Gecko) Version/5.1 Safari/534.50
Comment 1 Anne 2011-08-01 09:40:07 UTC 
What exactly is the request here?
Comment 2 Michael[tm] Smith 2011-08-04 05:15:39 UTC 
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-16 01:30:25 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate? What problem is this going to solve?