Support (icon) tabs in top navbar #2434
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!2434
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/top-nav-tabs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Advances AlekSIS/official/AlekSIS-App-Alsijil#189
Screenshots: https://edugit.org/AlekSIS/official/AlekSIS-App-Alsijil/-/merge_requests/235#note_43799
requested review from @ZugBahnHof
assigned to @nik
marked this merge request as draft
mentioned in merge request AlekSIS-App-Alsijil!1880
is this absolute measurement really necessary? I would suggest to try something relative like
6rem(notice that the number is random) Look e.g. here: https://github.com/materializecss/materialize/blob/main/sass/components/_global.scss#L142 Maybe there is also a fitting preexisting scss variable (although I couldn't find any.Please try to find relative measurements or scss variables (look e.g. at https://edugit.org/AlekSIS/official/AlekSIS-Core/-/merge_requests/770/diffs#9c5cc53dd7c47a3ff9897245b2332e0fd71f93e4_771_792)
I thought it would be useful to adapt existing structures as provided by Materialize [1]. Please give me a rationale why not.
[1] https://github.com/materializecss/materialize/blob/main/sass/components/_tabs.scss#L32
As I used official Material design standards which provided the values in pixels, I wouldn't know, how to this in relative units.
Then why don't you just use
@extend? Or am I missing something?Could you provide me a link to your source?
Yes, because these are new numbers.
https://material.io/components/tabs#specs
If I understand your numbers correctly, the tab should have a height of 50px (12px + 14px from a, and 24px from the icon), but it's defined as 48px inside materialize. What do you think about both of them having the same height of 50% of their parent? Then they would be 24px and 24px, but your code only saysI think there would be a better solution to this, but I don't know how. Due to there being no new specification for material tabs, we can do it this way, although I'm not a fan of it.
resolved all threads
I think we should note somewhere, why these numbers exist and the need to change them sometime
added 4 commits
master54f7a90b- Merge branch 'master' into feature/top-nav-tabsCompare with previous version
marked this merge request as ready
@nik Please review and merge.
changed the description
Please add how to extend the navbar in the template usage docs.
added 1 commit
a9817e6a- Add some documentation on the extended navbarCompare with previous version
added 21 commits
masterf91d1922- Merge branch 'master' into feature/top-nav-tabsb61275f6- Merge branch 'master' into feature/top-nav-tabsCompare with previous version
mentioned in commit
05bd93b47d