{"version":"2.1.229","anchor":"artifact-guidance-is-clearer-about-file-downloads","canonical_anchor":"artifact-guidance-is-clearer-about-file-downloads","heading":"Artifact guidance is clearer about file downloads","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-guidance-is-clearer-about-file-downloads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact guidance is clearer about file downloads\n\nArtifact guidance now says static pages can't hand you a file to save.\n\n**What**\n\nThe wording for what an artifact can and cannot do now lists handing the viewer a file to save among the things static HTML cannot provide, and the error you get when publishing an unservable supporting file explains what supporting files are for.\n\n**Details**\n\n- The rejection now spells out that neither a served file nor a `data:`\/`blob:` link gives the viewer a file, because downloads started by the page are blocked.\n- Applies to the runtime-capability description and the prototype\/template guidance.\n\n**Evidence**\n\n`Supporting files are assets the page itself loads`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}