This issue was encountered whilst trying to resolve
FLOE-361. It was found that our default policy of applying items: "*" as an option to the underlying jQuery UI widget was causing interaction problems - mouse movement (or clicking) within an item that should have counted as a single tooltip source would cause the tooltip to redisplay as well as potentially also swallowing the event.
However, attempting to reconfigure the "items" option to be more specific caused problems of its own. As diagnosed on the JIRA, this would cause any tooltips constructed by the component to accumulate endlessly if some collateral event caused them to be closed (where "collateral" signifies "outside the direct influence of the underlying UI widget" - for example, re-rendering, or opening of a different tooltip).
The diagnosis on
FLOE-361 is correct - the root cause is that the id stored in the Infusion component's openIdMap is incorrect and is that of the event target rather than the one that jQuery UI believes to be the tooltip target. As a result, jQuery UI ignores the request to "close" the tooltip when we ask for it by this id.
The resolution is to add an extra piece of solution in addition to "fluid.resolveEventTarget" in order to ensure that we only ever dispatch a valid node matched by "items" to the underlying UI widget's close method.