# Ignition 8.1.16, Multi-Monitor Layout Causes Pop-Up Calendar Position Issues **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition81\ **Created:** [May 24, 2026, 2:23pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-16-multi-monitor-layout-causes-pop-up-calendar-position-issues/115680 "2026-05-24T14:23:26Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![brandon7716](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@brandon7716](https://forum.inductiveautomation.com/u/brandon7716)\ **Post date:** [May 24, 2026, 2:23pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-16-multi-monitor-layout-causes-pop-up-calendar-position-issues/115680/1 "2026-05-24T14:23:26Z")
When using the pop-up calendar component in the multi-monitor setup described below, the calendar behaves inconsistently depending on which monitor the client is running on. - On Monitor 1, the pop-up calendar displays correctly. - On Monitor 2, the pop-up calendar opens at the top of Monitor 1 instead of Monitor 2. - On Monitor 3, the pop-up appears significantly offset, displaying much lower than the associated drop-down button. - The issue went away after reconfiguring the monitor layout so that all displays were arranged in a single horizontal row. - ![merged-image-2026-05-24T14-18-48](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aa6e226860c5e596c5a9dc634fda9e5ade57f392.jpeg) All displays are the same resolution and scaling. The components are simply placed in the root container of a main window. Is there any solution for this issue so the pop-up calendar behaves as expected regardless of the overall Windows multi-monitor arrangement? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 24, 2026, 3:21pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-16-multi-monitor-layout-causes-pop-up-calendar-position-issues/115680/2 "2026-05-24T15:21:00Z")
This sounds like a bug that has been fixed, but I don't recall exactly. 8.1.16 is **really** old. You should upgrade and see if the problem persists. (Or spin up a test VM with a new version and try with that.)