Nice suggestion! In development, I run the AIMMS Model Explorer on one monitor and the browser with WebUI displayed on another. I LOVE the idea of having two browser windows that can display different aspects.

---

In principle we prepared the WebUI for being able to have separate pages opened in multiple tabs.

You exactly addressed the current pain-point: clearly defining how the opening of pages/dialogs/side-panels programmatically should behave.



We deliberately left those considerations out of those stories, as opening WebUI in multiple tabs needs more thorough testing anyhow.



My idea is that the page/dialog/side-panel should open in the active tab of the active browser window, but I'm not even sure how easy that can be determined, if at all.

---

---

Hello @sandervlot and @MathFour,

I wanted to inform you that we are well aware of this idea, and it has already been added to our backlog. However, due to our current focus on higher-priority tasks in line with our WebUI roadmap, it may take some time before we can implement it.  

 

My story on the backlog goes like:  

As an App Developer who wants to leverage the WebUI supporting access across multiple tabs/windows, I need the ability to control the execution of functions like OpenPage(), OpenSidepanel() and related actions to a specific WebUI tab. This ensures that actions such as OpenPage(), OpenSidepanel(), etc., are carried out on a designated tab, for example the current active tab rather than affecting all open WebUI pages.  

Although WebUI State Support feature allows us to track the active tab when using multiple Tabs and Windows, functions like OpenPage() currently apply changes to all open tabs and windows. App developers would like these changes to be limited to the current active tab or be able to specify the WebUI tab on which these changes should be applied.

 

Can you please answer this question of mine?
I understand the desire to have the execution of OpenPage() and OpenSidepanel() functions to operate exclusively on a specific tab. However, regarding OpenDialogPage(), when this function is called, should users be prevented from interacting with other WebUI tabs?. Should the dialog continue to appear on all the WebUI tabs as it does currently, or should the dialog appear solely on the chosen tab, with a backdrop or veil covering all tabs?

 

Thanks,

Madhu Krishnappa

AIMMS WebUI Product Owner

---

Hi Madhu, thanks for the update. Regarding your question: I think the desired behaviour would depend a bit on the context.

• If a general dialog is raised and users must take action (e.g. they must refresh a dataset before they can continue), the dialog should (at least) appear on the main open page and a veil should cover the other tabs to prevent interaction.
• If a context specific dialog page is opened (for example showing detailed info of a Gantt Chart job), the other tabs shouldn't be blocked.  

Hope this gives some context of potential use. 

---

Thank you for your response, @sandervlot.  Your input has been valuable in helping me refine and enhance the user story for inclusion in my backlog.

---