And maybe this._source.fire('tooltipclose', {tooltip: this}, true); should be then fired on the tooltip self and with the event parent it is also fired on the source layer

And maybe this._source.fire('tooltipclose', {tooltip: this}, true); should be then fired on the tooltip self and with the event parent it is also fired on the source layer

Please explain what you mean

With this._source.fire('tooltipclose', {tooltip: this}, true); the event tooltipclose is only fired on the source layer, but it would make sense to fire this on the tooltip too. So it should changed to this.fire('tooltipclose', {tooltip: this}, true);

So it should changed to this.fire

No, it should fire on source layer - it is really intended so.

Next step to mark PR "ready for review"

Next step is decide how to be with closing on preclick.

P.S.
And final step - describe possible use cases. Do you have some?

No, it should fire on source layer - it is really intended so.

But why? A tooltip can also be a own layer on the map, so why not fireing events on it? And with the event parent it still fires on the source layer.

		var tooltip = L.tooltip().setContent('Tooltip');
		map.openTooltip(tooltip, map.getCenter());
		
		tooltip.on('tooltipclose',(e)=>console.log('Tooltip',e));
		map.on('tooltipclose',(e)=>console.log('Map',e));

But why? A tooltip can also be a own layer on the map, [...]

So it already has all related events ('remove', not 'tooltipclose')

So it already has all related events ('remove', not 'tooltipclose')

Ok yes sorry, you are right didn't thought about that one.

Next step is decide how to be with closing on preclick.

Ah sorry, didn't thought that you want to add this in this PR.
I don't think that the new function instead of preclick will be good, because it breaks current behaviour. It doesn't close anymore on click on the map or on the tooltip. It closes only if a new tooltip is open or closeTooltip() is called.

And final step - describe possible use cases. Do you have some?

I know that I had some usecase where I wanted to add a click listener on the tooltip. But I don't know for what exactly anymore.
Other usecases would be to make Tooltips dragable, specially if they are added as a own layer without "source". Or to make a "Click me to revert" Tooltip after removing a layer, ...

It doesn't close anymore on click on the map or on the tooltip.

It will be easy to add too, but with clear map click.

Ah sorry, didn't thought that you want to add this in this PR.

But you are right, it is not necessary in this PR.

I know that I had some usecase

Me too)

Good point.

This section is missing:

May be this way: 9251b80

But then DivOverlay and Popup would be "marked" as interactive too, but the code is missing. popup.on('click',(e)=>console.log(e)) is not working.

var layer = new L.Marker(map.getCenter()).bindPopup('TEST').addTo(map);
layer.getPopup().on('click',(e)=>console.log(e))

https://jsfiddle.net/falkedesign/xqc9mbzd/

But in my eyes it would make sense to add interactive to DivOverlay too.

Perhaps not every descendant of DivOverlay must to be interactive.
But I do not know if LeafDoc has ability to attach Interactive layer class 'in the middle', so..

@mourner @IvanSanchez
Ideas?

Perhaps not every descendant of DivOverlay must to be interactive.

if we add interactive to DivOverlay it would create new possibilities for plugins. Sure it can be added manually but why not make it easier for developers? What is the harm if we add it to DivOverlay? If a descendant should not support interactive it can be manually set to false in the onAdd but I think that is a rare usecase.

@Falke-Design
Something like this?

Good to know: click event will not fire on the Popup

Because of #7750.
May be fixed by #7751.

@johnd0e can you please resolve the conflicts and mark the PR as ready for review. I would say we keep this PR in the 1.8.0 milestone, because it was already approved by @mourner and then it is a small task to check the changes since them and then merge it.