Currently (and especially with default event-targets like BODY > DIV:nth-child(2) > DIV:nth-child(1) > DIV:nth-child(1) > MAIN:nth-child(3) > DIV:nth-child(2) > FORM:nth-child(2) > LABEL:nth-child(1) > INPUT:nth-child(1)), it can be hard to tell what an event actually is.
#11 will help with this.
But we should also make that feature where we load a target page in an iframe, so users can hover over elements of their site to name events. "Clicking on this thing mean someone just made an in-app purchase"
Currently (and especially with default event-targets like
BODY > DIV:nth-child(2) > DIV:nth-child(1) > DIV:nth-child(1) > MAIN:nth-child(3) > DIV:nth-child(2) > FORM:nth-child(2) > LABEL:nth-child(1) > INPUT:nth-child(1)), it can be hard to tell what an event actually is.#11 will help with this.
But we should also make that feature where we load a target page in an iframe, so users can hover over elements of their site to name events. "Clicking on this thing mean someone just made an in-app purchase"