Patrick Yeo

@marcoscv-work I decided it's better to use Sass color functions to derive the `L0` colors just in case someone is relying on it. I think we can change the colors...

We will need to add some CSS variants. I think we can use the existing markup, but need to add the `dropdown-menu` class on the items which is a bit...

@ethib137 Good catch, I'll update it. Standard inputs are a fixed width and can't grow with its content. There is some discussion at https://liferay.atlassian.net/browse/LPD-53482?focusedCommentId=2911231

@ethib137 I've been trying to get the value to display in the contenteditable element, but I'm running into some React quirks. Using `{value}` in the contenteditable span causes the text...

Closing this since it was discarded, will reopen if revisited.

@ethib137 I'm not totally against this other than the breaking changes part. It still runs into the same problem where we need to declare the disabled colors on `.btn-primary`. In...

@ethib137 Thanks for the example, that would indeed work. The underlying CSS is being changed, but I don't think it would affect people overwriting our components via a separate CSS...

I fired this pr up and I'm getting an error on Async Filter, Infinite Scroller, and Async Data. 

@matuzalemsteles It's not working correctly for me for some reason. Here is a gif of what I'm seeing. 

@matuzalemsteles I got it to work. Some of the left/right error stuff just needed to be swapped.