fix: [M3-9968] - Input placholder opacity #12208
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abailly-akamai
requested review from
carrillo-erik and
harsh-akamai
and removed request for
a team
Cloud Manager UI test results🎉 586 passing tests on test run #2 ↗︎
|
harsh-akamai
approved these changes
May 14, 2025
carrillo-erik
approved these changes
May 14, 2025
bnussman-akamai
added
Approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description 📝
Small PR to fix the placeholder opacity so we are showing the right color. Right now the placeholder text is barely readable (likely failing most accessibility standards), because of the default opacity applied to it in the MUI styles.
This style change will apply to all text inputs (Textfield, Text area, Autocomplete etc)
Changes 🔄
1to get the proper CDS placeholder colorPreview 📷
How to test 🧪
Verification steps
Check placeholder treatment for inputs through the application
Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