Navigation switches from Team folders to All files when opening a subfolder

[lspringfeld]

Steps to reproduce

1. Open the Files app.
2. Open Team folders.
3. Open any team folder.
4. Open any subfolder inside the team folder.

Expected behaviour

The active navigation entry should remain Team folders.

The breadcrumb root (/) should continue to point to the current team folder instead of leaving the Team folders view.

Actual behaviour

As soon as a subfolder is opened:

• the active navigation changes from Team folders to All files
• the breadcrumb root (/) now points to All files
• clicking the breadcrumb leaves the Team folders view

The problem occurs with every team folder.

The issue was reproduced with the original Team folders app, without any custom JavaScript modifications enabled.

Additional observations

Before opening a subfolder, the browser URL is:

/apps/files/groupfolders

After opening a subfolder, the URL changes to:

/apps/files/files/<fileid>?dir=/TeamFolderName

At exactly this moment, the browser console logs:

[DEBUG] files: Route view id files is different from active view id groupfolders, updating active view...

Immediately afterwards, the active navigation switches to All files.

Server configuration

Nextcloud version:
33.0.5

Team folders version:
21.0.9

Browser:
Firefox

[lspringfeld]

Additional analysis

I investigated the issue further and found what appears to be the code path leading to the incorrect navigation state.

When opening a Team Folder, openGroupfolderAction.ts executes:

window.OCP.Files.Router.goToRoute(
	null, // use default route
	{ view: 'files', fileid: nodes[0].id },
	{ dir },
)

After navigating into a Team Folder (or one of its subfolders), the route parameters are:

{
  view: "files",
  fileid: "9693"
}

In FilesNavigation.vue, the active view is derived from the route as follows:

const currentViewId = computed(() => route?.params?.view || 'files')

This causes currentViewId to become "files", which triggers the following watcher:

watchEffect(() => {
	if (currentViewId.value !== activeStore.activeView?.id) {
		const view = allViews.value.find(({ id }) => id === currentViewId.value)!
		if (view) {
			getNavigation().setActive(view.id)
		}
	}
})

As a result, the active navigation entry changes from Team folders to All files, even though the user is still browsing inside a Team Folder. This also causes the breadcrumb root to switch from Team folders to All files.

I'm not yet sure whether the root cause is:

• openGroupfolderAction.ts explicitly navigating with view: 'files', or
• FilesNavigation.vue deriving the active navigation exclusively from route.params.view.

However, this appears to be the complete code path that reproduces the incorrect navigation state.

[lspringfeld]

I created a small client-side JavaScript patch that works around the current UI behavior without modifying Nextcloud or Groupfolders.

The patch currently:

• opens Team folders by default,
• preserves Unified Search,
• keeps the Team folders navigation entry highlighted,
• removes the redundant root breadcrumb,
• and optionally customizes the navigation.

This is not a fix for the underlying issue, but it demonstrates that the desired behavior can be achieved entirely on the client side.

I've published the implementation here in case it is useful as a reference:

https://github.com/lspringfeld/nextcloud-groupfolders-ui-patch

[solracsf]

Is this a duplicate of #3713 ?

[lspringfeld]

Thanks for pointing me to #3713.

Initially, I assumed this was an implementation bug, which is why I investigated the routing and documented the code path that causes the navigation to switch to All files.

After reading the discussion in #3713, I'm no longer sure whether this is considered a bug or an intentional UX decision.

However, I think there is one aspect that wasn't really discussed there:

From a user's perspective, the current behaviour feels inconsistent. The user explicitly enters the Team folders section, but as soon as they open a folder, the active navigation changes to All files and the breadcrumb root changes accordingly, even though they are still browsing the same Team folder.

As shown in the attached screenshot, Team folders is presented as a first-class navigation entry alongside Personal files, Favorites, Shares, etc. Those views preserve their navigation context while browsing, whereas Team folders is the only one that immediately switches to All files after opening a folder.

That inconsistency is what made me assume this was an implementation bug rather than an intentional UX decision.

I'm therefore wondering whether the current behaviour is actually intended, or whether it is simply a consequence of the current routing implementation.