fix: Switching between browser tabs can cause illegible text color for config parameter value field

[mtrezza]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

The TextInput component doesn't have an explicit color property defined, which means it relies on CSS inheritance. When navigating between tabs, sometimes the browser's paint/style recalculation can cause issues with CSS inheritance, especially if there's any dynamic styling or state changes.

Approach

Added an explicit color property to .text_input class to ensure the text input color is always defined.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds explicit color styling to the TextInput component, setting the base text color to black and introducing a disabled state rule that applies a SCSS variable for disabled input color.

Changes

Cohort / File(s)	Summary
TextInput styling src/components/TextInput/TextInput.scss	Adds color: #000; to base TextInput rules and introduces a disabled state rule that applies $mainTextColor variable when input is disabled

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "fix: Switching between browser tabs can cause illegible text color for config parameter value field" is directly related to the changeset, which adds explicit color styling to the TextInput component to fix CSS inheritance issues. While the title describes the symptom rather than the implementation detail, it accurately conveys the purpose and intent of the fix. The title is specific enough that a teammate reviewing the commit history would understand this addresses a text color visibility problem in the TextInput component.
Description Check	✅ Passed	The pull request description includes the required template structure with most key sections properly populated. The Issue Description section clearly explains the problem with CSS inheritance when navigating between tabs, and the Approach section describes the solution of adding explicit color properties. However, the checklist items at the top are unchecked and the approach section provided is relatively brief, though it does capture the core intent. The description is substantively complete enough to understand the change's purpose and approach.

✨ Finishing touches

🧪 Generate unit tests (beta)

• 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 fc2bf6a and bc26170.

📒 Files selected for processing (1)

• src/components/TextInput/TextInput.scss (2 hunks)

⏰ 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: Docker linux/amd64

🔇 Additional comments (3)

src/components/TextInput/TextInput.scss (3)

15-15: Verify compatibility with dark mode or theme support.

The hardcoded color: #000 explicitly sets the text to black. While this addresses the illegible text issue by ensuring an explicit color is applied, verify that this doesn't conflict with any dark mode, high-contrast, or theming support elsewhere in the project.

• Does the project support dark mode or multiple color themes?
• If yes, does this hardcoded black color have adequate contrast in all theme contexts?

---

24-26: Verify that $mainTextColor is semantically appropriate for disabled inputs.

The disabled state styling uses the $mainTextColor SCSS variable. Confirm this is the intended semantic choice for disabled input styling (e.g., a muted or lighter color that signals a disabled state).

---

1-50: PR template and deliverables incomplete before merge.

The PR description indicates unchecked TODOs:

• Add tests
• Add changes to documentation

Additionally, the issue reference placeholder "Closes: FILL_THIS_OUT" is not filled in. Before merging, ensure these items are addressed per project policy.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[parseplatformorg]

🎉 This change has been released in version 8.0.0-alpha.5