Select to view content in your preferred language

Unable to Open Widget in Full Screen Mode When Widget Panel Arrangement is set to Fixed

332
1
Jump to solution
10-10-2024 07:45 AM
Labels (1)
NicoKroes
Occasional Contributor

In ArcGIS Experience Builder Developer Edition (v.1.15), I am unable to open a widget in a widget controller when I attempt to open the widget in Full Screen Mode. I have the widget panel arrangement in the widget controller set to 'Fixed'. When I have the widget panel arrangement in the widget controller set to 'Floating', I am able to open the widget in full screen mode.

Reproduction steps.

1. I create a widget controller and add a widget in there and set the 'Widget Panel Arrangement' to 'Fixed'

Widget Panel Fixed.PNG

2. I click the full screen button and attempt to open the widget in full screen and a panel does not appear, when it is expected to appear at a fixed position on the top right. 

Widget Panel Fixed 2.PNG

Any help on this would be greatly appreciated. Thank you!

0 Kudos
1 Solution

Accepted Solutions
Marshal
Frequent Contributor

I have noticed a similar behavior when using the Map widget's full screen tool.  The widget would not open in full screen mode unless it is opened at least once before activating full screen.

My solution was to remove the Map widget full screen button entirely, and prompt users to use browser full screen shortcut instead (F11 in Chrome, Firefox and Edge).  The browser full screen mode worked as expected.

Not entirely sure this is the same issue, but it sounds very similar.

View solution in original post

0 Kudos
1 Reply
Marshal
Frequent Contributor

I have noticed a similar behavior when using the Map widget's full screen tool.  The widget would not open in full screen mode unless it is opened at least once before activating full screen.

My solution was to remove the Map widget full screen button entirely, and prompt users to use browser full screen shortcut instead (F11 in Chrome, Firefox and Edge).  The browser full screen mode worked as expected.

Not entirely sure this is the same issue, but it sounds very similar.

0 Kudos