-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Correlation Analysis details not closing UI element #10275
Comments
This is definitely deviating from our other overlay patterns. The overlay should be semi-transparent, and the modal should be aligned to other modal instances. Here's a redraw that aligns the content to other modal examples. I removed the footer as it always adds up to 100%, so didn't feel like it was adding much. |
@clarkus I picked up this issue and tried recreating the issue but no luck yet. Can you help by sharing the steps to recreate it? |
Go to a funnel -> add events -> scroll down to correlation table -> click three dots at the rightmost end of the table -> click 'view correlation details' -> see the above happen. |
@clarkus how do I get to locate a funnel |
@neilkakkar The experience is different for me on my side. I see this on the insight page. I open one of the items, I have to click edit on the inner page and then navigate to the funnel tab but I do not see correlation table option |
Hey @AsiwajuDev , my bad, didn't realise this was an enterprise feature 😅 . I'd recommend switching to another issue. Something labelled good first issue is ideal: https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
Bug description
Then I click for detail on a correlation analysis result, this is what I see:
Blacking out the background and creating a pop-up I can understand, but leaving the 'View correlation details' box popped up and in-focus seems like a mistake.
How to reproduce
Environment
Additional context
Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: