@cahyo-dimas/freeday 1.53.0 → 2.0.0

package/dist/freeday-mask.js

@@ -1,4 +1,4 @@
-/* Freeday — input mask + password reveal enhancer (optional, zero-dependency).
+/* Freeday, input mask + password reveal enhancer (optional, zero-dependency).
  *
  * [data-fdy-mask]="pattern" formats a text input as you type. Placeholders:
  *   #  a digit (0-9)      A  a letter (a-z/A-Z)      *  a letter or digit
@@ -51,16 +51,16 @@
   }
 
 
-  /* 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 = {
-    show: 'Tampilkan kata sandi',
-    hide: 'Sembunyikan kata sandi'
+    show: 'Show password',
+    hide: 'Hide password'
   };
   /* 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. */

package/dist/freeday-menu.js

@@ -1,4 +1,4 @@
-/* Freeday — menu enhancer (optional, zero-dependency).
+/* Freeday, menu enhancer (optional, zero-dependency).
  * Menu-button pattern (WAI-ARIA APG): a trigger with aria-haspopup="menu" toggles a
  * role="menu" popup of role="menuitem" buttons. Also powers the split button
  * (main action + attached caret toggle). Auto-inits [data-fdy-menu].

package/dist/freeday-number.js

@@ -1,7 +1,7 @@
-/* Freeday — number field enhancer (optional, zero-dependency).
+/* Freeday, number field enhancer (optional, zero-dependency).
  * Gives a native <input type="number"> its increment/decrement affordance back, on the kit's terms:
  * .fdy-input hides the user agent's own spin buttons (unthemeable OS widgets), so this puts two real
- * buttons in an .fdy-input-group instead. No new block — the group already owns the shared border,
+ * buttons in an .fdy-input-group instead. No new block, the group already owns the shared border,
  * :focus-within ring and error promotion.
  *
  * Markup contract:
@@ -67,7 +67,7 @@
         if (frozen()) return;
         if (Number(btn.getAttribute('data-fdy-number-step')) < 0) input.stepDown();
         else input.stepUp();
-        /* The value changed without the user typing, so say so the way the platform does — frameworks
+        /* The value changed without the user typing, so say so the way the platform does, frameworks
            listen to these, not to a kit-specific event. */
         input.dispatchEvent(new Event('input', { bubbles: true }));
         input.dispatchEvent(new Event('change', { bubbles: true }));

package/dist/freeday-popover.js

@@ -1,7 +1,7 @@
-/* Freeday — popover positioning helper (optional, zero-dependency).
+/* Freeday, popover positioning helper (optional, zero-dependency).
  * Lifts a dropdown panel into the top layer via the native Popover API so it escapes ANY
  * ancestor overflow clip (a .fdy-card with overflow:hidden, an app-shell main with
- * overflow:auto, …), then positions it `fixed` against its trigger — flipping above when
+ * overflow:auto, …), then positions it `fixed` against its trigger, flipping above when
  * there is no room below, and matching the trigger width. The panel stays a DOM child of its
  * component, so focus, outside-click (.closest), and ARIA relationships keep working unchanged.
  *
@@ -21,7 +21,7 @@
     && typeof HTMLElement.prototype.showPopover === 'function';
 
   // Position `panel` (already shown, so it has a measurable box) against `trigger`'s rect.
-  // matchWidth (default true) floors the panel to the trigger width — right for input-shaped
+  // matchWidth (default true) floors the panel to the trigger width, right for input-shaped
   // dropdowns (combo/cascade/date/time), skipped for menus that keep their own min-width.
   function place(panel, trigger, matchWidth) {
     var r = trigger.getBoundingClientRect();

package/dist/freeday-rating.js

@@ -1,7 +1,7 @@
-/* Freeday — rating enhancer (optional, zero-dependency).
+/* Freeday, rating enhancer (optional, zero-dependency).
  * Fills stars up to the checked radio (and previews on hover) for an interactive
  * [data-fdy-rating] radio group; for [data-fdy-readonly] it fills from data-value.
- * The radios are native — arrow-key selection and form association come for free.
+ * The radios are native, arrow-key selection and form association come for free.
  */
 (function () {
   'use strict';

package/dist/freeday-select.js

@@ -1,8 +1,8 @@
-/* Freeday — combobox enhancer (optional, zero-dependency).
+/* Freeday, combobox enhancer (optional, zero-dependency).
  * Implements the WAI-ARIA APG "select-only combobox" pattern for every
  * [data-fdy-combo] on the page. Progressive enhancement: the markup is the
  * component, this script wires behavior. In a Vue/React/Blazor app you would
- * bind your own state instead — this is the framework-agnostic reference.
+ * bind your own state instead, this is the framework-agnostic reference.
  *
  * Expected markup:
  *   <div class="fdy-combo" data-fdy-combo data-value="x">
@@ -25,7 +25,7 @@
   var seq = 0;
   var openClose = null; // close() of the currently-open combo, or null
 
-  /* The tick lives in CSS now, so the option's text IS its label — no sibling walk to skip a glyph. */
+  /* The tick lives in CSS now, so the option's text IS its label, no sibling walk to skip a glyph. */
   function optionLabel(opt) {
     return (opt.textContent || '').trim();
   }
@@ -91,7 +91,7 @@
       if (openClose === close) openClose = null;
     }
     // Mark an option selected + reflect it in the button. `silent` skips the change
-    // event, close, and focus — used by the programmatic setValue() below so a host
+    // event, close, and focus, used by the programmatic setValue() below so a host
     // (e.g. a Blazor/framework wrapper) can push a value in without echoing an event
     // back to itself or stealing focus. User-driven picks go through choose() (loud).
     function select(opt, silent) {
@@ -126,7 +126,7 @@
       isOpen() ? close() : open();
     });
     // Pressing an option must not blur the button: a blur fires the focusout
