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 9977 - It shall be valuable if you add a "forcedownload" link type which forces the client to download the target document in the download window rather than opening the document in the same window of the browser as what is hapening right now
Summary: It shall be valuable if you add a "forcedownload" link type which forces the...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (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: 2010-06-22 08:49 UTC by contributor
Modified: 2010-10-04 14:32 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-06-22 08:49:45 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#linkTypes

Comment:
It shall be valuable if you add a "forcedownload" link type which  forces the
client to download the target document in the download window rather than
opening the document in the same window of the browser as what is hapening
right now

Posted from: 213.130.124.66
Comment 1 Ian 'Hixie' Hickson 2010-08-28 00:08:50 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: Rejected
Change Description: no spec change
Rationale: The first step is to register the keyword in the link registry and get browsers to implement it. Once we have a proven feature, then it's time to standardise.