@cahyo-dimas/freeday 1.54.0 → 2.0.0

package/adapters/vue/components/FdyCfl.vue

@@ -9,7 +9,7 @@ import { computed, nextTick, onBeforeUnmount, ref, useId, type ComputedRef, type
 // that: a real `v-model:Row|null` over a native <dialog> whose rows come from an async
 // `fetchPage(query, page)`. It re-implements the enhancer's open/close + search + dense
 // sticky-header results + single-commit-on-click + keyboard, and adds the pieces a server
-// picker needs — loading/empty/error states, retry, pagination, an out-of-order guard, and
+// picker needs, loading/empty/error states, retry, pagination, an out-of-order guard, and
 // an optional in-memory cache. The enhancer is NOT mounted here (it would fight Vue's DOM).
 
 interface CflColumn {
@@ -23,7 +23,7 @@ interface CflPage {
 }
 
 const props = defineProps<{
-  /** Single: `Row | null`. With `multiple`, an array — `Row[] | null`, where null and [] both mean
+  /** Single: `Row | null`. With `multiple`, an array, `Row[] | null`, where null and [] both mean
    *  nothing picked. The enhancer has had `data-fdy-cfl-multiple` all along; this is the typed
    *  wrappers catching up (#019). */
   modelValue: Row | Row[] | null;
@@ -31,7 +31,7 @@ const props = defineProps<{
   columns: ReadonlyArray<CflColumn>;
   display: (row: Row) => string;
   rowKey: (row: Row) => string;
-  /** Advisory only — the caller's `fetchPage` owns paging; kept for API documentation. */
+  /** Advisory only, the caller's `fetchPage` owns paging; kept for API documentation. */
   pageSize?: number;
   /** The dialog's heading. Default 'Choose data', matching the Blazor adapter's `Title`. */
   title?: string;
@@ -108,7 +108,7 @@ const showClear: ComputedRef<boolean> = computed(
 );
 const clearLabelText: ComputedRef<string> = computed((): string => props.clearLabel ?? 'Clear selection');
 const isInvalid: ComputedRef<boolean> = computed((): boolean => props.invalid === true);
-/* `display()` takes one row, so in multi the field states HOW MANY — naming one of six would be a
+/* `display()` takes one row, so in multi the field states HOW MANY, naming one of six would be a
    lie, and naming all six does not fit a control that is 22rem wide. */
 const currentRows: ComputedRef<Row[]> = computed((): Row[] =>
   Array.isArray(props.modelValue) ? props.modelValue : props.modelValue !== null ? [props.modelValue as Row] : [],
@@ -119,7 +119,7 @@ const displayValue: ComputedRef<string> = computed((): string => {
   return props.modelValue !== null ? props.display(props.modelValue as Row) : '';
 });
 // The results <table> (owner of `resultsId`) only renders in the rows branch, so gate the
-// search input's aria refs on rows existing — otherwise they'd dangle during loading/empty/error.
+// search input's aria refs on rows existing, otherwise they'd dangle during loading/empty/error.
 const hasRows: ComputedRef<boolean> = computed((): boolean => rows.value.length > 0);
 const controlsId: ComputedRef<string | undefined> = computed((): string | undefined =>
   hasRows.value ? resultsId : undefined,
@@ -156,7 +156,7 @@ async function loadPage(targetPage: number, append: boolean): Promise<void> {
   try {
     const cached: CflPage | undefined = cache.get(key);
     const res: CflPage = cached ?? (await props.fetchPage(q, targetPage));
-    if (token !== reqToken) return; // stale — a newer request has started
+    if (token !== reqToken) return; // stale, a newer request has started
     if (cached === undefined) cache.set(key, res);
     const copy: Row[] = res.rows.slice(); // never mutate the caller's array
     rows.value = append ? rows.value.concat(copy) : copy;
@@ -220,7 +220,7 @@ function togglePick(row: Row): void {
   else picked.value = picked.value.filter((_: Row, i: number): boolean => i !== at);
 }
 
-/* A click means "tick this" in multi and "this is my answer" in single — the whole difference. */
+/* A click means "tick this" in multi and "this is my answer" in single, the whole difference. */
 function onRowClick(row: Row): void {
   if (props.multiple === true) togglePick(row);
   else commit(row);
@@ -238,7 +238,7 @@ function commit(row: Row | null): void {
   closeDialog();
 }
 
-/* Unsetting is not "picking nothing" — it must not open or close the dialog, and it must leave focus
+/* Unsetting is not "picking nothing", it must not open or close the dialog, and it must leave focus
    on a control that still exists, so focus returns to the trigger beside it. */
 function clearValue(): void {
   picked.value = [];

package/adapters/vue/components/FdyChart.vue

@@ -4,7 +4,7 @@ import { computed, onBeforeUnmount, onMounted, ref, watch, nextTick, type Comput
 // A Vue-native wrapper over freeday's zero-dependency chart renderer (freeday-chart.js).
 // Unlike the input components, charts are not form controls, so re-implementing them in Vue
 // would only duplicate the SVG maths. Instead this thin wrapper binds the renderer's data-*
-// API reactively and re-invokes window.FreedayChart.update() whenever the data changes — giving
+// API reactively and re-invokes window.FreedayChart.update() whenever the data changes, giving
 // reactive, typed charts (a drop-in replacement for hand-rolled Chart.js wrappers) with no
 // external dependency. Because the renderer paints with CSS var()/--chart-* tokens, charts also
 // recolour on data-theme change for free. Requires the freeday enhancers (dist/freeday.js) to be
@@ -16,7 +16,7 @@ interface FdyChartSeries {
   role?: string;
 }
 
-// Note: no `ariaLabel` prop — pass `aria-label` (and any other native attribute) directly; it
+// Note: no `ariaLabel` prop, pass `aria-label` (and any other native attribute) directly; it
 // falls through onto the root element. `role="img"` is set below. Give every chart an aria-label.
 const props = defineProps<{
   type: 'line' | 'area' | 'bar' | 'sparkline' | 'donut';

package/adapters/vue/components/FdyCombo.vue

@@ -220,7 +220,7 @@ onBeforeUnmount((): void => {
     <ul :id="listboxId" ref="listboxEl" class="fdy-combo__listbox" role="listbox" popover="manual" :hidden="!open">
       <!-- @mousedown.prevent keeps focus on the button: the option <li> isn't focusable, so a plain
            mousedown moves focus out of the combo, fires @focusout, and closes the list before the click
-           lands — mouse-select would silently do nothing. Same pattern as FdyDatepicker/FdyAutocomplete. -->
+           lands, mouse-select would silently do nothing. Same pattern as FdyDatepicker/FdyAutocomplete. -->
       <li
         v-for="(opt, i) in options"
         :id="optionId(i)"

package/adapters/vue/components/FdyDateRange.vue

@@ -13,7 +13,7 @@ import FdyDatepicker from './FdyDatepicker.vue';
 // two linked FdyDatepickers where the end can't precede the start (start.max = end, end.min =
 // start). A real `v-model:DateRangeValue` that composes the single-date picker rather than
 // re-implementing the calendar. The vanilla enhancer's cross-calendar `.in-range` day shading is
-// not reproduced (each picker is independent) — the min/max linkage is what keeps the range valid.
+// not reproduced (each picker is independent), the min/max linkage is what keeps the range valid.
 
 const props = defineProps<{
   modelValue: DateRangeValue;
@@ -21,7 +21,7 @@ const props = defineProps<{
   max?: string;
   locale?: string;
   disabled?: boolean;
-  /** Locked/view mode for both pickers — focusable, values shown, but can't be opened or changed. */
+  /** Locked/view mode for both pickers, focusable, values shown, but can't be opened or changed. */
   readonly?: boolean;
   invalid?: boolean;
   describedby?: string;

package/adapters/vue/components/FdyDatepicker.vue

@@ -39,7 +39,7 @@ const props = defineProps<{
   ariaLabelledby?: string;
   /** Show a clear (×) button in the trigger when a date is set, so an optional date can be unset. Emits `''` via update:modelValue + change. Off by default. */
   clearable?: boolean;
-  /** aria-label for the previous-month nav button. Default 'Previous month' — override for non-English UIs (month/weekday names already follow `locale`). */
+  /** aria-label for the previous-month nav button. Default 'Previous month', override for non-English UIs (month/weekday names already follow `locale`). */
   prevMonthLabel?: string;
   /** aria-label for the next-month nav button. Default 'Next month'. */
   nextMonthLabel?: string;
@@ -145,7 +145,7 @@ const effectiveFocusDate: ComputedRef<Date> = computed((): Date => {
   return new Date(view.value.getFullYear(), view.value.getMonth(), Math.min(f.getDate(), daysInMonth));
 });
 
-/* 'days' | 'months' — the calendar drills one level up instead of growing furniture beside the title.
+/* 'days' | 'months', the calendar drills one level up instead of growing furniture beside the title.
    Before this the only pointer route to another month was one click per month: August 2026 to March
    2022 is fifty-three of them, and the Shift+PageUp jump had no affordance at all. */
 const mode: Ref<'days' | 'months' | 'years'> = ref('days');
@@ -212,7 +212,7 @@ interface YearCell {
   focusable: boolean;
 }
 
-/** A year is unreachable only when EVERY month in it falls outside min/max — the same rule
+/** A year is unreachable only when EVERY month in it falls outside min/max, the same rule
  *  isMonthDisabled applies one level down, and for the same reason. */
 function isYearDisabled(year: number): boolean {
   if (minDate.value !== null && startOfDay(new Date(year, 11, 31)).getTime() < startOfDay(minDate.value).getTime()) return true;
@@ -411,7 +411,7 @@ function pick(d: Date): void {
   closePanel(true);
 }
 
-// Clear (reset to empty). Emits '' — parseISO('') is null, so the placeholder shows again.
+// Clear (reset to empty). Emits '', parseISO('') is null, so the placeholder shows again.
 function clearValue(): void {
   emit('update:modelValue', '');
   emit('change', '');
@@ -496,7 +496,7 @@ function onDocPointerDown(e: MouseEvent): void {
 }
 
 // Close when focus leaves the control entirely (e.g. Shift+Tab off the trigger).
-/* A null relatedTarget means focus fell to <body> — which is what happens when the element the
+/* A null relatedTarget means focus fell to <body>, which is what happens when the element the
  * user just pressed is REMOVED by the click it triggered (drilling into the month grid replaces
  * the grid, and with it the cell that had focus). That is not focus leaving the control, and
  * closing on it made the panel vanish mid-navigation. A pointer that really lands outside is

package/adapters/vue/components/FdyDrawer.vue

@@ -2,15 +2,15 @@
 import { computed, onMounted, useId, watch, type ComputedRef, type Ref, ref } from 'vue';
 
 // A controlled Vue wrapper over freeday's `.fdy-drawer` native <dialog> side panel
-// (src/components/drawer.css). Same controlled contract and glue as FdyModal — showModal()/close()
+// (src/components/drawer.css). Same controlled contract and glue as FdyModal, showModal()/close()
 // guarded, @cancel.prevent so Esc routes through app state, backdrop-click via `event.target ===
-// dialogEl` — applied to a drawer that anchors left (default) or right. Native <dialog> supplies the
+// dialogEl`, applied to a drawer that anchors left (default) or right. Native <dialog> supplies the
 // focus trap, focus restore, top-layer stacking and inert background; `dismissible` (default true)
 // gates Esc + backdrop dismissal.
 
 // dismissible MUST go through withDefaults: Vue's boolean-cast gives an omitted Boolean prop
 // `false`, not `undefined`, so a bare `props.dismissible !== false` would make an un-annotated
-// drawer non-dismissible (no Esc, no backdrop, no close button) — the opposite of the default.
+// drawer non-dismissible (no Esc, no backdrop, no close button), the opposite of the default.
 const props = withDefaults(defineProps<{
   open: boolean;
   title: string;

package/adapters/vue/components/FdyModal.vue

@@ -8,11 +8,11 @@ import { computed, onMounted, useId, watch, type ComputedRef, type Ref, ref } fr
 // (showModal() on an open dialog throws), @cancel.prevent so Esc routes through app state instead of
 // closing the DOM behind its back, and backdrop-click detection via `event.target === dialogEl`.
 // Native <dialog> already provides the focus trap, focus restore, top-layer stacking and inert
-// background — the wrapper only avoids breaking them. `dismissible` (default true) gates Esc + backdrop.
+// background, the wrapper only avoids breaking them. `dismissible` (default true) gates Esc + backdrop.
 
 // dismissible MUST go through withDefaults: Vue's boolean-cast gives an omitted Boolean prop
 // `false`, not `undefined`, so a bare `props.dismissible !== false` would make an un-annotated
-// modal non-dismissible (no Esc, no backdrop, no close button) — the opposite of the default.
+// modal non-dismissible (no Esc, no backdrop, no close button), the opposite of the default.
 const props = withDefaults(defineProps<{
   open: boolean;
   title: string;
@@ -46,7 +46,7 @@ onMounted((): void => sync(props.open));
 function onCancel(): void {
   if (dismissible.value) emit('close');
 }
-// The ::backdrop is not a separate element — a click whose target is the dialog box itself (not its
+// The ::backdrop is not a separate element, a click whose target is the dialog box itself (not its
 // content) is a backdrop click.
 function onClick(e: MouseEvent): void {
   if (dismissible.value && e.target === dialogEl.value) emit('close');

package/adapters/vue/components/FdyTable.vue

@@ -45,14 +45,14 @@ const props = withDefaults(defineProps<{
   /** Client-side page size when `page` is absent; 0/undefined = render all rows (no pager). */
   pageSize?: number;
   /**
-   * Controlled client-side page index (0-based). Provide it — with `pageSize`, without `page` — to
+   * Controlled client-side page index (0-based). Provide it, with `pageSize`, without `page`, to
    * own the page while the table keeps doing filter/sort/paginate. This is what lets an EXTERNAL
    * pager drive the table: a responsive screen that hides `.fdy-datatable` below `md` and renders a
    * card list from the `process` event can render one pager for both breakpoints and point it here.
    * Omit for the internal index (unchanged default).
    */
   /** Withhold the table's own footer (pager + range) so the screen can render one. Server mode had
-   *  no way to do this: the app owns the page there ANYWAY, and was still handed a second control —
+   *  no way to do this: the app owns the page there ANYWAY, and was still handed a second control,
    *  a responsive list that shows a table at one breakpoint and cards at another ended up with the
    *  kit's pager stacked under its own. Client mode's counterpart is `pageIndex`. Default true. */
   pager?: boolean;
@@ -61,7 +61,7 @@ const props = withDefaults(defineProps<{
    * (unchanged default). Every back office has one, and a table that renders two thirds of its own
    * footer forces the app to rebuild all three to add the last (#008).
    *
-   * Server mode reports the pick through `update:page` — same event as a page click, with a new
+   * Server mode reports the pick through `update:page`, same event as a page click, with a new
    * `size`. Client mode keeps it internally and also emits `update:pageSize`, so the control works
    * with nothing wired and can still be persisted.
    */
@@ -86,11 +86,11 @@ const emit = defineEmits<{
    *  a reset to 0 after sort/filter, or a clamp when filtering shrank the set). */
   'update:pageIndex': [index: number];
   /** Client mode with `pageSizes`: the reader picked a new rows-per-page. The table has already
-   *  applied it — this is for a caller that wants to persist the choice. */
+   *  applied it, this is for a caller that wants to persist the choice. */
   'update:pageSize': [size: number];
   /** A row was activated (click, or Enter/Space while the row itself is focused). */
   'row-activate': [row: Row];
-  /** The processed page of rows (after filter/sort/paginate) plus the total row count — fires in
+  /** The processed page of rows (after filter/sort/paginate) plus the total row count, fires in
    *  BOTH modes whenever they change. Lets a consumer render the SAME processed set elsewhere
    *  (a `< md` card list, a "selected" summary, export-to-CSV) without re-deriving the pipeline. */
   'process': [result: { rows: Row[]; total: number }];
@@ -100,7 +100,7 @@ const internalSort: Ref<FdySortState | null> = ref(null);
 const internalFilters: Ref<FdyFilterMap> = ref({});
 const internalPageIndex: Ref<number> = ref(0);
 /* Client-mode rows-per-page. `pageSize` is a plain prop with no event, so a footer control that only
- * emitted would do nothing in the app that wired nothing — the table applies the pick itself and
+ * emitted would do nothing in the app that wired nothing, the table applies the pick itself and
  * reports it. An explicit change to the prop wins back: the parent said something newer. */
 const internalPageSize: Ref<number | null> = ref(null);
 watch((): number | undefined => props.pageSize, (): void => { internalPageSize.value = null; });
@@ -250,7 +250,7 @@ function rowClasses(row: Row): Array<string | undefined> {
 function onRowClick(row: Row): void {
   if (props.rowActivatable === true) emit('row-activate', row);
 }
-// Enter/Space activate only when the row itself is focused — a control inside a cell keeps its own
+// Enter/Space activate only when the row itself is focused, a control inside a cell keeps its own
 // event (the `event.target !== event.currentTarget` guard). Click relies on inner controls calling
 // stopPropagation, matching the pattern consumers hand-roll today.
 function onRowKeydown(e: KeyboardEvent, row: Row): void {

package/adapters/vue/components/FdyTableFilter.vue

@@ -7,7 +7,7 @@ import type { FdyColumnFilter, FdyColumnFilterType } from '../../core/table-mode
 // Internal to FdyTable: one column's header funnel button + its type-aware filter popover
 // (text / enum / number / date) over freeday's `.fdy-table__filterbtn` + `.fdy-filter*` classes.
 // Reuses usePopover so the panel escapes the table's `overflow:hidden` via the top layer. Purely
-// controlled — it renders the current `filter` and emits the next one (or null to clear); the
+// controlled, it renders the current `filter` and emits the next one (or null to clear); the
 // parent owns where that goes (client state or an `update:filters` emit). Not exported.
 
 const props = defineProps<{

package/adapters/vue/components/FdyTableFooter.vue

@@ -8,19 +8,19 @@ import FdyCombo from './FdyCombo.vue';
  * The band under a table: what you are looking at, how much of it you see, where you are.
  *
  * `FdyTable` renders this itself, so most screens never import it. It is exported for the one shape
- * that cannot use the table's own — a RESPONSIVE list, where a `.fdy-datatable` at `lg` and a
+ * that cannot use the table's own, a RESPONSIVE list, where a `.fdy-datatable` at `lg` and a
  * `.fdy-list` below it are two renderings of ONE page of rows. A footer inside the table is inside
  * the half that is hidden on a phone, so those screens need to render it once, outside both
  * (improvement notes #005 and #008, from IDU_EMATE_APPL_WEB).
  *
- * It owns nothing. `page` in, `update:page` out — the same contract as the table's server mode, so a
+ * It owns nothing. `page` in, `update:page` out, the same contract as the table's server mode, so a
  * screen already wired for that switches by moving the prop.
  */
 const props = defineProps<{
   /** The page being shown. `size` drives the range AND the rows-per-page control's value. */
   page: FdyPageState;
   /**
-   * Offer a rows-per-page control. Omit for none — the footer is then range + pager, exactly as
+   * Offer a rows-per-page control. Omit for none; the footer is then range + pager, exactly as
    * before. Picking a size emits `update:page` carrying the new `size` and the index that still
    * holds the row you were looking at.
    */
@@ -29,7 +29,7 @@ const props = defineProps<{
 
 const emit = defineEmits<{ 'update:page': [page: FdyPageState] }>();
 
-/* The combo is labelled by the visible word beside it — a `<label for>` cannot reach inside a
+/* The combo is labelled by the visible word beside it, a `<label for>` cannot reach inside a
  * component, and an aria-label would leave that word unattached to anything. */
 const sizeLabelId: string = `fdy-rows-${useId()}`;
 
@@ -54,7 +54,7 @@ const sizes: ComputedRef<readonly number[]> = computed((): readonly number[] =>
 const sizeOptions: ComputedRef<Array<{ value: string; label: string }>> = computed(() =>
   sizes.value.map((size: number) => ({ value: String(size), label: String(size) })),
 );
-/* One page and no size control means there is nothing here to say — the table has always withheld
+/* One page and no size control means there is nothing here to say, the table has always withheld
  * the whole band in that case, and this is where that decision now lives. */
 const visible: ComputedRef<boolean> = computed((): boolean => hasPager.value || sizes.value.length > 0);
 

package/adapters/vue/index.d.ts

@@ -14,7 +14,7 @@ export declare function useFreeday(rootRef?: Ref<HTMLElement | null>): UseFreeda
 
 /**
  * Anchor a dropdown panel to its trigger in the top layer, so it escapes any ancestor overflow clip
- * — `.fdy-card` is `overflow:hidden`, so a panel positioned inside one is otherwise cut at the card's
+ *, `.fdy-card` is `overflow:hidden`, so a panel positioned inside one is otherwise cut at the card's
  * edge. The panel element must carry `popover="manual"`. This is the plumbing every kit dropdown
  * uses; it is exported so a control the kit does not ship can behave like one that it does, instead
  * of each app re-implementing it from the description.
@@ -35,7 +35,7 @@ export type { CascadeNode } from './components/FdyCascade.vue';
 export { default as FdyCfl } from './components/FdyCfl.vue';
 export { default as FdyChart } from './components/FdyChart.vue';
 export { default as FdyTable } from './components/FdyTable.vue';
-/** The table's own footer, standalone — for a responsive list whose table is hidden at some
+/** The table's own footer, standalone, for a responsive list whose table is hidden at some
  *  breakpoints and so cannot host it. */
 export { default as FdyTableFooter } from './components/FdyTableFooter.vue';
 export { default as FdyModal } from './components/FdyModal.vue';

package/adapters/vue/useFreeday.js

@@ -1,4 +1,4 @@
-/* Freeday — Vue 3 adapter (thin). The enhancers stay the source of truth; this
+/* Freeday. Vue 3 adapter (thin). The enhancers stay the source of truth; this
  * composable just re-runs every registered window.Freeday*.initAll() over a
  * subtree after Vue renders it, so [data-fdy-*] markup rendered by Vue gets
  * enhanced (and re-enhanced after updates). Enhancers are idempotent, so the
@@ -10,12 +10,12 @@
  *   useFreeday(root);            // scopes init to this component's subtree
  *   // <div ref="root"> ...[data-fdy-*] markup... </div>
  *
- * The ref may also sit ON the widget itself — <div ref="root" data-fdy-menu> — which is what you
+ * The ref may also sit ON the widget itself, <div ref="root" data-fdy-menu>, which is what you
  * write when the component's root element IS the widget. initAll() matches its own root as
  * well as descendants, so both shapes work. (Before 1.23.0 only the wrapping shape did, and
  * the other failed silently: querySelectorAll never matches its root.)
  *
- * Events come straight through as native bubbling CustomEvents — bind them with
+ * Events come straight through as native bubbling CustomEvents, bind them with
  * plain v-on (e.g. @fdy-cascade-change) and read event.detail. See index.d.ts
  * for the detail types.
  */

package/dist/asset.d.ts

@@ -1,6 +1,6 @@
-// Shared type stub for every export imported purely for its side effects — the CSS
+// Shared type stub for every export imported purely for its side effects: the CSS
 // bundles (`./css`, `./css/components`, `./tokens`) and the individual enhancer scripts
 // (`./enhancers/*`). TypeScript only needs the `types` condition to *resolve* the module;
-// there is no value surface to describe. (The root `.` import is different — it augments
-// window.Freeday — so it points at ./freeday.d.ts instead.)
+// there is no value surface to describe. (The root `.` import is different, since it augments
+// window.Freeday, so it points at ./freeday.d.ts instead.)
 export {};

package/dist/freeday-app-shell.js

@@ -1,23 +1,23 @@
-/* Freeday — app shell enhancer (optional, zero-dependency).
+/* Freeday, app shell enhancer (optional, zero-dependency).
  * Opt in with <div class="fdy-app" data-fdy-app>; the markup is otherwise unchanged.
  *
  * The shell has always shipped the state classes and no behaviour, which left every consumer to
- * assemble the toggle, Escape, focus trap, focus restore and `inert` themselves — and the two
+ * assemble the toggle, Escape, focus trap, focus restore and `inert` themselves, and the two
  * hand-rolled copies in this repo's own docs already disagreed about which of those exist. Below
  * 721px the sidebar is an OVERLAY (app-shell.css: position:fixed + translateX(-100%)), so it needs
  * the same treatment a modal drawer gets; at or above 721px it is a column that merely collapses.
  *
  * One rule covers both a hidden nav and a hidden page:
  *   - `__sidebar` is inert whenever the nav is NOT visible. Off-canvas and collapsed panels stay in
- *     the tab order otherwise — translateX(-100%) and width:0 hide a thing from the eye, not from
+ *     the tab order otherwise, translateX(-100%) and width:0 hide a thing from the eye, not from
  *     the keyboard, which is how a nav nobody can see still swallows Tab.
  *   - `__content` is inert only while the nav is an OPEN OVERLAY, so Tab cannot wander behind the
  *     backdrop.
  *
  * Emits a bubbling `fdy-app-nav` CustomEvent (detail {visible}) whenever the nav's visibility
  * changes, and takes `FreedayAppShell.setVisible(root, visible)` from outside. Those two exist for
- * the same reason the other enhancers have them: a host that keeps its own state — the Blazor
- * wrapper binding @bind-NavOpen, an app persisting the collapsed preference — has to be able to
+ * the same reason the other enhancers have them: a host that keeps its own state, the Blazor
+ * wrapper binding @bind-NavOpen, an app persisting the collapsed preference, has to be able to
  * hear the change and to drive it, without owning the behaviour twice.
  * FreedayAppShell.init(root) for late-mounted markup.
  */
@@ -31,7 +31,7 @@
     + ' textarea:not([disabled]), [tabindex]:not([tabindex="-1"])';
 
   /* getClientRects(), not offsetParent: an overlay sidebar is position:fixed, and a fixed element
-     reports no offsetParent at all — filtering on it would call every nav item invisible. */
+     reports no offsetParent at all, filtering on it would call every nav item invisible. */
   function focusables(root) {
     return Array.prototype.filter.call(root.querySelectorAll(FOCUSABLE), function (el) {
       return el.getClientRects().length > 0;
@@ -62,7 +62,7 @@
     function isCollapsed() { return app.classList.contains('fdy-app--nav-collapsed'); }
     function navVisible() { return mqWide.matches ? !isCollapsed() : isOverlayOpen(); }
 
-    /* aria-expanded answers "is the nav showing?" in BOTH modes — the two state classes are the
+    /* aria-expanded answers "is the nav showing?" in BOTH modes, the two state classes are the
        kit's business, not the reader's. */
     function sync() {
       var visible = navVisible();
@@ -91,7 +91,7 @@
       }
     }
 
-    /* restoreFocus is false when the viewport closed it rather than the user — a resize must not
+    /* restoreFocus is false when the viewport closed it rather than the user, a resize must not
        yank focus out from under whatever the reader was doing. */
     function close(restoreFocus) {
       if (!isOverlayOpen()) return;
@@ -118,7 +118,7 @@
 
     if (backdrop) backdrop.addEventListener('click', function () { close(); });
 
-    /* Following a link inside an overlay nav means "take me there" — leaving the panel open over
+    /* Following a link inside an overlay nav means "take me there", leaving the panel open over
        the page you just asked for is the one thing every hand-rolled copy in this repo disagreed on. */
     sidebar.addEventListener('click', function (e) {
       if (!isOverlayOpen()) return;

package/dist/freeday-autocomplete.js

@@ -1,7 +1,7 @@
-/* Freeday — autocomplete enhancer (optional, zero-dependency).
+/* Freeday, autocomplete enhancer (optional, zero-dependency).
  * Editable combobox (WAI-ARIA APG): a text input filters a role="listbox" of role="option"
  * items as you type; select fills the input. Auto-inits [data-fdy-autocomplete]. Options are
- * static markup filtered client-side — in an app, fetch/filter server-side and re-render options.
+ * static markup filtered client-side, in an app, fetch/filter server-side and re-render options.
  *
  * Markup: <div data-fdy-autocomplete class="fdy-autocomplete">
  *   <input class="fdy-input" role="combobox" aria-expanded="false" aria-autocomplete="list"

package/dist/freeday-breakpoint.js

@@ -1,4 +1,4 @@
-/* Freeday — breakpoint provider (optional, zero-dependency).
+/* Freeday, breakpoint provider (optional, zero-dependency).
  * The MudBreakpointProvider equivalent for JS consumers: stamps the current breakpoint on
  * <html data-breakpoint="xs|sm|md|lg|xl"> and emits a bubbling "fdy-breakpoint-change"
  * CustomEvent (detail {breakpoint}) whenever it changes. Also fills any element with

package/dist/freeday-carousel.js

@@ -1,4 +1,4 @@
-/* Freeday — carousel enhancer (optional, zero-dependency).
+/* Freeday, carousel enhancer (optional, zero-dependency).
  * Scroll-snap slider with prev/next arrows, generated dot indicators, keyboard (←/→),
  * and optional autoplay (data-fdy-autoplay="4000", pauses on hover/focus). Auto-inits
  * [data-fdy-carousel].
@@ -18,16 +18,16 @@
   'use strict';
 
 
-  /* 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 = {
-    position: '{n} dari {total}',
+    position: '{n} of {total}',
     slide: 'Slide {n}'
   };
   /* 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-cascade.js

@@ -1,4 +1,4 @@
-/* Freeday — cascade select enhancer (optional, zero-dependency).
+/* Freeday, cascade select enhancer (optional, zero-dependency).
  * Turns a [data-fdy-cascade] wrapper into a hierarchical drill-down picker. The
  * data model is a hidden nested <ul> inside the wrapper: a <li> with a child <ul>
  * is a branch (drills in), a <li> without is a leaf (selects). Each <li> carries
@@ -54,16 +54,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 = {
-    back: 'Kembali satu tingkat',
+    back: 'Back one level',
     submenu: '{label}, submenu'
   };
   /* 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. */
@@ -88,8 +88,8 @@
     var root = sourceUl ? parse(sourceUl) : [];
     if (sourceUl) sourceUl.remove();
 
-    var label = wrap.getAttribute('data-label') || 'Pilih';
-    var placeholder = wrap.getAttribute('data-placeholder') || 'Pilih…';
+    var label = wrap.getAttribute('data-label') || 'Select';
+    var placeholder = wrap.getAttribute('data-placeholder') || 'Select…';
     var sep = wrap.getAttribute('data-separator') || ' / ';
 
     var trigger = document.createElement('button');

package/dist/freeday-cfl.js

@@ -1,21 +1,21 @@
-/* Freeday — choose-from-list enhancer (optional, zero-dependency).
+/* Freeday, choose-from-list enhancer (optional, zero-dependency).
  * Wires a searchable master-data picker dialog to read-only fields.
  * Progressive enhancement over a native <dialog>; in a framework app, drive the
  * dialog as a controlled component (fetchPage callback + server cache), not a store.
  *
  * Markup contract (see docs):
- *  - Field group:  [data-fdy-cfl="<dialogId>"] — usually a `.fdy-input-group` holding a
+ *  - Field group:  [data-fdy-cfl="<dialogId>"], usually a `.fdy-input-group` holding a
  *      read-only `.fdy-input` and a trigger `<button class="fdy-input-group__btn">`.
  *      Optional `data-fdy-cfl-display="<key>"` picks which row dataset key fills the input
  *      (default "value"); optional `data-fdy-cfl-summary="{n} dipilih"` formats the multi label.
- *  - Standalone opener:  [data-fdy-cfl-open="<dialogId>"] — opens the dialog with no bound field.
+ *  - Standalone opener:  [data-fdy-cfl-open="<dialogId>"], opens the dialog with no bound field.
  *  - Dialog:  <dialog id="<dialogId>" class="fdy-modal fdy-modal--cfl"> containing
  *      a `[data-fdy-cfl-search]` input, `.fdy-cfl__row` <tr> rows carrying `data-*` fields,
  *      a `[data-fdy-cfl-empty]` element, and (multi only) `[data-fdy-cfl-multiple]` on the
  *      dialog plus `[data-fdy-cfl-count]` and `[data-fdy-cfl-confirm]` in the footer.
  *
  * Emits a bubbling "fdy-cfl-select" CustomEvent on the field group (or the dialog when
- * opened standalone): detail {row} for single-select, {rows} for multi-select — each a plain
+ * opened standalone): detail {row} for single-select, {rows} for multi-select, each a plain
  * object copy of the row's dataset. Consumers fill sibling fields (code → name) from it.
  */
 (function () {
@@ -34,15 +34,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 = {
-    selected: '{n} dipilih'
+    selected: '{n} selected'
   };
   /* 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,7 +103,7 @@
       var input = activeGroup.querySelector('.fdy-input');
       if (input) {
         if (detail.rows) {
-          var tpl = activeGroup.getAttribute('data-fdy-cfl-summary') || '{n} dipilih';
+          var tpl = activeGroup.getAttribute('data-fdy-cfl-summary') || '{n} selected';
           input.value = detail.rows.length ? tpl.replace('{n}', String(detail.rows.length)) : '';
         } else {
           var key = activeGroup.getAttribute('data-fdy-cfl-display') || 'value';