Chris Clark

Love that you're thinking about and testing for this. We went through extensive contrast checks when updating the color palette recently and all the button colors passed contrast checks. There...

> @clarkus would love your advise on the Dashboard Insight "Show details" button as that's the only hard one to work around. I guess Experiment Success button could just become...

> So is that removing what the implementation calls `type=secondary status=muted-alt` and replacing it with `type=secondary status=muted-alt` > > > > Or removing _all_ `muted-alt` options in favour of `primary-alt`?...

For contrast on primary destructive, it looks like the font-weight might be wrong. In figma the buttons use a mid-range emphasis value (with the Inter font, I'd say `font-weight:500` or...

@lottiecoxon This work is being considered for the upcoming sprint. Can you move the art boards that are being considered into the posthog app project in figma just so it's...

Inline CSS is the hardest to override in terms of inheritance / cascade. I typically aim for 240px for a search input, but it varies based on context. In some...

> That said, happy to set a default width for inputs but seeing as this would apply to all inputs, it is hard to say what the wider impact would...

> Because the search input is just an input with a search icon. I can make it a fully fledged unique component if you think it is worth it? Can't...

Related https://github.com/PostHog/posthog/issues/11128

I am all for answering this question, but I would encourage us to ask it after the main objectives of onboarding are complete. Anytime we add another field, it can...