@astryxdesign/core 0.4.3 → 0.4.4-canary.0f4d45f

package/src/theme/expandColorScale.test.ts

@@ -192,6 +192,144 @@ describe('expandColorScale — neutral-only themes (#2279)', () => {
   });
 });
 
+describe('expandColorScale — tuple accent (#2279)', () => {
+  const LIGHT_SEED = '#B7410E';
+  const DARK_SEED = '#48CAE4';
+
+  it('accepts a [light, dark] tuple and generates the accent tokens', () => {
+    const tokens = expandColorScale({accent: [LIGHT_SEED, DARK_SEED]});
+    for (const key of ACCENT_TOKENS) {
+      expect(tokens).toHaveProperty(key);
+    }
+    expect(tokens['--color-accent']).toMatch(/^light-dark\(#/);
+    expect(tokens['--color-on-accent']).toMatch(/^light-dark\(#/);
+  });
+
+  it('a same-halves tuple matches the single-string expansion, token for token', () => {
+    // Pins the string path as the tuple fast path: introducing tuples must
+    // not re-color any existing single-accent theme.
+    const fromString = expandColorScale({accent: LIGHT_SEED});
+    const fromTuple = expandColorScale({accent: [LIGHT_SEED, LIGHT_SEED]});
+    expect(fromTuple).toEqual(fromString);
+  });
+
+  it('derives the light palette from the light seed and the dark palette from the dark seed', () => {
+    // Every generated light-dark() pair takes its light half from the light
+    // seed's palettes and its dark half from the dark seed's, so resolving
+    // each mode must agree with the matching single-accent expansion.
+    const tuple = defineTheme({
+      name: 'tuple',
+      color: {accent: [LIGHT_SEED, DARK_SEED]},
+    });
+    const fromLight = defineTheme({name: 'light', color: {accent: LIGHT_SEED}});
+    const fromDark = defineTheme({name: 'dark', color: {accent: DARK_SEED}});
+
+    const generatedKeys = Object.keys(
+      expandColorScale({accent: [LIGHT_SEED, DARK_SEED]}),
+    );
+    const tupleLight = resolveThemeTokens(tuple, {mode: 'light'});
+    const refLight = resolveThemeTokens(fromLight, {mode: 'light'});
+    const tupleDark = resolveThemeTokens(tuple, {mode: 'dark'});
+    const refDark = resolveThemeTokens(fromDark, {mode: 'dark'});
+    for (const key of generatedKeys) {
+      expect(tupleLight[key], `${key} (light)`).toBe(refLight[key]);
+      expect(tupleDark[key], `${key} (dark)`).toBe(refDark[key]);
+    }
+  });
+
+  it('differing seeds produce a dark half the light seed would not', () => {
+    // Regression guard: the dark half must not silently reuse the light seed.
+    const tuple = defineTheme({
+      name: 'tuple-differs',
+      color: {accent: [LIGHT_SEED, DARK_SEED]},
+    });
+    const single = defineTheme({
+      name: 'single',
+      color: {accent: LIGHT_SEED},
+    });
+    expect(
+      resolveThemeTokens(tuple, {mode: 'dark'})['--color-accent'],
+    ).not.toBe(resolveThemeTokens(single, {mode: 'dark'})['--color-accent']);
+  });
+
+  it('keeps the derived accent tokens as references with a tuple accent', () => {
+    const tokens = expandColorScale({accent: [LIGHT_SEED, DARK_SEED]});
+    expect(tokens['--color-text-accent']).toBe('var(--color-accent)');
+    expect(tokens['--color-icon-accent']).toBe('var(--color-accent)');
+    expect(tokens['--color-accent-muted']).toContain('var(--color-accent)');
+  });
+
+  it('honours neutralStyle with a tuple accent', () => {
+    const warm = expandColorScale({
+      accent: [LIGHT_SEED, DARK_SEED],
+      neutralStyle: 'warm',
+    });
+    const cool = expandColorScale({
+      accent: [LIGHT_SEED, DARK_SEED],
+      neutralStyle: 'cool',
+    });
+    expect(warm['--color-neutral']).not.toBe(cool['--color-neutral']);
+  });
+});
+
+describe('accent precedence — color config vs tokens overrides (#2279)', () => {
+  const CONFIG_ACCENT: [string, string] = ['#B7410E', '#48CAE4'];
+  const TOKEN_ACCENT: [string, string] = ['#AA0000', '#FF5555'];
+
+  it('tokens["--color-accent"] wins over the color-generated accent', () => {
+    const theme = defineTheme({
+      name: 'precedence-base',
+      color: {accent: CONFIG_ACCENT},
+      tokens: {'--color-accent': TOKEN_ACCENT},
+    });
+    expect(theme.tokens['--color-accent']).toBe(
+      `light-dark(${TOKEN_ACCENT[0]}, ${TOKEN_ACCENT[1]})`,
+    );
+  });
+
+  it('reference tokens follow the tokens override at runtime', () => {
+    const theme = defineTheme({
+      name: 'precedence-refs',
+      color: {accent: CONFIG_ACCENT},
+      tokens: {'--color-accent': TOKEN_ACCENT},
+    });
+    const light = resolveThemeTokens(theme, {mode: 'light'});
+    expect(light['--color-text-accent']).toBe(TOKEN_ACCENT[0]);
+    expect(light['--color-icon-accent']).toBe(TOKEN_ACCENT[0]);
+    const dark = resolveThemeTokens(theme, {mode: 'dark'});
+    expect(dark['--color-text-accent']).toBe(TOKEN_ACCENT[1]);
+  });
+
+  it('baked --color-on-accent stays derived from the color.accent seed', () => {
+    // Documented divergence: a tokens override of --color-accent does not
+    // re-derive --color-on-accent, which is a baked contrast computation
+    // against the color.accent seed. Consumers who override the accent via
+    // tokens must override --color-on-accent too (or pass the tuple through
+    // color.accent so the whole palette re-derives).
+    const overridden = defineTheme({
+      name: 'precedence-on-accent',
+      color: {accent: CONFIG_ACCENT},
+      tokens: {'--color-accent': TOKEN_ACCENT},
+    });
+    const generated = defineTheme({
+      name: 'generated-on-accent',
+      color: {accent: CONFIG_ACCENT},
+    });
+    expect(overridden.tokens['--color-on-accent']).toBe(
+      generated.tokens['--color-on-accent'],
+    );
+  });
+
+  it('an explicit --color-on-accent token wins over the generated one', () => {
+    const theme = defineTheme({
+      name: 'precedence-on-accent-explicit',
+      color: {accent: CONFIG_ACCENT},
+      tokens: {'--color-on-accent': '#FFFFFF'},
+    });
+    expect(theme.tokens['--color-on-accent']).toBe('#FFFFFF');
+  });
+});
+
 describe('expandColorScale + defineTheme integration', () => {
   it('explicit token overrides win over generated values', () => {
     const theme = defineTheme({

package/src/theme/expandColorScale.ts

@@ -6,8 +6,8 @@
  * @output Token overrides for derivable color tokens
  * @position Theme utility; consumed by defineTheme.ts
  *
- * Generates color token overrides from a single accent color using the
- * HCT perceptual color model. Only produces tokens that meaningfully
+ * Generates color token overrides from an accent seed using the HCT
+ * perceptual color model. Only produces tokens that meaningfully
  * derive from the accent — status colors, categorical hues, and fixed
  * tokens (on-dark/on-light) fall through to colorDefaults.
  *
@@ -15,11 +15,19 @@
  * ramp (seeded from the default accent's hue) while the accent tokens
  * themselves fall through to colorDefaults, same as the tokens above.
  *
+ * `accent` also accepts a `[light, dark]` tuple (matching `TokenValue` in
+ * defineTheme). A tuple seeds each color scheme from its own half: the
+ * light side of every generated `light-dark()` pair derives from the light
+ * accent's palettes, the dark side from the dark accent's. A plain string
+ * seeds both sides identically, token for token the same output as before
+ * tuples existed.
+ *
  * WCAG contrast guarantees (asserted in expandColorScale.test.ts):
  * - Text tones are guaranteed >= 4.5:1 against their surfaces by tone
  *   spacing alone — HCT tone is CIE L*, which fixes relative luminance
  *   regardless of hue/chroma, so the fixed tone assignments hold for any
- *   accent/neutralStyle (WCAG 1.4.3).
+ *   accent/neutralStyle (WCAG 1.4.3), and each half of a tuple pairs with
+ *   surfaces derived from that same seed.
  * - --color-border-emphasized (form-control boundaries) is tone-bumped
  *   until it reaches >= 3:1 against the generated surface (WCAG 1.4.11).
  * - --color-border, --color-skeleton, and --color-track are intentionally
@@ -46,6 +54,9 @@ import {hexToHct, hctToHex, tonalPalette, hexWithAlpha} from './hct';
  * // Minimal — just a seed color
  * { accent: '#0064E0' }
  *
+ * // Per-scheme seeds: light palettes from '#0064E0', dark from '#48CAE4'
+ * { accent: ['#0064E0', '#48CAE4'] }
+ *
  * // With customization
  * { accent: '#B7410E', neutralStyle: 'warm', contrast: 'high' }
  *
@@ -55,14 +66,18 @@ import {hexToHct, hctToHex, tonalPalette, hexWithAlpha} from './hct';
  */
 export interface ColorScaleConfig {
   /**
-   * Seed accent color as hex (#RRGGBB). Everything derives from this.
+   * Seed accent color. Everything derives from this.
+   *
+   * Either a single hex (#RRGGBB) used for both color schemes, or a
+   * `[light, dark]` hex tuple: the light scheme's palettes derive from
+   * the light seed and the dark scheme's palettes from the dark seed.
    *
    * Optional. When omitted, the neutral palettes are seeded from the
    * default accent's hue and the accent tokens (--color-accent,
    * --color-accent-muted, --color-on-accent) are not generated — they
    * fall through to colorDefaults.
    */
-  accent?: string;
+  accent?: string | [light: string, dark: string];
 
   /**
    * Neutral tone warmth. Controls how much of the seed's hue bleeds
@@ -159,6 +174,11 @@ export function ensureContrastTone(
  * --color-on-dark/on-light) are NOT generated — they fall through
  * to colorDefaults.
  *
+ * A `[light, dark]` tuple accent seeds each scheme separately: the light
+ * half of every generated `light-dark()` pair comes from the light seed's
+ * palettes, the dark half from the dark seed's. A string accent seeds both
+ * halves from the same palettes, exactly as before tuples were supported.
+ *
  * Without an `accent`, the accent tokens join that fall-through set: the
  * neutrals are seeded from the default accent's hue, and --color-accent,
  * --color-accent-muted and --color-on-accent keep their colorDefaults values.
@@ -168,6 +188,9 @@ export function ensureContrastTone(
  * const tokens = expandColorScale({ accent: '#0064E0' });
  * // tokens['--color-accent'] === 'light-dark(#..., #...)'
  *
+ * const perScheme = expandColorScale({ accent: ['#0064E0', '#48CAE4'] });
+ * // light half derives from #0064E0, dark half from #48CAE4
+ *
  * const neutralOnly = expandColorScale({ neutralStyle: 'warm' });
  * // neutralOnly['--color-accent'] === undefined
  * ```
@@ -175,16 +198,33 @@ export function ensureContrastTone(
 export function expandColorScale(config: ColorScaleConfig): ColorScaleTokens {
   const {accent, neutralStyle = 'cool', contrast = 'standard'} = config;
 
-  const seed = hexToHct(accent ?? DEFAULT_ACCENT_SEED);
-  const seedHue = seed.hue;
+  // Normalize to per-scheme seeds. A string accent (or an absent one) uses
+  // the same seed for both halves, which keeps single-seed output identical
+  // to the pre-tuple implementation.
+  const [lightAccent, darkAccent] = Array.isArray(accent)
+    ? accent
+    : [accent, accent];
+
+  const lightSeed = hexToHct(lightAccent ?? DEFAULT_ACCENT_SEED);
+  const sameSeed = darkAccent === lightAccent;
+  const darkSeed = sameSeed
+    ? lightSeed
+    : hexToHct(darkAccent ?? DEFAULT_ACCENT_SEED);
 
-  const primaryChroma = Math.max(seed.chroma, 48);
   const neutralChroma = NEUTRAL_CHROMA[neutralStyle] ?? 5;
   const neutralVariantChroma = NEUTRAL_VARIANT_CHROMA[neutralStyle] ?? 8;
 
-  const P = tonalPalette(seedHue, primaryChroma);
-  const N = tonalPalette(seedHue, neutralChroma);
-  const NV = tonalPalette(seedHue, neutralVariantChroma);
+  // Palette naming: *L palettes feed the light (first) half of each ld()
+  // pair below, *D palettes the dark (second) half. With a single seed the
+  // D palettes alias the L ones.
+  const PL = tonalPalette(lightSeed.hue, Math.max(lightSeed.chroma, 48));
+  const NL = tonalPalette(lightSeed.hue, neutralChroma);
+  const NVL = tonalPalette(lightSeed.hue, neutralVariantChroma);
+  const PD = sameSeed
+    ? PL
+    : tonalPalette(darkSeed.hue, Math.max(darkSeed.chroma, 48));
+  const ND = sameSeed ? NL : tonalPalette(darkSeed.hue, neutralChroma);
+  const NVD = sameSeed ? NVL : tonalPalette(darkSeed.hue, neutralVariantChroma);
 
   const isHigh = contrast === 'high';
 
@@ -209,19 +249,19 @@ export function expandColorScale(config: ColorScaleConfig): ColorScaleTokens {
   const borderEmphasizedStartDark = isHigh ? 50 : 30;
   const borderEmphasized = ld(
     ensureContrastTone(
-      seedHue,
+      lightSeed.hue,
       neutralVariantChroma,
       borderEmphasizedStartLight,
       -1,
-      N[99],
+      NL[99],
       NON_TEXT_MIN_CONTRAST,
     ),
     ensureContrastTone(
-      seedHue,
+      darkSeed.hue,
       neutralVariantChroma,
       borderEmphasizedStartDark,
       1,
-      N[10],
+      ND[10],
       NON_TEXT_MIN_CONTRAST,
     ),
   );
@@ -234,7 +274,7 @@ export function expandColorScale(config: ColorScaleConfig): ColorScaleTokens {
     // seed above, so a supplied-but-malformed accent keeps its old behavior.
     ...(accent != null
       ? {
-          '--color-accent': ld(P[40], P[80]),
+          '--color-accent': ld(PL[40], PD[80]),
           // Derived accent tokens reference --color-accent instead of baking its
           // resolved hex, so a scoped override of the base token re-accents the
           // whole subtree at runtime. --color-on-accent stays baked: it is a
@@ -243,65 +283,70 @@ export function expandColorScale(config: ColorScaleConfig): ColorScaleTokens {
             accentWithAlpha(0.2),
             accentWithAlpha(0.25),
           ),
-          '--color-on-accent': ld(P[100], P[20]),
+          '--color-on-accent': ld(PL[100], PD[20]),
         }
       : null),
-    '--color-neutral': ld(hexWithAlpha(N[10], 0.1), hexWithAlpha(N[90], 0.2)),
-    '--color-background-surface': ld(N[99], N[10]),
-    '--color-background-body': ld(N[95], N[5]),
-    '--color-overlay': ld(hexWithAlpha(N[10], 0.4), hexWithAlpha(N[10], 0.6)),
+    '--color-neutral': ld(hexWithAlpha(NL[10], 0.1), hexWithAlpha(ND[90], 0.2)),
+    '--color-background-surface': ld(NL[99], ND[10]),
+    '--color-background-body': ld(NL[95], ND[5]),
+    '--color-overlay': ld(hexWithAlpha(NL[10], 0.4), hexWithAlpha(ND[10], 0.6)),
     '--color-overlay-hover': ld(
-      hexWithAlpha(N[10], 0.05),
-      hexWithAlpha(N[100], 0.05),
+      hexWithAlpha(NL[10], 0.05),
+      hexWithAlpha(ND[100], 0.05),
     ),
     '--color-overlay-pressed': ld(
-      hexWithAlpha(N[10], 0.1),
-      hexWithAlpha(N[100], 0.1),
+      hexWithAlpha(NL[10], 0.1),
+      hexWithAlpha(ND[100], 0.1),
     ),
     '--color-background-muted': ld(
-      hexWithAlpha(N[10], 0.05),
-      hexWithAlpha(N[10], 0.5),
+      hexWithAlpha(NL[10], 0.05),
+      hexWithAlpha(ND[10], 0.5),
     ),
 
     // Text
-    '--color-text-primary': ld(N[textPrimaryLightTone], N[textPrimaryDarkTone]),
+    '--color-text-primary': ld(
+      NL[textPrimaryLightTone],
+      ND[textPrimaryDarkTone],
+    ),
     '--color-text-secondary': ld(
-      NV[textSecondaryLightTone],
-      NV[textSecondaryDarkTone],
+      NVL[textSecondaryLightTone],
+      NVD[textSecondaryDarkTone],
     ),
-    '--color-text-disabled': ld(NV[60], NV[40]),
+    '--color-text-disabled': ld(NVL[60], NVD[40]),
     '--color-text-accent': 'var(--color-accent)',
 
     // Icon
     '--color-icon-accent': 'var(--color-accent)',
-    '--color-icon-primary': ld(N[textPrimaryLightTone], N[textPrimaryDarkTone]),
+    '--color-icon-primary': ld(
+      NL[textPrimaryLightTone],
+      ND[textPrimaryDarkTone],
+    ),
     '--color-icon-secondary': ld(
-      NV[textSecondaryLightTone],
-      NV[textSecondaryDarkTone],
+      NVL[textSecondaryLightTone],
+      NVD[textSecondaryDarkTone],
     ),
-    '--color-icon-disabled': ld(NV[60], NV[40]),
+    '--color-icon-disabled': ld(NVL[60], NVD[40]),
 
     // Surface variants
-    '--color-background-card': ld(N[99], N[10]),
-    '--color-background-popover': ld(N[99], N[20]),
-    '--color-background-inverted': ld(N[10], N[99]),
+    '--color-background-card': ld(NL[99], ND[10]),
+    '--color-background-popover': ld(NL[99], ND[20]),
+    '--color-background-inverted': ld(NL[10], ND[99]),
 
-    // Border
     // Border
     // Decorative hairline — not a WCAG 1.4.11 boundary. High contrast
     // doubles the alpha so structural boundaries stay perceivable.
     '--color-border': ld(
-      hexWithAlpha(N[10], borderSubtleAlpha),
-      hexWithAlpha(N[95], borderSubtleAlpha),
+      hexWithAlpha(NL[10], borderSubtleAlpha),
+      hexWithAlpha(ND[95], borderSubtleAlpha),
     ),
     '--color-border-emphasized': borderEmphasized,
 
     // Effects
-    '--color-skeleton': ld(NV[70], NV[30]),
+    '--color-skeleton': ld(NVL[70], NVD[30]),
     // Channel-on-body surface (ProgressBar/Slider tracks, Switch off-state).
     // Defaults to the same NV[70]/NV[30] ramp stop as --color-skeleton.
-    '--color-track': ld(NV[70], NV[30]),
-    '--color-shadow': ld(hexWithAlpha(N[0], 0.1), hexWithAlpha(N[0], 0.3)),
+    '--color-track': ld(NVL[70], NVD[30]),
+    '--color-shadow': ld(hexWithAlpha(NL[0], 0.1), hexWithAlpha(ND[0], 0.3)),
     '--color-tint-hover': ld('black', 'white'),
   };
 }

package/src/utils/ime.test.ts

@@ -0,0 +1,32 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+import {describe, expect, it} from 'vitest';
+import {isImeKeyEvent} from './ime';
+
+describe('isImeKeyEvent', () => {
+  it('detects the modern isComposing signal', () => {
+    expect(isImeKeyEvent({isComposing: true})).toBe(true);
+    expect(isImeKeyEvent({isComposing: true, keyCode: 13})).toBe(true);
+  });
+
+  it('detects the legacy keyCode 229 fallback (IME processing sentinel)', () => {
+    // Some IMEs / older Safari fire the composing keydown with isComposing
+    // not yet set to true but report keyCode 229.
+    expect(isImeKeyEvent({keyCode: 229})).toBe(true);
+    expect(isImeKeyEvent({isComposing: false, keyCode: 229})).toBe(true);
+  });
+
+  it('returns false for ordinary (non-composing) keydowns', () => {
+    expect(isImeKeyEvent({})).toBe(false);
+    expect(isImeKeyEvent({isComposing: false})).toBe(false);
+    expect(isImeKeyEvent({keyCode: 13})).toBe(false); // plain Enter
+    expect(isImeKeyEvent({keyCode: 27})).toBe(false); // plain Escape
+    expect(isImeKeyEvent({isComposing: false, keyCode: 13})).toBe(false);
+  });
+
+  it('only treats a literal `true` isComposing as composing', () => {
+    // Guards against truthy-but-not-true values leaking through.
+    // @ts-expect-error intentionally passing a non-boolean to assert strictness
+    expect(isImeKeyEvent({isComposing: 1})).toBe(false);
+  });
+});

package/src/utils/ime.ts

@@ -0,0 +1,69 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+/**
+ * @file ime.ts
+ * @input Receives a keyboard event (React SyntheticEvent's `nativeEvent`, or a
+ *   native DOM KeyboardEvent) with optional `isComposing` / `keyCode`.
+ * @output Exports `isImeKeyEvent`, the canonical predicate for "this keydown is
+ *   part of an in-progress IME composition and must not be treated as a command".
+ * @position Shared low-level utility; consumed by every editable/overlay surface
+ *   that handles Enter/Escape/arrows in `onKeyDown` (Typeahead, PowerSearch,
+ *   Dialog, ContextMenu, Tooltip, Chat composer, focus-trap Escape, ...).
+ *
+ * ── Why this exists (read once, here — do not re-explain at call sites) ──
+ *
+ * When a CJK user (Korean / Japanese / Chinese) is composing text via an IME,
+ * the browser fires a `keydown` event to COMMIT or CANCEL the pending
+ * composition (Enter commits the highlighted candidate; Escape cancels it;
+ * ArrowUp/Down/Home/End navigate the candidate window). Crucially this
+ * `keydown` fires BEFORE the `compositionend` event that actually writes the
+ * committed text into the field. So a naive `onKeyDown` handler sees a bare
+ * "Enter" or "Escape" and misreads the composition-commit/cancel as an
+ * application command — accepting a typeahead suggestion, submitting a chat
+ * message, closing a dialog/menu/tooltip, or saving a filter — mid-composition.
+ * The fix is to detect the composing keydown and early-return before running
+ * any command logic.
+ *
+ * Two signals, both needed:
+ *
+ *  1. `event.isComposing === true` — the modern, spec'd signal
+ *     (https://www.w3.org/TR/uievents/#dom-keyboardevent-iscomposing). This is
+ *     the primary check and is reliable in current evergreen browsers.
+ *
+ *  2. `event.keyCode === 229` — the legacy fallback. `229` is the sentinel
+ *     keyCode browsers report for "the key event is being processed by an IME".
+ *     It is still load-bearing: some IMEs and older Safari fire the composing
+ *     `keydown` with `isComposing` NOT yet set to `true`, but DO report
+ *     keyCode 229. Keeping both makes the guard robust across the browser
+ *     matrix we support. Do not drop the 229 fallback without a browser-matrix
+ *     audit.
+ *
+ * ── Which event object to pass ──
+ *
+ * React's SyntheticEvent for KeyboardEvent *does* surface `isComposing`, but to
+ * avoid any cross-browser normalization gap prefer passing the *native* event
+ * (`e.nativeEvent`) from React handlers — that is what BaseTypeahead,
+ * PowerSearch, and the Chat composer do. Native DOM listeners (Dialog,
+ * ContextMenu, Tooltip, focus-trap) pass the DOM `KeyboardEvent` directly.
+ * The parameter is intentionally structurally typed so both shapes are accepted.
+ *
+ * Note: `keyCode` is deprecated on the DOM `KeyboardEvent` type but is still
+ * present at runtime; we read it defensively via the optional structural field.
+ */
+
+/**
+ * The sentinel `keyCode` browsers report while a key event is being processed
+ * by an IME (the composing keydown that fires before `compositionend`). See the
+ * file header for why this legacy signal is still load-bearing alongside
+ * `isComposing`.
+ */
+const IME_PROCESSING_KEY_CODE = 229;
+
+export function isImeKeyEvent(event: {
+  isComposing?: boolean;
+  keyCode?: number;
+}): boolean {
+  return (
+    event.isComposing === true || event.keyCode === IME_PROCESSING_KEY_CODE
+  );
+}

package/src/utils/index.ts

@@ -107,3 +107,5 @@ export {rtlStyles} from './rtlStyles';
 // The shared focus ring, exported for @astryxdesign/lab — same reason
 // rtlStyles is: a style that must be identical across packages, not copied.
 export {focusOutlineStyles, focusOutlineProps} from './focusOutline.stylex';
+
+export {isImeKeyEvent} from './ime';