Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better treatment for namespace roots #5012

Closed
rcubetrac opened this issue Oct 26, 2010 · 1 comment · Fixed by #6789
Closed

Better treatment for namespace roots #5012

rcubetrac opened this issue Oct 26, 2010 · 1 comment · Fixed by #6789

Comments

@rcubetrac
Copy link

Reported by brandond on 26 Oct 2010 09:09 UTC as Trac ticket #1487084

Namespace roots are currently displayed as just a regular unselectable top-level folder, and they and their children are just sorted in with the normal list of folders.

It would be nice if there was some indication (a special icon perhaps) of the special status of the root folder, and if it was sorted specially in the folder list. I'm not sure if it belongs at the top, or bottom, or what, though.

Migrated-From: http://trac.roundcube.net/ticket/1487084

@rcubetrac rcubetrac added this to the later milestone Mar 20, 2016
@alecpl alecpl removed the P8 label Apr 7, 2016
alecpl added a commit to alecpl/roundcubemail that referenced this issue Jun 5, 2019
- Display a special icon for other users and shared namespace roots (Elastic)
- Change folders sorting so shared/other users namespaces are listed last

Fixes roundcube#5012.
@alecpl
Copy link
Member

alecpl commented Jun 5, 2019

PR created. Ready for testing. For now different icons are only applied in the Elastic skin.

@alecpl alecpl modified the milestones: later, 1.5-beta Jun 5, 2019
alecpl added a commit that referenced this issue Jan 5, 2020
- Display a special icon for other users and shared namespace roots (Elastic)
- Change folders sorting so shared/other users namespaces are listed last

Fixes #5012.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants