Description

To maintain retro-compatibility with old maps, as reported here in #10246, with the new TOC there are still a few inconsistent but not blocking behaviors due to how the 'default group' is managed.

Loading a Map in one of the following scenarios:

• Importing a Map
• Opening an existing Map

a logic should intervene to automatically update the TOC internal structure to definitely fix retro-compatibility issues.

What kind of improvement you want to add? (check one with "x", remove the others)

• Minor changes to existing features
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Other useful information

For example, below are some use cases to be fixed within this issue:

1

1. Open this map (export here for testers)
2. The first group (with name "New York") is not draggable but it should be

2

1. Open this map (export here for testers)
2. Add a new layer from related TOC toolbar button ensuring no groups are selected
3. The layer is added inside the first group instead as a first item/leaf in the TOC

3

1. Open this map (export here for testers)
2. Open the one group (e.g. the "Florence" one) and drag a layer outside of any group
3. It is not possible in this old map (where the concept of "default group" is still present at TOC state level) to have layers outside a group

As part of this issue is definitely requested to provide also the necessary clean up for completely removing the concept of "default group" to make also old maps consistent with new TOC behaviors.