Relative floating window rendered on wrong tab page about neovim HOT 5 CLOSED

Note: if this is supported, it's also necessary to prevent nvim_win_set_config from moving autocmd window into another tabpage.

from neovim.

I think the expectation here is wrong. win is not the target window that will be made floating, but rather the window where the newly opened float's position will be relative to.
Supplying a win from a different tabpage with relative == 'win' should probably be an error.

from neovim.

I never implied that the passed in win is the one to be made floating. What the relative to win implies to me is that the newly created floating window by the api will be rendrred and anchored / relative to the target win. However, the target win is not in the current tab page, so either the correct tabpahe layout has to be modified to correctly reflect and render the floating window or error out.

from neovim.

OK fair I interpreted incorrectly. But yeah the issue is not that the relative float is rendered on the wrong tab page, but rather that the API does not support opening a float on a non-current tabpage, and unexpectedly does not give an error with a relative window from a different tabpage.

from neovim.

Supplying a win from a different tabpage with relative == 'win' should probably be an error.

Imo this should only be an error in the short-term if at all. I think the expectation to be able to open windows in non-current tabpages is reasonable and should be supported if possible. Splits should already support this since #25550, I'll have to check again, but maybe I can look into getting that working for floats as well.

from neovim.