Draw Widget - Options Appear Under Map when in Sidebar

[mwartman_grey]

I noticed this on Enterprise version 11.5 of ExB, when a Draw widget is placed inside of a Sidebar, the Options pane appears under the map. It appears that the pattern used for the Options pane is different than the other other tools within the Draw widget. This is demonstrated in the gif below. I've tried to arrange the Sidebar and Draw widgets to "Bring to front", but this does not resolve the issue.  Can you please make the Options pane appear above the map so that it is consistent with the other tools in the draw widget? 

[mwartman_grey]

This also occurs with the selection tools, but not as big of a concern since the area occupied by the selection options is small.

In short, all the tool panes within the Draw Widget should all follow the same design pattern - this would make designing an ExB app much easier if we didn't have to worry about different window pane sizes or arrangement order. 

[Shen_Zhang]

Hi @mwartman_grey, you're seeing this because the symbol selector popover is rendered with a higher display level than the draw widget itself; however, the settings panel and editing tools are on the same level as the draw widget. 

I know it's a little bit confusing, but I'm afraid currently it's a know limit for now. We'll see how to fix this and please try placing the draw widget on the map as a walkaround for now.

[mwartman_grey]

Thanks for replying @Shen_Zhang .

The problem with moving the Draw toolbar outside of a Sidebar is that the Draw Selection tools are always visible. Users think that they can use them to select features on the map; they are not aware that the selection is for drawn items only. This makes for a confusing user experience and I'd constantly need to explain how to use the other selection tool. Alternatively, I can place the draw widget in a widget controller, but then lose control where the toolbar opens (the location is tied to the widget controller placement). In short, I'm struggling to get these alternatives working while maintaining a good user experience. 

Do you have a timeline or target version when you're hoping to fix this issue? I'm sure there are technical reasons that are making this a challenge. Thanks