Michael Coker

Looks like this is a CSS problem and only occurs when the form control's value is selected from autofill. Chrome is applying a `background` with `!important`, that overrides the background...

A potential fix - https://codepen.io/mcoker/pen/rNVegEX

Hey @skobyda! Dark theme styles are overrides of default styles, and `$pf-color-blue-400` is defined in our default SCSS in [src/patternfly/sass-utilities/colors.scss](https://github.com/patternfly/patternfly/blob/main/src/patternfly/sass-utilities/colors.scss). There are a bunch of SCSS base vars, mixins, etc...

I like this as the default, too, though we did decide to have the horizontal filter overflow scroll as a single line as opposed to wrap like this (and typeahead...

@mcarrano ^ - @srambach's codepen is what I was going to create last time we discussed this issue.

> B. add a class to the chip indicating it should stick @srambach do you mean add a class to the chip group item (`.pf-c-chip-group__list-item`)? If so, I'm in favor...

> Implement a scroll variant of a chip group, which does not wrap but remains on one line with a gradient indicating when there is something scrolled off to one...

@srambach would it still be an option to add the shadows via a class on the react side, depending on which direction has overflow?

@mcarrano @mmenestr a couple of thoughts come to mind. There is padding around the form control elements - would we keep that so that switching between readonly and non won't...

> Is it possible to just localize this change to the single line text input and not the text area @mcoker ? Yep. Also you mentioned the clipboard copy component...