@hshoff, @williaster, @mtlewis

Sorry for pestering. Anyone of you who could help on a consulting basis on the above and some other things? Or happy to donate to the project or charity for help with this one. 🙏 It's proven a bit of a blocker for us.

I did some more debugging @williaster. The mouseover is firing as expected but the svgPoint = null:

This seems to be because the useEventHandlers is not called. Essentially the XYChart is not rerendering.
If I put a log here, it will only be called ca: 10 times and then not rerender on mouseover, even if the event is emitted:

export default function XYChart< .... 

console.log("Is it calling useEventHandlers?")

useEventHandlers({
    dataKey:
      pointerEventsDataKey === "nearest"
        ? POINTER_EVENTS_NEAREST
        : POINTER_EVENTS_ALL,
    onPointerMove,
    onPointerOut,
    onPointerUp,
    onPointerDown,
    allowedSources: allowedEventSources,
  })

What is it that should cause the XYChart to rerender on mousemove fundamentally? Is it that the TooltipProvider changes? Or is there some other effect that is not triggering here?

@williaster

Found the issue!

"event.nativeEvent instanceof Event" is not working as expected within the iframe context:

AI helped me explain why ...

The instanceof operator checks if an object is an instance of a specific class or constructor function. However, it may not work as expected across different JavaScript contexts, such as different iframes, due to the way JavaScript handles different global environments.

When you use instanceof inside an iframe, the constructor function (e.g., Event) is from the iframe's global context, which is different from the global context of the parent window. Consequently, objects created in one context do not pass the instanceof check for constructor functions in another context.

Here’s why this happens:

Separate Global Objects: Each iframe has its own global object, which includes its own versions of Event, Array, Object, and other built-in constructors. Therefore, window.Event in the main document is different from iframe.contentWindow.Event.

Different References: An event created in the main document will be an instance of window.Event, but not of iframe.contentWindow.Event, even though both refer to the Event constructor.

To check if an object is an instance of Event across different contexts, you can use a combination of techniques:

Duck Typing: Check for properties and methods that are unique to the Event object.
Cross-context Checks: Use the constructor.name property to check the type by name.
Using typeof and Object.prototype.toString.call(): These can sometimes help identify the object type more reliably across different contexts.

When I patch this, the Tooltips show up as expected. But the next issue I'm facing is with: getXAndYFromEvent where these will be need to be offset for the iFrame scenario I believe:

x: event.clientX,
y: event.clientY

I think this is a smaller fix to account for this scenario.

Can I submit a PR that aims to fix both of these? Thank you!

Hey @lapidus thanks much for digging in here - was initially surprised at this behavior but that makes complete sense.

We would happily review a PR with the 2x fixes mentioned.

Thank you @williaster!

I made some progress on the PR:
#1848

Now the tooltip shows almost correctly.
But I can't get it to position itself adequately. I think it has to do with this part:

// To correctly position itself in a Portal, the tooltip must know its container bounds
// this is done by rendering an invisible node whose ref can be used to find its parentElement

I tried correcting for the iframe offsets here:
https://github.com/airbnb/visx/pull/1848/files#diff-be158cfaccba14687300842e06a1700307de86e6727d08beb2c112eaa49c6813R171

Appreciate if you can take a closer look. Thank you.