User Paths dropdown UX feels buggy

[samwinslow]

Bug description

User Paths needs more than cosmetic fixes — we need to consider reorganizing the architecture of information shown to the user, and also the underlying data structures. It took me hours to understand how I'd even use this feature.

• I thought the app was broken and leaking DOM strings here. We should show HTML element tags with distinct typography.

• Why are we separating autocaptured vs. custom events? It seems like we don't do this in other parts of the app.
• We should not refer to URLs as "elements".
• Revise empty-state copy: makes reference to $pageview when this may or may not be relevant.

Expected behavior

Unified menu such as we are now using for property filters elsewhere. Icons to differentiate events, URLs, and DOM elements.

How to reproduce

1. Use anything other than the defaults in User Paths, and observe as if you were a first-time user.

Environment

• PostHog Cloud
• self-hosted PostHog, version/commit: please provide

Additional context

Thank you for your bug report – we love squashing them!

[marcushyett-ph]

This will likely be valuable for our next milestone

[paolodamico]

This has been fixed by the new paths UI.