Version 0.5.4a of the LogUI client introduces some small changes in the way that event bubbling is handled. This is to be tested more to ensure that all functionality remains consistent.
Instead of dropping events if an event's eventPhase is not set to 2 (i.e., bubbling has stopped), we ditch this requirement. This is because certain webpage designs where nested elements existed within a parent element, which has a configuration associated with it, fails to trigger correctly because bubbling is stopped. We also switch from target to currentTarget to more reliably work out what element is actually being interacted with in the eventCallbackHandler. From testing so far, no adverse effects have been observed from this change. I'll keep an eye out for any changes that are derived from this change.
I've also added the onElement to the elementProperty metadata sourcer. This allows LogUI to extract a property from a different element from the one that the user interacts with. In some scenarios, this may be useful (e.g., wanting the value of a form element on submission). Documentation on this change is available here.