<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Confirm &lt;a download&gt; satisfies specification criteria"
   href="https://bugs.webkit.org/show_bug.cgi?id=156057">156057</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Confirm &lt;a download&gt; satisfies specification criteria
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>WebKit Nightly Build
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Major
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>WebKit Misc.
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>bfulgham&#64;webkit.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>We should be sure our implementation meets the functional and safety criteria defined in &lt;<a href="https://html.spec.whatwg.org/multipage/semantics.html#downloading-resources">https://html.spec.whatwg.org/multipage/semantics.html#downloading-resources</a>&gt;:

Specifically we want to ensure:

1. Can be used with blob: URLs and data: URLs
2. If the HTTP header Content-Disposition: is present and gives a different filename than this attribute, the HTTP header has priority over this attribute.
3. If this attribute is present and Content-Disposition: is set to inline, we should probably match Chrome and give priority to the download attribute.
4. We should only honor this attribute for links to resources with the same-origin.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>