Skip to content

Enhanced ChatGPT Clone: Features Agents, MCP, Skills, DeepSeek, Anthropic, AWS, OpenAI, Responses API, Azure, Groq, o1, GPT-5, Mistral, OpenRouter, Vertex AI, Gemini, Artifacts, AI model switching, message search, Code Interpreter, langchain, DALL-E-3, OpenAPI Actions, Functions, Secure Multi-User Auth, Presets, open-source for self-hosting. Active

5.4 KB
Raw Blame
/* Shared Input/Textarea (.lc-field): show the focus ring for keyboard users
   only. Text inputs match :focus-visible on pointer focus too (a UA heuristic
   CSS cannot distinguish), so the ring is gated on the input modality tracked
   by useInputModality (mount it once near the app root). Without the hook the
   attribute is absent and the ring always shows, which is the safe fallback.
   A theme that focuses fields by swapping their edge (`fieldFocusStyle: border`)
   keeps that edge on pointer focus too, so it puts the edge back over the
   reset. The style is read from the `--theme-field-focus-style` property of the
   nearest themed root, so a field under a ring root nested in a border root is
   reset again, and a browser without style queries keeps the default reset. A field marked
   `aria-invalid` keeps its destructive edge through both border resets but still
   loses the ring and outline on pointer focus. The framed and flush editors
   (`lc-own-focus`) take the same ring and outline reset, so they behave alike
   without the SPA's global textarea rules. */
html[data-input-modality='pointer'] :is(.lc-field, .lc-own-focus):focus,
html[data-input-modality='pointer'] :is(.lc-field, .lc-own-focus):focus-visible {
  box-shadow: none;
  outline: none;
}

html[data-input-modality='pointer'] .lc-field:not([aria-invalid='true']):focus,
html[data-input-modality='pointer'] .lc-field:not([aria-invalid='true']):focus-visible {
  border-color: rgb(var(--border-light) / var(--border-light-alpha, 1));
}

@container style(--theme-field-focus-style: border) {
  html[data-input-modality='pointer'] .lc-field:not([aria-invalid='true']):is(:root *):focus,
  html[data-input-modality='pointer']
    .lc-field:not([aria-invalid='true']):is(:root *):focus-visible {
    border-color: rgb(var(--border-field-focus, var(--focus-control)));
  }
}

/* A field draws its own indicator (the ring, or the swapped edge), so it draws no outline too.
   The app's dark-mode `:focus-visible` outline is unlayered, so it outranks the field's own
   `focus-visible:outline-hidden` utility and would add a second indicator; `:is(:root *)` keeps
   this rule's weight above it. Forced colors drop the edge color and the ring, so there the
   outline stays as the only indicator, and the contrast modes enlarge the outline to 3px on
   purpose, so `html.high-contrast` keeps it. */
@media not (forced-colors: active) {
  html:not(.high-contrast) .lc-field:focus-visible {
    outline: none;
  }
}

/* The floating-label field (`floatingField`) paints its own fill over the browser's autofill, so
   an autofilled sign-in field keeps the theme's field color instead of the UA's yellow. The mask
   is one entry of the box-shadow list, followed by the ring and shadow layers Tailwind composes,
   so the field's keyboard ring still paints over it. */
.webkit-dark-styles {
  --lc-autofill-mask: 0 0 0 50vh rgb(var(--field-fill, var(--surface-primary))) inset;
}

.webkit-dark-styles,
.webkit-dark-styles:focus {
  background-clip: content-box;
  box-shadow:
    var(--lc-autofill-mask), var(--tw-ring-offset-shadow, 0 0 transparent),
    var(--tw-ring-shadow, 0 0 transparent), var(--tw-shadow, 0 0 transparent);
}

html[data-input-modality='pointer'] .lc-field.webkit-dark-styles:focus,
html[data-input-modality='pointer'] .lc-field.webkit-dark-styles:focus-visible {
  box-shadow: var(--lc-autofill-mask);
}

.dark .webkit-dark-styles,
.dark .webkit-dark-styles:focus {
  -webkit-text-fill-color: rgb(var(--field-text, var(--text-primary)));
}

/* A control outside `.lc-field` that carries `lc-own-focus` (the framed and flush editors) has
   its own ring, or a frame that owns the indicator, so the app's global focus outline for
   non-`.lc-field` textareas would add a second one. `:root` lifts this above that rule's
   weight; forced colors keep the outline as the only indicator, and the contrast modes keep
   their enlarged outline. */
@media not (forced-colors: active) {
  html:root:not(.high-contrast) textarea.lc-own-focus:focus-visible {
    outline: none !important;
  }
}

/* iOS zooms into a focused field under 16px and the installed PWA never zooms back out. On touch
   devices every text entry control keeps at least 16px, wherever a caller sizes it. Sizes at
   text-base or above keep their own value, floored the same way for a small UI scale. This sits in
   the package stylesheet so standalone consumers get it too; the composer and message editor in
   the app size themselves from the chat font setting and are excluded here. */
@media (any-pointer: coarse) {
  :is(
    input:not([type]),
    input:is(
      [type='text'],
      [type='email'],
      [type='password'],
      [type='search'],
      [type='url'],
      [type='tel'],
      [type='number'],
      [type='date'],
      [type='time'],
      [type='datetime-local'],
      [type='month'],
      [type='week']
    ),
    textarea,
    select
  ) {
    &:not(
      .text-base,
      .text-lg,
      .text-xl,
      .text-2xl,
      .text-3xl,
      .message-editor-text,
      .composer-text
    ) {
      font-size: max(16px, 0.875rem);
    }

    &.text-base {
      font-size: max(16px, var(--text-base, 1rem));
    }

    &.text-lg {
      font-size: max(16px, var(--text-lg, 1.125rem));
    }

    &.text-xl {
      font-size: max(16px, var(--text-xl, 1.25rem));
    }

    &.text-2xl {
      font-size: max(16px, var(--text-2xl, 1.5rem));
    }

    &.text-3xl {
      font-size: max(16px, var(--text-3xl, 1.875rem));
    }
  }
}