Bryce Osterhaus

@matuzalemsteles thats a great idea! Would you be up for creating that? I think you have a better idea of the DataProvider and would know which issues to filter through...

This might be something the user intentionally implements. AFAIK, our tooltips are written to follow the html standard for `title`, and html standard for titles isn't super great for touch...

@marcoscv-work I think it really depends on the use case, are you thinking we would provide an accessible tooltip on mobile for all `title` attributes? Currently our `ClayTooltipProvider` will automatically...

Great idea to me. This is a very similar idea that we did for portal with [liferay-npm-scripts](https://github.com/bryceosterhaus/liferay-npm-tools/tree/master/packages/liferay-npm-scripts). The pain points are a little different, in portal we wanted to give...

Yeah I think its best to keep it around but not actively seek it out at the moment.

I just tested @pat270s suggestion and overflow seems to work fine for alerts to go off the screen. As for the order in which the elements appear, that is up...

> @wincent > It's made Clay harder to use than necessary for teams working in liferay-portal Any particular areas that have been hard about it? I really haven't heard much...

> One clear pitfall is that Clay is not easily usable from JSPs (which make up for a sizeable portion of the products). > ... > The most standard, stable...

> Analytics Cloud would be a good testbed for our React components... but I don't see Clay gaining much traction there, and they seem comfortable with what they have. I'd...

Okay, so I think we all agree that DXP is our primary target and end user, and so we need to primarily build with that in mind. So no need...