Currently, Studio Landing Page editor doesn't respect content.tree.location_id.

Consider configuration as follow:

    system:
        group_a:
            content:
                tree_root:
                    content_id: 80
        group_b:
            content:
                tree_root:
                    content_id: 85

Current behaviour:
Even if you are currently viewing content, with location path, for instance: /1/2/85/123 (which belongs to group_b siteaccess group (thanks to tree_root setting), then when you switch to Page view, you will see that first siteaccess is active (even if it doesn't belong to the group_b siteaccess).

Expected behaviour:
If you are going to see Landing Page in Page tab, then correct siteaccess should be activated automatically.