Wijmo hosting element issue

Wijmo hosting element issue

Posted by: omarovd on 20 August 2024, 11:58 am EST

• 

  omarovd

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 20 August 2024, 11:58 am EST - Updated 20 August 2024, 12:03 pm EST

  Hi folks!
  
  I’m working on the solution, when end-user can “undock” part of the application in a separate browser window, or re-dock it back again to the main-application window.

  (in a nutshell it works as detecting required part of a DOM elements and re-parenting to another window’s div by appendChild)

  The problems, which I’m facing are coming mainly from @grapecity/wijmo.react components - particularly with the hostElement:
  
  

  

  1084×572 39.7 KB

  I’ve found that developers can assign hostElement for the wijmo components in the vanilla-js version of the components.

  Is it possible to do with wijmo.react components family?
  
  I think that might help to achieve autonomy for the components, if they would be “packed” along with produced layout.

• 

  vivek.pannu

  

  • Post Options:
  • Link
    Copy

  Posted 22 August 2024, 7:22 am EST

  Hi Omarov,

  It would not be possible to assign a hostElement for Wijmo controls used using React Interops, as the hostElement is internally assigned in this case. We are not aware of your project structure, or how you are performing the docking and undocking part in your project. You can try using the pureJs Wijmo control instead of React interops, if that could work with your current project implementation.
  
  We will be able to assist you better, when we can replicate the issue on our end. So, could you please share a small working sample, similar to your actual project, in which the issue can be replicated?

  You can also modify the following sample to replicate the issue and share it with us - https://stackblitz.com/edit/react-tdun4f?file=index.js

  Regards