@object-ui/fields 17.5.0 → 17.7.0

package/src/widgets/__tests__/FullscreenFieldEditor.i18n.test.tsx

@@ -1,248 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-
-/**
- * The REGISTERED path's fullscreen long-text dialog speaks the session locale —
- * objectui#3404.
- *
- * This is the second half of objectui#3272. That issue translated the built-in
- * branch (`FullscreenTextarea` in `components/src/renderers/form/form.tsx`,
- * pinned next door in `form-fullscreen-textarea-i18n.test.tsx`); the shared
- * `FullscreenFieldEditor` that `TextAreaField` and `RichTextField` render was
- * left with four English literals — the toggle's accessible name
- * (`Edit ${label} fullscreen`), the title fallback `Edit text`, `Cancel` and
- * `Done`.
- *
- * Nothing about the keys was missing: `form.fullscreen.*` and `common.cancel`
- * have shipped in all ten locale packs since #3272. This path simply never
- * consumed them, so the defect was visible INSIDE A SINGLE FORM: with
- * `ObjectFormSchema.mobile.fullscreenLongText` on, `ObjectForm` stamps
- * `mobile_fullscreen` onto every long-text field, and a zh session got
- * 「取消 / 完成」 from a built-in-rendered field and `Cancel / Done` from a
- * registered-widget one.
- *
- * ## What the cases assert, and why in this shape
- *
- * - **Both widgets.** `TextAreaField` (`field:textarea`) and `RichTextField`
- *   (`field:markdown` / `field:html`) are the two hosts, and the copy lives in
- *   the component they share. Covering one would leave a regression that broke
- *   only the other's props path (`label`, `testIdPrefix`) unreported.
- * - **`en` is a NO-OP pin, not a defect reproducer.** The four literals were
- *   byte-identical to the `en` pack, so the English cases below were green
- *   before this change too. They are here to prove the swap did not alter the
- *   English rendering — the direction that only a positive assertion can see.
- * - **Non-`en` positive AND English-literal negative, together.** A re-inlined
- *   literal rendered next to a translated sibling still satisfies a
- *   positive-only assertion. `ja` joins `zh` because the toggle's name is
- *   INTERPOLATED (`{{label}}` + a translated generic noun) and the two packs
- *   put the noun on opposite sides — a build that dropped the interpolation
- *   passes a zh-only check by luck.
- * - **Un-labelled fixtures for the generic copy.** `form.fullscreen.title` and
- *   `form.fullscreen.textFallback` are reachable only when the field has no
- *   `label` (a labelled field titles the dialog with its own label, in the
- *   author's language, on both paths). The labelled stack is pinned separately
- *   at the bottom, where what matters is that `{{label}}` is interpolated into
- *   translated surroundings rather than concatenated in English.
- */
-import { describe, it, expect, vi } from 'vitest';
-import { render, screen, fireEvent } from '@testing-library/react';
-import '@testing-library/jest-dom';
-import { I18nProvider } from '@object-ui/i18n';
-
-import { TextAreaField } from '../TextAreaField';
-import { RichTextField } from '../RichTextField';
-import type { FieldMetadata } from '@object-ui/types';
-
-/**
- * No `label` — the one authoring stack the generic copy is written for. The
- * flag is spelled `mobile_fullscreen`, the single carrier `ObjectForm`
- * produces (#3233/#3301).
- */
-const textareaField = (extra: Record<string, unknown> = {}) =>
-  ({ name: 'notes', type: 'textarea', mobile_fullscreen: true, ...extra }) as unknown as FieldMetadata;
-
-const markdownField = (extra: Record<string, unknown> = {}) =>
-  ({ name: 'notes', type: 'markdown', mobile_fullscreen: true, ...extra }) as unknown as FieldMetadata;
-
-function renderIn(language: string, element: React.ReactElement) {
-  return render(
-    <I18nProvider config={{ defaultLanguage: language, detectBrowserLanguage: false }}>
-      {element}
-    </I18nProvider>,
-  );
-}
-
-/** Open the dialog and hand back the trigger, so its name can be asserted too. */
-function openFullscreen(prefix: 'textarea' | 'richtext') {
-  const toggle = screen.getByTestId(`${prefix}-fullscreen-toggle`);
-  fireEvent.click(toggle);
-  return toggle;
-}
-
-describe('TextAreaField fullscreen dialog is translated (objectui#3404)', () => {
-  it('renders the English copy under an en provider', () => {
-    renderIn('en', <TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    const toggle = openFullscreen('textarea');
-
-    // Byte-identical to the literals this replaced, so `en` is a no-op change.
-    expect(toggle).toHaveAttribute('aria-label', 'Edit text fullscreen');
-    expect(screen.getByText('Edit text')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Cancel' })).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Done' })).toBeInTheDocument();
-  });
-
-  it('renders the whole dialog in Chinese under a zh provider', () => {
-    renderIn('zh', <TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    const toggle = openFullscreen('textarea');
-
-    expect(toggle).toHaveAttribute('aria-label', '全屏编辑文本');
-    expect(screen.getByText('编辑文本')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: '取消' })).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: '完成' })).toBeInTheDocument();
-
-    // The four literals, asserted absent. `Edit text` is matched loosely
-    // because it was BOTH the dialog title and part of the trigger's name.
-    expect(screen.queryByText(/edit text/i)).not.toBeInTheDocument();
-    expect(screen.queryByRole('button', { name: 'Cancel' })).not.toBeInTheDocument();
-    expect(screen.queryByRole('button', { name: 'Done' })).not.toBeInTheDocument();
-    expect(toggle.getAttribute('aria-label')).not.toMatch(/fullscreen/i);
-  });
-
-  it('renders the whole dialog in Japanese under a ja provider', () => {
-    renderIn('ja', <TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    const toggle = openFullscreen('textarea');
-
-    expect(toggle).toHaveAttribute('aria-label', 'テキストを全画面で編集');
-    expect(screen.getByText('テキストを編集')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'キャンセル' })).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: '完了' })).toBeInTheDocument();
-
-    expect(screen.queryByText(/edit text/i)).not.toBeInTheDocument();
-    expect(screen.queryByRole('button', { name: 'Done' })).not.toBeInTheDocument();
-  });
-});
-
-describe('RichTextField fullscreen dialog is translated (objectui#3404)', () => {
-  // The second host of the SAME component. The copy is shared, the props path
-  // into it (`label`, `testIdPrefix`) is not.
-  it('renders the English copy under an en provider', () => {
-    renderIn('en', <RichTextField value="# hello" onChange={vi.fn()} field={markdownField()} />);
-    const toggle = openFullscreen('richtext');
-
-    expect(toggle).toHaveAttribute('aria-label', 'Edit text fullscreen');
-    expect(screen.getByText('Edit text')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Cancel' })).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Done' })).toBeInTheDocument();
-  });
-
-  it('renders the whole dialog in Chinese under a zh provider', () => {
-    renderIn('zh', <RichTextField value="# hello" onChange={vi.fn()} field={markdownField()} />);
-    const toggle = openFullscreen('richtext');
-
-    expect(toggle).toHaveAttribute('aria-label', '全屏编辑文本');
-    expect(screen.getByText('编辑文本')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: '取消' })).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: '完成' })).toBeInTheDocument();
-
-    expect(screen.queryByText(/edit text/i)).not.toBeInTheDocument();
-    expect(screen.queryByRole('button', { name: 'Cancel' })).not.toBeInTheDocument();
-    expect(screen.queryByRole('button', { name: 'Done' })).not.toBeInTheDocument();
-    expect(toggle.getAttribute('aria-label')).not.toMatch(/fullscreen/i);
-  });
-});
-
-describe('fullscreen dialog copy — the field label is interpolated, not concatenated (objectui#3404)', () => {
-  it("titles the dialog with the author's label and interpolates it into the trigger name", () => {
-    // A labelled field keeps its own label as the title on both paths — what
-    // must be translated around it is the trigger's sentence. `Edit Notes
-    // fullscreen` was the literal; zh wraps the label instead of prefixing it.
-    renderIn(
-      'zh',
-      <TextAreaField value="hello" onChange={vi.fn()} field={textareaField({ label: 'Notes' })} />,
-    );
-    const toggle = openFullscreen('textarea');
-
-    expect(toggle).toHaveAttribute('aria-label', '全屏编辑Notes');
-    expect(screen.getByText('Notes')).toBeInTheDocument();
-    expect(toggle.getAttribute('aria-label')).not.toMatch(/^Edit /);
-  });
-
-  it('still commits the draft — translating the footer did not unwire it', () => {
-    // "Done" lost its literal child. This pins that the click handler still
-    // rides on the translated button and not on some node that merely used to
-    // carry the old text.
-    const onChange = vi.fn();
-    renderIn('zh', <TextAreaField value="hello" onChange={onChange} field={textareaField()} />);
-    openFullscreen('textarea');
-
-    fireEvent.change(screen.getByTestId('textarea-fullscreen-input'), {
-      target: { value: 'hello from fullscreen' },
-    });
-    fireEvent.click(screen.getByRole('button', { name: '完成' }));
-
-    expect(onChange).toHaveBeenCalledWith('hello from fullscreen');
-    expect(screen.queryByTestId('textarea-fullscreen-dialog')).not.toBeInTheDocument();
-  });
-
-  it('still discards the draft on the translated Cancel', () => {
-    const onChange = vi.fn();
-    renderIn('zh', <TextAreaField value="hello" onChange={onChange} field={textareaField()} />);
-    openFullscreen('textarea');
-
-    fireEvent.change(screen.getByTestId('textarea-fullscreen-input'), {
-      target: { value: 'discarded' },
-    });
-    fireEvent.click(screen.getByRole('button', { name: '取消' }));
-
-    expect(onChange).not.toHaveBeenCalled();
-    expect(screen.queryByTestId('textarea-fullscreen-dialog')).not.toBeInTheDocument();
-  });
-});
-
-describe('fullscreen dialog has an accessible description (objectui#3404)', () => {
-  /**
-   * The issue listed this as an unverified aside. What was measured: Radix
-   * only sets `aria-describedby` when a `Dialog.Description` is present
-   * (`descriptionPresent ? descriptionId : undefined`), so before this change
-   * the registered path's dialog had NO accessible description while the
-   * byte-identical built-in one did, and `form.fullscreen.description` was a
-   * key with no consumer on this path.
-   *
-   * Explicitly NOT justified by a console warning: `@radix-ui/react-dialog`
-   * 1.1.23 (the pinned version) contains no `console.*` call at all — the
-   * missing-Description warning older versions emitted is gone upstream, and
-   * no warning fired in the baseline run.
-   */
-  it('wires aria-describedby to the translated sr-only description', () => {
-    renderIn('zh', <TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    openFullscreen('textarea');
-
-    const dialog = screen.getByTestId('textarea-fullscreen-dialog');
-    const describedBy = dialog.getAttribute('aria-describedby');
-    expect(describedBy).toBeTruthy();
-
-    const description = document.getElementById(describedBy!);
-    expect(description).not.toBeNull();
-    expect(description).toHaveTextContent('编辑完整的文本内容，然后保存或取消更改。');
-  });
-
-  it('renders the English description under an en provider', () => {
-    renderIn('en', <TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    openFullscreen('textarea');
-
-    expect(
-      screen.getByText('Edit the full text value, then save or cancel your changes.'),
-    ).toBeInTheDocument();
-  });
-});
-
-// The provider-LESS leg lives in `FullscreenFieldEditor.no-provider.test.tsx`.
-// It cannot share this file: mounting `I18nProvider` installs its instance as
-// react-i18next's GLOBAL default, so after any case above there is no
-// "no provider" state left in this module graph to observe. See that file's
-// header — it was measured, not assumed.

package/src/widgets/__tests__/FullscreenFieldEditor.no-provider.test.tsx

@@ -1,116 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-
-/**
- * The shared fullscreen long-text dialog with NO `I18nProvider` mounted
- * (objectui#3404) — standalone/embedded hosts, and most of this package's own
- * bare-render tests.
- *
- * ## Why this leg decided the implementation
- *
- * Routing the copy through i18n must not turn it into raw keys where nothing
- * is configured. MEASURED on the pre-change tree with a probe rendering bare
- * `useObjectTranslation()` and no provider:
- *
- *     {"cancel":"common.cancel","done":"form.fullscreen.done",
- *      "title":"form.fullscreen.title","toggle":"form.fullscreen.toggle"}
- *
- * Raw keys on every one, and the `{{label}}` interpolation gone entirely —
- * strictly WORSE than the English literals being replaced. So
- * `FullscreenFieldEditor` consumes `useFieldTranslation()`
- * (`createSafeTranslation` + English defaults, the same shape the built-in
- * branch has used since objectui#3272) rather than the bare hook, and the
- * defaults are byte-identical to the old literals so this rendering is
- * unchanged.
- *
- * ## Why a separate FILE and not another `describe`
- *
- * Mounting `I18nProvider` calls `initReactI18next`, which installs that
- * instance as react-i18next's GLOBAL default. Once any sibling case has done
- * so there is no "no provider" state left in the module graph, and these
- * assertions would pass by reading that leaked instance instead of the
- * fallback — green for the wrong reason. That is not a hypothetical: these
- * cases were FIRST written inside `FullscreenFieldEditor.i18n.test.tsx`, and
- * the reverse check (swap `useFieldTranslation` back to bare
- * `useObjectTranslation`, expect red) left them GREEN there while it correctly
- * turned `RichTextField.mobileFullscreen.test.tsx` red. Split out, the same
- * swap turns them red — which is what makes them a pin.
- *
- * Same split, same reason as `TagsField.placeholder.no-provider.test.tsx` and
- * `OptionsEmptyState.no-provider.test.tsx`; vitest's per-file isolation is
- * what makes the observation honest.
- */
-import { describe, it, expect, vi } from 'vitest';
-import { render, screen, fireEvent } from '@testing-library/react';
-import '@testing-library/jest-dom';
-
-import { TextAreaField } from '../TextAreaField';
-import type { FieldMetadata } from '@object-ui/types';
-
-const textareaField = (extra: Record<string, unknown> = {}) =>
-  ({ name: 'notes', type: 'textarea', mobile_fullscreen: true, ...extra }) as unknown as FieldMetadata;
-
-function openFullscreen() {
-  const toggle = screen.getByTestId('textarea-fullscreen-toggle');
-  fireEvent.click(toggle);
-  return toggle;
-}
-
-describe('fullscreen dialog copy — English fallback survives with no i18n configured (objectui#3404)', () => {
-  it('renders the English defaults, not raw keys', () => {
-    render(<TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    const toggle = openFullscreen();
-
-    // Byte-identical to the literals this change replaced.
-    expect(toggle).toHaveAttribute('aria-label', 'Edit text fullscreen');
-    expect(screen.getByText('Edit text')).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Cancel' })).toBeInTheDocument();
-    expect(screen.getByRole('button', { name: 'Done' })).toBeInTheDocument();
-
-    // The measured failure mode, stated directly — a raw key reaching a user.
-    expect(document.body.textContent).not.toMatch(/form\.fullscreen\./);
-    expect(document.body.textContent).not.toMatch(/common\.cancel/);
-  });
-
-  it('still interpolates the field label into the trigger name', () => {
-    // `createSafeTranslation`'s fallback does its own `{{k}}` replacement.
-    // Bare `useObjectTranslation` returns `form.fullscreen.toggle` verbatim
-    // here, label dropped.
-    render(
-      <TextAreaField value="hello" onChange={vi.fn()} field={textareaField({ label: 'Notes' })} />,
-    );
-
-    expect(openFullscreen()).toHaveAttribute('aria-label', 'Edit Notes fullscreen');
-  });
-
-  it('the code-shipped defaults carry no CJK (Commandment #-1)', () => {
-    // With no provider mounted, whatever renders here came from CODE
-    // (FIELD_DEFAULTS). Escaped ranges on purpose: a literal CJK class would
-    // itself violate the commandment this asserts (same shape as
-    // `TagsField.placeholder.no-provider.test.tsx`).
-    render(<TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    openFullscreen();
-
-    expect(screen.getByTestId('textarea-fullscreen-dialog').textContent).not.toMatch(
-      /[\u3000-\u30ff\u4e00-\u9fff]/,
-    );
-  });
-
-  it('still gives the dialog an accessible description', () => {
-    render(<TextAreaField value="hello" onChange={vi.fn()} field={textareaField()} />);
-    openFullscreen();
-
-    const describedBy = screen
-      .getByTestId('textarea-fullscreen-dialog')
-      .getAttribute('aria-describedby');
-    expect(describedBy).toBeTruthy();
-    expect(document.getElementById(describedBy!)).toHaveTextContent(
-      'Edit the full text value, then save or cancel your changes.',
-    );
-  });
-});

package/src/widgets/__tests__/RichTextField.fullscreenDisabled.test.tsx

@@ -1,244 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-
-/**
- * A DISABLED `RichTextField` cannot be edited through its fullscreen dialog —
- * objectui#3402.
- *
- * The rich-text half of the same defect the sibling
- * `TextAreaField.fullscreenDisabled.test.tsx` pins, and it is a genuinely
- * separate code path rather than a copy of the assertions: this widget reaches
- * the affordance through `RichTextEditorSurface`'s `overlay` slot, and the
- * dialog renders the SAME surface again. `disabled` therefore has to be
- * resolved once and given to both renderings, exactly like `formatLabel` /
- * `hint` / `placeholder` already were — otherwise the two surfaces disagree
- * about whether the field is editable, which is the drift #3301 built the
- * shared surface to prevent.
- *
- * Measured on `origin/main` before the fix, by a dynamic probe (the issue
- * carried static evidence only):
- *
- *     PROBE richtext: inline disabled = true , toggle disabled = false
- *     PROBE richtext: dialog opened = true , dialog input disabled = false
- *     PROBE richtext: onChange calls = [["# EDITED WHILE DISABLED"]]
- *
- * `readonly` was never part of this: the widget early-returns a read-only
- * display before the affordance is computed. That path is untouched by the fix
- * and pinned below as a non-regression.
- */
-
-import { describe, it, expect, vi } from 'vitest';
-import { render, screen, fireEvent } from '@testing-library/react';
-import '@testing-library/jest-dom';
-
-import { RichTextField } from '../RichTextField';
-import type { FieldMetadata } from '@object-ui/types';
-
-const fieldMeta = (extra: Record<string, unknown> = {}) =>
-  ({
-    name: 'notes',
-    label: 'Notes',
-    type: 'markdown',
-    mobile_fullscreen: true,
-    ...extra,
-  }) as unknown as FieldMetadata;
-
-const toggle = () =>
-  screen.queryByTestId('richtext-fullscreen-toggle') as HTMLButtonElement | null;
-const dialogInput = () =>
-  screen.queryByTestId('richtext-fullscreen-input') as HTMLTextAreaElement | null;
-const saveButton = () =>
-  screen.queryByTestId('richtext-fullscreen-save') as HTMLButtonElement | null;
-
-describe('RichTextField fullscreen — disabled keeps the affordance but makes it inert (objectui#3402)', () => {
-  it('keeps the expand button and disables it', () => {
-    render(
-      <RichTextField value="# hello" onChange={() => {}} field={fieldMeta()} disabled />,
-    );
-
-    expect(toggle()).not.toBeNull();
-    expect(toggle()!.disabled).toBe(true);
-  });
-
-  it('does not open the dialog when that button is clicked anyway', () => {
-    render(
-      <RichTextField value="# hello" onChange={() => {}} field={fieldMeta()} disabled />,
-    );
-
-    fireEvent.click(toggle()!);
-
-    expect(screen.queryByTestId('richtext-fullscreen-dialog')).not.toBeInTheDocument();
-    expect(dialogInput()).toBeNull();
-  });
-
-  it('still disables the inline editing surface', () => {
-    render(
-      <RichTextField value="# hello" onChange={() => {}} field={fieldMeta()} disabled />,
-    );
-
-    const inline = screen.getAllByRole('textbox')[0] as HTMLTextAreaElement;
-    expect(inline.disabled).toBe(true);
-  });
-
-  it('never commits a value while disabled', () => {
-    const onChange = vi.fn();
-    render(
-      <RichTextField value="# hello" onChange={onChange} field={fieldMeta()} disabled />,
-    );
-
-    fireEvent.click(toggle()!);
-
-    expect(onChange).not.toHaveBeenCalled();
-  });
-});
-
-describe('RichTextField fullscreen — the dialog holds on its own when disabled arrives mid-edit (objectui#3402)', () => {
-  /**
-   * The `isSubmitting` shape at widget level: the form renderer has already
-   * OR-ed `isSubmitting` into the `disabled` this widget receives, so a submit
-   * starting under an open dialog looks exactly like this rerender.
-   */
-  function openThenDisable(onChange: () => void) {
-    const { rerender } = render(
-      <RichTextField value="# hello" onChange={onChange} field={fieldMeta()} />,
-    );
-    fireEvent.click(toggle()!);
-    expect(dialogInput()).not.toBeNull();
-
-    rerender(
-      <RichTextField value="# hello" onChange={onChange} field={fieldMeta()} disabled />,
-    );
-  }
-
-  it('locks the dialog controls', () => {
-    openThenDisable(vi.fn());
-
-    expect(dialogInput()).not.toBeNull();
-    expect(dialogInput()!.disabled).toBe(true);
-    expect(saveButton()!.disabled).toBe(true);
-  });
-
-  /** Split from the attribute assertions for the reason its textarea sibling
-   * spells out: as a tail on them it could only run when the native attribute
-   * was already doing the work. */
-  it('refuses the write-back even when "Done" is driven directly', () => {
-    const onChange = vi.fn();
-    openThenDisable(onChange);
-
-    fireEvent.change(dialogInput()!, { target: { value: '# EDITED WHILE SUBMITTING' } });
-    fireEvent.click(saveButton()!);
-
-    expect(onChange).not.toHaveBeenCalled();
-  });
-
-  it('still lets the user out of the dialog', () => {
-    const onChange = vi.fn();
-    const { rerender } = render(
-      <RichTextField value="# hello" onChange={onChange} field={fieldMeta()} />,
-    );
-
-    fireEvent.click(toggle()!);
-    rerender(
-      <RichTextField value="# hello" onChange={onChange} field={fieldMeta()} disabled />,
-    );
-
-    fireEvent.click(screen.getByRole('button', { name: /cancel/i }));
-
-    expect(screen.queryByTestId('richtext-fullscreen-dialog')).not.toBeInTheDocument();
-    expect(onChange).not.toHaveBeenCalled();
-  });
-});
-
-describe('RichTextField fullscreen — the states the fix must not have moved (objectui#3402)', () => {
-  it('still edits fullscreen and commits when the field is editable', () => {
-    const onChange = vi.fn();
-    render(<RichTextField value="# hello" onChange={onChange} field={fieldMeta()} />);
-
-    expect(toggle()!.disabled).toBe(false);
-    fireEvent.click(toggle()!);
-
-    const input = dialogInput()!;
-    expect(input.disabled).toBe(false);
-    expect(saveButton()!.disabled).toBe(false);
-
-    fireEvent.change(input, { target: { value: '# hello from fullscreen' } });
-    fireEvent.click(saveButton()!);
-
-    expect(onChange).toHaveBeenCalledWith('# hello from fullscreen');
-  });
-
-  it('keeps the dialog holding the REAL editor, disabled and not', () => {
-    // #3301's acceptance criterion, re-pinned under `disabled`: the dialog
-    // shows the same surface as the inline one (same format indicator), and now
-    // the same interactivity too — the very thing that had drifted.
-    const onChange = vi.fn();
-    const { rerender } = render(
-      <RichTextField
-        value=""
-        onChange={onChange}
-        field={fieldMeta({ format: 'html' })}
-      />,
-    );
-
-    fireEvent.click(toggle()!);
-    expect(screen.getAllByText('Format: html')).toHaveLength(2);
-
-    rerender(
-      <RichTextField
-        value=""
-        onChange={onChange}
-        field={fieldMeta({ format: 'html' })}
-        disabled
-      />,
-    );
-
-    // Both surfaces present, both inert.
-    expect(screen.getAllByText('Format: html')).toHaveLength(2);
-    // Queried off the document rather than by role: the dialog is modal, so
-    // Radix marks the background `aria-hidden` and a role query sees only the
-    // dialog's own control — which is precisely the textarea NOT at issue here.
-    // Both surfaces have to be disabled, so both are read directly.
-    const textareas = Array.from(
-      document.body.querySelectorAll('textarea'),
-    ) as HTMLTextAreaElement[];
-    expect(textareas).toHaveLength(2);
-    expect(textareas.every((el) => el.disabled)).toBe(true);
-  });
-
-  it('still renders no affordance at all in readonly mode', () => {
-    // The untouched early return — why readonly was never part of this defect.
-    render(
-      <RichTextField value="# hello" onChange={() => {}} readonly field={fieldMeta()} />,
-    );
-
-    expect(toggle()).toBeNull();
-    expect(screen.queryByRole('textbox')).not.toBeInTheDocument();
-    expect(screen.getByText('# hello')).toBeInTheDocument();
-  });
-
-  it('still renders no affordance when the metadata does not opt in, disabled or not', () => {
-    const { rerender } = render(
-      <RichTextField
-        value="# hello"
-        onChange={() => {}}
-        field={fieldMeta({ mobile_fullscreen: false })}
-      />,
-    );
-    expect(toggle()).toBeNull();
-
-    rerender(
-      <RichTextField
-        value="# hello"
-        onChange={() => {}}
-        field={fieldMeta({ mobile_fullscreen: false })}
-        disabled
-      />,
-    );
-    expect(toggle()).toBeNull();
-  });
-});