text-area `disabled` state low-contrast

[nwhittaker]

Check existing issues

• [X] I have checked for existing issues to avoid duplicates

Actual Behavior

The disabled state for a text-area element is very low contrast and inconsistent with the disabled state of the other input components.

Expected Behavior

I was expecting the colors used in the text-area's disabled state to match the colors used in the inputs' disabled state.

Reproduction Sample

https://codepen.io/nwhittaker-esri/pen/ZEwwwMy

Reproduction Steps

Visit the repro. and visually compare the disabled components.

Reproduction Version

2.0.0

Relevant Info

Inspecting the calcite-text-area component, it looks like a 0.5 opacity is getting doubly applied. Once to the :host and once to the :host textarea element.

Regression?

No response

Priority impact

p3 - want for upcoming milestone

Impact

No response

Calcite package

• [X] @esri/calcite-components
• [ ] @esri/calcite-components-angular
• [ ] @esri/calcite-components-react
• [ ] @esri/calcite-design-tokens
• [ ] @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Field Apps

[geospatialem]

Adding design folks to this issue to determine next steps and evaluation across the components in alignment with textarea.

[ashetland]

@geospatialem Next steps are to remove the double opacity, matching the above expected behavior. If there are no other questions, we should be able to mark this ready for dev.

[geospatialem]

@geospatialem Next steps are to remove the double opacity, matching the above expected behavior. If there are no other questions, we should be able to mark this ready for dev.

@ashetland Awesome, think we'd just need a Figma url, or screenshot of the expected outcome then this is ready for dev 🚀 .

[github-actions[bot]]

cc @geospatialem, @brittneytewks

[github-actions[bot]]

Installed and assigned for verification.

[DitwanP]

🍬 Verified on 2.9.0-next.18