-    // handler below, which closes the listbox before the option's click lands —
+    // handler below, which closes the listbox before the option's click lands,
     // so the pick is lost (real mouse only; synthetic .click() never blurs).
     // preventDefault on mousedown keeps focus on the button without blocking click.
     listbox.addEventListener('mousedown', function (e) { e.preventDefault(); });

package/dist/freeday-slider.js

@@ -1,7 +1,7 @@
-/* Freeday — slider value binding (optional, zero-dependency).
+/* Freeday, slider value binding (optional, zero-dependency).
  * Mirrors a [data-fdy-slider] range input's value into <output for="inputId">, with an
  * optional prefix/suffix on the output (data-fdy-prefix / data-fdy-suffix). The range itself
- * is a native input — keyboard and ARIA are built in; this only updates the visible readout.
+ * is a native input, keyboard and ARIA are built in; this only updates the visible readout.
  */
 (function () {
   'use strict';

package/dist/freeday-stepper.js

@@ -1,6 +1,6 @@
-/* Freeday — stepper/wizard enhancer (optional, zero-dependency).
+/* Freeday, stepper/wizard enhancer (optional, zero-dependency).
  * Drives a step header + panels: prev/next navigation, completed/active state, and
- * clicking a reached step to revisit it (linear — can't skip ahead). Auto-inits
+ * clicking a reached step to revisit it (linear, can't skip ahead). Auto-inits
  * [data-fdy-stepper].
  *
  * Markup: <div data-fdy-stepper>
@@ -19,16 +19,16 @@
   var CHECK = '<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="3" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M20 6 9 17l-5-5"></path></svg>';
 
 
-  /* 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 = {
-    done: 'Selesai',
-    next: 'Lanjut'
+    done: 'Done',
+    next: 'Next'
   };
   /* 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. */

package/dist/freeday-table.js

@@ -1,4 +1,4 @@
-/* Freeday — data-table enhancer (optional, zero-dependency).
+/* Freeday, data-table enhancer (optional, zero-dependency).
  * Adds client-side search, column sort, pagination and row selection to any
  * [data-fdy-table]. Progressive enhancement over a plain semantic <table>;
  * in a framework app, do this server- or store-side instead.
@@ -34,26 +34,26 @@
   }
 
 
-  /* 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 = {
-    prev: 'Sebelumnya',
-    next: 'Berikutnya',
-    selected: '{n} dipilih',
-    filter: 'Filter kolom',
-    filterText: 'Berisi teks',
-    filterTextPlaceholder: 'Berisi…',
-    filterEnum: 'Tampilkan nilai',
-    filterRange: 'Rentang nilai',
+    prev: 'Previous',
+    next: 'Next',
+    selected: '{n} selected',
+    filter: 'Filter column',
+    filterText: 'Contains text',
+    filterTextPlaceholder: 'Contains…',
+    filterEnum: 'Show values',
+    filterRange: 'Value range',
     reset: 'Reset',
-    close: 'Tutup',
-    rows: '{n} baris',
-    info: 'Menampilkan {from}–{to} dari {total}'
+    close: 'Close',
+    rows: '{n} rows',
+    info: 'Showing {from}–{to} of {total}'
   };
   /* 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. */

package/dist/freeday-tabs.js

@@ -1,4 +1,4 @@
-/* Freeday — tabs enhancer (optional, zero-dependency, WAI-ARIA APG tabs).
+/* Freeday, tabs enhancer (optional, zero-dependency, WAI-ARIA APG tabs).
  * Auto-inits every [data-fdy-tabs]. Roving tabindex + arrow/Home/End nav.
  *
  * Markup: a [data-fdy-tabs] with a [role="tablist"] of

package/dist/freeday-timepicker.js

@@ -1,4 +1,4 @@
-/* Freeday — time picker enhancer (optional, zero-dependency).
+/* Freeday, time picker enhancer (optional, zero-dependency).
  * Builds an input-styled trigger + scrollable time-list popover (WAI-ARIA listbox)
  * from an empty [data-fdy-timepicker] wrapper. 24h HH:MM. Options run from
  * data-min (default 00:00) to data-max (default 23:59) every data-step minutes
@@ -28,7 +28,7 @@
     wrap.dataset.fdyTpReady = '1';
     wrap.classList.add('fdy-timepicker');
 
-    var label = wrap.getAttribute('data-label') || 'Pilih waktu';
+    var label = wrap.getAttribute('data-label') || 'Choose a time';
     var placeholder = wrap.getAttribute('data-placeholder') || '--:--';
     var step = Math.max(1, parseInt(wrap.getAttribute('data-step') || '30', 10));
     var minM = valid(wrap.getAttribute('data-min')) ? toMin(wrap.getAttribute('data-min')) : 0;

package/dist/freeday-toast.js

@@ -1,9 +1,9 @@
-/* Freeday — toast API (optional, zero-dependency).
+/* Freeday, toast API (optional, zero-dependency).
  * Freeday.toast({ variant, title, message, timeout, key }) shows a transient
  * notification in a live region (created on first use). Returns the element.
  *   variant: 'success' | 'warning' | 'danger' | 'info' (default: neutral)
  *   timeout: ms before auto-dismiss (default 4000; 0 = sticky)
- *   key:     optional stable id — a new toast with the same key REPLACES the
+ *   key:     optional stable id, a new toast with the same key REPLACES the
  *            existing one in place instead of stacking a duplicate (e.g. a burst
  *            of identical failures shows one toast, refreshed).
  * Freeday.dismiss(nodeOrKey) closes a toast early (pass the returned element or its key).
@@ -39,14 +39,14 @@
 
   /* Put the region in the TOP LAYER, above any open <dialog>.
    *
-   * A modal dialog lives in the top layer, where z-index does not reach — so a toast raised by an
+   * A modal dialog lives in the top layer, where z-index does not reach, so a toast raised by an
    * action taken inside a modal was painted behind that modal's backdrop, which is where an error
    * message is least useful. showPopover() joins the same layer, and membership there is ordered by
    * when you joined: hide-then-show re-joins at the top, so a toast shown while a dialog is open
    * lands above it rather than under the dialog that was opened after the last toast.
    *
    * Guarded twice on purpose. `showPopover` is absent before Chrome 114 / Safari 17 / Firefox 125,
-   * and the call throws if the element is disconnected or already open — in every one of those
+   * and the call throws if the element is disconnected or already open, in every one of those
    * cases the region stays an ordinary fixed block at z-index 200, which is what it has always
    * been. A notification must never be the thing that throws.
    */
@@ -77,15 +77,15 @@
   }
 
 
-  /* 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 = {
-    close: 'Tutup'
+    close: 'Close'
   };
   /* 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. */

package/dist/freeday-tree.js

@@ -1,7 +1,7 @@
-/* Freeday — tree checkbox cascade (optional, zero-dependency).
+/* Freeday, tree checkbox cascade (optional, zero-dependency).
  * Turns a [data-fdy-tree] checkbox tree into a selectable one: checking a branch checks
  * every descendant; a partially-selected branch shows the native :indeterminate state.
- * Rows are native <input class="fdy-checkbox">, labelled via aria-label — Space toggles.
+ * Rows are native <input class="fdy-checkbox">, labelled via aria-label. Space toggles.
  * Selection never toggles the <details> (the checkbox stops click propagation).
  *
  * Markup contract:
@@ -25,7 +25,7 @@
     return Array.prototype.filter.call(ul.children, function (n) { return n.tagName === 'LI'; });
   }
 
-  // The checkbox belonging to a row's own <li> — branch summary or leaf, never a child's.
+  // The checkbox belonging to a row's own <li>, branch summary or leaf, never a child's.
   function ownBox(li) {
     return li.querySelector(':scope > details > summary input[type="checkbox"]')
       || li.querySelector(':scope > input[type="checkbox"]');

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) {