Skip to content

Conversation

alessiocappa
Copy link

@alessiocappa alessiocappa commented Sep 28, 2025

I noticed that all the input fields have the overflow property set to hidden, and white-space set to nowrap.
This creates visibility issues in case of textarea elements, because the whole text is displayed on a single line and there is no scrollbar, so no way to easily move to a specific point of the text.

It is pretty noticeable, for instance, in the transaction notes:

Screenshot 2025-09-29 alle 01 14 32

This is how it looks after removing the CSS properties:

Screenshot 2025-09-29 alle 01 14 19

Summary by CodeRabbit

  • Style
    • Input fields no longer truncate long text with an ellipsis; full content is now visible instead of being cut off.
    • Improves readability when reviewing and editing long values in form fields.
    • No changes to form interactions or validation; only visual presentation is affected.

Copy link

coderabbitai bot commented Sep 28, 2025

Walkthrough

Removed the Tailwind @apply rule enforcing text-ellipsis, overflow-hidden, and whitespace-nowrap on .form-field__input in maybe-design-system.css. This change stops automatic truncation/ellipsis for form inputs; other styles and control flow remain unchanged.

Changes

Cohort / File(s) Summary
Form input truncation styles
app/assets/tailwind/maybe-design-system.css
Removed @apply of text-ellipsis, overflow-hidden, and whitespace-nowrap from .form-field__input, lifting forced truncation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A nibble of CSS, a hop in the field,
No more clipped words—true lengths revealed.
Inputs stretch wide, like burrows at night,
Lines run free in the moon’s soft light.
I twitch my whiskers: “No ellipses tonight!” 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly describes the main change of the pull request, which is to address the rendering behavior of textarea elements by removing CSS rules causing them to display as a single line without scrollbars, and it is concise, clear, and directly related to the change set.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 617876f and 0b5e5b6.

📒 Files selected for processing (1)
  • app/assets/tailwind/maybe-design-system.css (0 hunks)
💤 Files with no reviewable changes (1)
  • app/assets/tailwind/maybe-design-system.css
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: ci / test

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant