-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Non interactive app navigation entry #2612
Comments
Clearly! |
@skjnldsv tried that. Only problem: |
Is it used directly after app-navigation? |
Yeah, i agree with you, let's go with a |
If I remember correctly in the Mail app the account name is not a link. Might be worth a look... |
In the Mail app we did have the account name not being a link, by being a h2. But now even that is a link, opening the specific inbox of that account. :) cc'ing other app devs @ChristophWurst @BernhardPosselt @georgehrke @raghunayyar @raimund-schluessler probably makes sense to move this fix to core, right? |
Would make sense to check the use case and add an additional element if needed (separator?) |
@jancborchardt there is a lot of "common" stuff we should rebuild and move to core, like he popover, or the nav entry for example. |
closed in #3024 |
I stumbled over a problem during the development of nextcloud/notes#28
There is currently no way to introduce entries to the app-navigation which aren't links.
I hotfixed this by duplicating code from core, introducing a new class
.nav-entry
:fix in notes
source in core/apps.css
@nextcloud/designers what do you think? should we move this fix into core?
The text was updated successfully, but these errors were encountered: