Bug: Context menu - sub menu gets out of container

Bug: Context menu - sub menu gets out of container

Posted by: eyal.ofri on 19 December 2021, 6:54 am EST

• 

  eyal.ofri

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 19 December 2021, 6:54 am EST - Updated 3 October 2022, 9:23 am EST

  Hello,

  I use spreadJS inside a container that has “overflow: hidden” and when right clicking on a cell that is at the edge of the spread container I get the following behavior:

  1. The context menu itself doesn’t go out of the container as expected.
  2. When opening a sub menu inside the context menu it gets out of the container and cuts off (because of the “overflow: hidden” I have on the container).

  Is there something I can currently do in order to limit the context menu’s sub menu to stay inside the container?

  Pay attention that when the spreadsheet container is placed on the edge of the it does work and the sub menu gets open on the other side so it won’t overflow the . I want the same thing, but with the container itself.

  Attached an example of the problem using one of your demos. I just added “overflow: hidden” to the container and that’s the result:
  
  

  

  1139×768 69.1 KB

• 

  avinash.pathak

  • Post Options:
  • Link
    Copy

  Posted 22 December 2021, 5:45 am EST

  Hi,

  We are able to replicate the issue at our end hence we have escalated this issue to the concerned team. We will update you regarding this as we get any information from the team. The internal ID for this issue will be SJS-11330.

  Regards
  
  Avinash

• 

  avinash.pathak

  • Post Options:
  • Link
    Copy

  Posted 23 December 2021, 1:36 am EST

  Hi,

  The devs informed us that this is by design. We are sorry for the inconvenience.

  Regards
  
  Avinash

• 

  eyal.ofri

  • Post Options:
  • Link
    Copy

  Posted 23 December 2021, 5:15 am EST - Updated 3 October 2022, 9:17 am EST

  This is obviously a problem. But a solvable one.
  
  I suggest that you will allow to specify a container id, and use this container as the limit instead of the “window” that is hard coded right now.
  
  It can be optional so it will not change any previous behavior but will help us with working with your component a lot.

  Any other workaround for the meantime will be welcome as well.

• 

  avinash.pathak

  • Post Options:
  • Link
    Copy

  Posted 22 March 2022, 6:35 am EST

  Hi,

  The issue has been fixed in our latest build v15.0.4. Please update to the latest build and let me know if you still face any issues.

  Regards,
  
  Avinash