To use this feature, you have to use Google Chrome as the browser and install the JProfiler origin tracker extension.
When tracking is activated, the JProfiler extension will ask you to reload the page. This is necessary for adding instrumentation. If you choose to not reload the page, event detection may not work.
The tracking status is persistent on a per-domain basis. If you restart the browser while tracking is active and visit the same URL, tracking will automatically be enabled, without the need to reload the page.
At the top of the tree you find browser event nodes that show event name and element name together with important attributes that help you pin down the source of the event. Not all requests have an associated event.
target node of an event up to the node where the event listener is located, looking for attributes that are
suitable for display and splitting the call tree. Failing to find framework-specific attributes, it stops at
id attribute. In the absence of an ID, it searches for "control elements" like
input. All failing, the element where the event listener is registered
will be shown.
In some cases, the automatic detection of interesting attributes may not be suitable and you may prefer a different call tree splitting. For example, some frameworks assign automatic IDs, but it would be more readable to group all elements together with a semantic description of the action. To achieve a different call tree splitting, add the HTML attribute
to the target element or an element between the target and the location of the event listener. The text in that attribute will be used for splitting and other attributes will be ignored.
Call tree splitting
In the call tree view, XHR calls will split the call tree for each separate combination of browser event
and call stack. The splitting nodes
show information about the browser event. If no event is in progress, like in a call to
the last few stack frames are displayed inline.