[w3c/FileAPI] Editorial updates around encoding and MIME types (PR #223)

- "encodingName" was used as an argument, but this was confusing, because it was actually referring to an encoding's label (e.g. "utf8"), instead of its canonical name ("UTF-8").
- The mimeType argument was said to be optional, but all callers always passed it, so that was dead code.


<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/FileAPI/pull/223.html" title="Last updated on Aug 1, 2026, 6:50 AM UTC (0e80c93)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/FileAPI/223/cd1d1da...0e80c93.html" title="Last updated on Aug 1, 2026, 6:50 AM UTC (0e80c93)">Diff</a>
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/FileAPI/pull/223

-- Commit Summary --

  * Editorial: use encodingLabel for algorithm arguments
  * Editorial: require a MIME type when packaging data

-- File Changes --

    M index.bs (16)

-- Patch Links --

https://github.com/w3c/FileAPI/pull/223.patch
https://github.com/w3c/FileAPI/pull/223.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/pull/223
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/pull/223@github.com>