+2This div is being used as a button, so I’m mapping it using “div[title=”Delete activity”]
When the div is clicked, notice that the title attribute’s value is not included in the payload:
Has anyone else ever run into this issue before? Were you able to determine a root cause?
Best answer by rschlette
Looping back here to share the root cause:
The application we’re mapping has implemented a 3rd party library to add custom tool tips to the UI. At the same time, the default browser behavior will show a native tooltip on hover, and the default value for those native tooltips is the title attribute (where available). If you allow both of these things to run in the browser, you’ll get a multiple tooltips on hover.
To avoid these collisions, the dev team has an event listener on the onHover action that strips out the title attribute values. So the workflow becomes:
So the effective situation is that there are title attributes in the source code, but they aren’t usable in runtime because of that tooltip collision management.
+2
+2
Is it “some” buttons or “all” buttons with a title attribute value not included in the tracked click event?
+2Thanks for taking a look, Link. It’s any/all elements that have a title attribute. The title attribute is getting tracked as expected based on the custom DOM attributes inclusion, but contrary to the source code, the value for that title attribute is always blank. The issue is completely isolated to this one product, so I don’t think it’s a PX issue; just trying to figure out precisely what the issue is or could be.
I’m going to put the details in a support ticket, and maybe that team can see old tickets/Slacks where this came up in the past. I know it has, but managed to retain nothing from that experience 😂
+2Sure. there could be some JavaScript at play in that app that removes/updates the title attribute before PX can capture it, but I just don’t know. 🤔
+2Looping back here to share the root cause:
The application we’re mapping has implemented a 3rd party library to add custom tool tips to the UI. At the same time, the default browser behavior will show a native tooltip on hover, and the default value for those native tooltips is the title attribute (where available). If you allow both of these things to run in the browser, you’ll get a multiple tooltips on hover.
To avoid these collisions, the dev team has an event listener on the onHover action that strips out the title attribute values. So the workflow becomes:
So the effective situation is that there are title attributes in the source code, but they aren’t usable in runtime because of that tooltip collision management.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
