@cahyo-dimas/freeday 1.54.0 → 2.0.0

package/dist/freeday-upload.js

@@ -1,13 +1,13 @@
-/* Freeday — file-upload enhancer (optional, zero-dependency).
+/* Freeday, file-upload enhancer (optional, zero-dependency).
  * A drop target that also opens the file dialog on click / Enter / Space, validates each file
  * (accept + max size), and renders a per-file row with explicit state. Actual upload is the
- * consumer's job — this is a controlled reference: wire the emitted event's row API to your
+ * consumer's job, this is a controlled reference: wire the emitted event's row API to your
  * upload call, or set data-fdy-upload-simulate for a demo progress animation.
  *
  * Markup contract:
  *  <div class="fdy-dropzone" data-fdy-dropzone role="button" tabindex="0"
  *       data-max-size="10485760" data-filelist="#dz-list" [data-fdy-upload-simulate]
- *       aria-label="Unggah berkas — seret ke sini atau tekan Enter">
+ *       aria-label="Unggah berkas, seret ke sini atau tekan Enter">
  *    <span class="fdy-dropzone__icon">…svg…</span>
  *    <span class="fdy-dropzone__title">…</span>
  *    <span class="fdy-dropzone__hint">…</span>
@@ -15,15 +15,15 @@
  *  </div>
  *  <div class="fdy-filelist" id="dz-list"></div>
  *
- * Emits bubbling CustomEvents — BOTH on the dropzone element, which is the one target a consumer
+ * Emits bubbling CustomEvents. BOTH on the dropzone element, which is the one target a consumer
  * needs to listen on:
  *   "fdy-upload-add"    {file, rejected, reason, row}
  *   "fdy-upload-remove" {file}
  * `row` is the state machine over the rendered .fdy-file:
- *   .ready() (rest — where a dropped file starts) / .uploading() / .setProgress(pct) /
+ *   .ready() (rest, where a dropped file starts) / .uploading() / .setProgress(pct) /
  *   .waiting(label) (sent, awaiting the server) / .done() / .fail(msg) / .el
  * Note the file list is a SIBLING of the dropzone above, so nothing dispatched on a row would ever
- * bubble through the zone — which is why removal fires on the zone and not on the row.
+ * bubble through the zone, which is why removal fires on the zone and not on the row.
  */
 (function () {
   'use strict';
@@ -51,21 +51,21 @@
   }
 
 
-  /* User-facing strings. Indonesian by default — documented and deliberate for the raw enhancer
-   * path — and every one overridable per element, so a host that speaks another language (the
+  /* User-facing strings. Indonesian by default, documented and deliberate for the raw enhancer
+   * path, and every one overridable per element, so a host that speaks another language (the
    * Blazor adapters, an English app on the raw path) supplies its own without forking this file.
    * Keeping them in ONE table is also what lets a guard prove none is hard-coded further down. */
   var TEXT = {
-    remove: 'Hapus {name}',
-    progress: 'Progres unggah {name}',
-    uploading: 'Mengunggah…',
-    waiting: 'Menunggu server…',
-    done: 'Terunggah',
-    badType: 'Tipe berkas tidak didukung.',
-    tooBig: 'Ukuran melebihi batas ({max}).'
+    remove: 'Remove {name}',
+    progress: 'Upload progress for {name}',
+    uploading: 'Uploading…',
+    waiting: 'Waiting for the server…',
+    done: 'Uploaded',
+    badType: 'Unsupported file type.',
+    tooBig: 'Over the {max} limit.'
   };
   /* HTML lowercases attribute names, so a camelCase key like `filterText` can only ever be written
-     as `data-fdy-text-filtertext` — while the kebab form anybody would reach for,
+     as `data-fdy-text-filtertext`, while the kebab form anybody would reach for,
      `data-fdy-text-filter-text`, becomes a DIFFERENT attribute the enhancer never reads, and the
      override fails silently. So the key is kebab-cased for the lookup; the run-together spelling
      still resolves, for markup written against 1.39.0. */
@@ -103,12 +103,12 @@
     remove.setAttribute('aria-label', textOf(zone, 'remove', { name: file.name }));
     remove.innerHTML = '&times;';
     remove.addEventListener('click', function () {
-      /* Dispatched on the ZONE, not on the row — the same target as fdy-upload-add, so one listener
+      /* Dispatched on the ZONE, not on the row, the same target as fdy-upload-add, so one listener
          on the dropzone gets both. The row lives in the file list, which the kit's own markup
          contract puts as a SIBLING of the dropzone, so a row event never bubbles through the zone:
          a consumer following the docs saw `add` arrive and `remove` never fire, with no error.
-         Firing on both would look safer, but it makes the pair asymmetric — one `add` and, for
-         anyone delegating on a common ancestor, two `remove`s — which is its own silent bug. It
+         Firing on both would look safer, but it makes the pair asymmetric, one `add` and, for
+         anyone delegating on a common ancestor, two `remove`s, which is its own silent bug. It
          also fixes the listless case: a row that was never attached bubbles to nothing at all. */
       zone.dispatchEvent(new CustomEvent('fdy-upload-remove', { bubbles: true, detail: { file: file } }));
       el.remove();
@@ -140,14 +140,14 @@
     }
     /* Back to a measured bar. While the indeterminate modifier is on it owns the bar's width, so an
        explicit one has to be restored when it comes off: .fdy-progress__bar is a plain block div, and
-       with no width at all it fills the track — a full bar, which is the opposite of what 0% means. */
+       with no width at all it fills the track, a full bar, which is the opposite of what 0% means. */
     function determinate() {
       progressEl.classList.remove('fdy-progress--indeterminate');
       if (!bar.style.width) bar.style.width = '0%';
     }
     return {
       el: el,
-      /* The state a row starts in: chosen, not yet sent. The size alone — it makes no claim about
+      /* The state a row starts in: chosen, not yet sent. The size alone, it makes no claim about
          a transfer, and no progress bar is shown, because nothing is in flight. Without this the
          state machine had no start state: done() claims success, fail() claims an error, and
          uploading() is a lie until the consumer actually sends the file. */
@@ -171,12 +171,12 @@
         bar.style.width = v + '%';
         progressEl.setAttribute('aria-valuenow', String(Math.round(v)));
       },
-      /* The bytes are gone and the server has not answered yet — extraction, scanning, transcoding.
+      /* The bytes are gone and the server has not answered yet, extraction, scanning, transcoding.
          "Mengunggah…" turns false the moment the last byte leaves, and a determinate bar parked at
          100% is the most convincing "hung" signal a UI can produce, so this state reports no
          percentage: the bar goes indeterminate and the label belongs to the consumer, because only
          they know what the server is doing ("Membaca PDF…", "Memindai…"). done()/fail()/ready() need
-         no counterpart here — they drop the progress element outright, modifier and all. */
+         no counterpart here, they drop the progress element outright, modifier and all. */
       waiting: function (label) {
         el.classList.remove('fdy-file--error', 'fdy-file--success');
         icon.innerHTML = FILE_ICON;
@@ -184,7 +184,7 @@
         ensureProgress();
         progressEl.classList.add('fdy-progress--indeterminate');
         /* The modifier styles .fdy-progress__bar, so it must sit on the CONTAINER, and the inline
-           width setProgress wrote has to go — an inline style beats any rule the modifier brings.
+           width setProgress wrote has to go, an inline style beats any rule the modifier brings.
            aria-valuenow goes with it: a progressbar with no value is precisely what ARIA calls
            indeterminate, which is the contract COMPONENTS.md already states for this component. */
         bar.style.width = '';
@@ -255,7 +255,7 @@
     if (input) input.addEventListener('change', function () { handleFiles(input.files); input.value = ''; });
 
     /* The list is optional: rendering a row and announcing the file are separate jobs. A consumer
-       that wants its own markup simply provides no list — it still gets `fdy-upload-add`, and
+       that wants its own markup simply provides no list, it still gets `fdy-upload-add`, and
        `detail.row` still works (its element is just never attached). Gating the EVENT on the list
        meant "bring your own row" silently cost you the notification that a file had arrived. */
     function handleFiles(fileList) {