Closed ianthomas23 closed 6 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
This was fixed by #700.
I would like to add
host
andref
HTMLElement
options toMenu.open
.Currently
Menu.open
always adds the menudiv
to the DOM as the last child of thedocument.body
. This has caused a problem inipydatagrid
as although it does give the correct behaviour in JupyterLab, it is not correct for NbClassic, Voila, etc, as their different DOM structure directly under thebody
means the menus have been appearing in the wrong location (full analysis is in this ipydatagrid comment).Menu.open
doesn't give us any control over where the menu is inserted in the DOM, butWidget.attach
(which is what is called byMenu.open
) does via the argumentshost
(the parent element to insert under) andref
(the element to insert before). The proposal here therefore is to expose these two arguments viaMenu.IOptions
inMenu.open
.The workaround in
ipydatagrid
PR bloomberg/ipydatagrid#509 is to let the menu be attached as normal tobody
by callingMenu.open
, then immediately useWidget.detach
andWidget.attach
to move it to the desired location in the DOM. By exposing thehost
andref
inMenu.open
we will be able to changeipydatagrid
to attach it directly to the correct location and avoid having to detach and reattach it.Strictly speaking the
ipydatagrid
use case only needs theref
option and not thehost
one. But I think it best to add all rather than part of the API to control exactly where in the DOM the menu is added.I will submit a PR for this shortly.