Perhaps to avoid the "legacy baggage" it could be a simple attribute
eg. <a href="blah" download> This would prevent duplicating 'type', and bringing in all the "knowledge" people seem to not have about how 'content-disposition' works in headers. or even an extension of target? eg. <a href="blah" target="_save"> Then it would be clear that it's only a hint, like the other target values. -- James (I accidentally sent this to the wrong address before sorry for the dupe) On 3 August 2010 03:37, Boris Zbarsky <[email protected]> wrote: > On 8/2/10 1:15 PM, Aryeh Gregor wrote: >> >> If you don't agree that this use-case is worth adding the feature for, >> do you think that: >> 3) Something else? > > For the use case your describe, it might just make more sense for browsers > to support Content-Disposition on data: URIs directly somehow... Maybe. > > -Boris >
