Closed (fixed)
Project:
Navigation
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Oct 2023 at 10:24 UTC
Updated:
6 Nov 2023 at 09:09 UTC
Jump to comment: Most recent
Comments
Comment #3
saschaeggiComment #4
ckrinaAs mentioned in Slack we discussed exactly that on the CSS refactor, but on mobile this region is not sticky anymore. That’s why we kept bottom. Happy to change it to something more useful than bottom that still applies regardless of it being sticky :)
Comment #5
ckrinaAs mentioned in Slack we discussed exactly that on the CSS refactor, but on mobile this region is not sticky anymore. That’s why we kept bottom. Happy to change it to something more useful than bottom that still applies regardless of it being sticky :)
Comment #6
finnsky commentedwe have:
1. header.
2. content.
3. bottom. (for me it should be footer)
Comment #7
saschaeggiFooter? Meta?
Comment #8
finnsky commentedYes. Semantically it will be part of NAV
But in BEM we will add
admin-toolbar__header
admin-toolbar__content
admin-toolbar__footer
Simple logic imo
Comment #9
saschaeggi@finnsky that sounds about right 👍
Comment #10
ckrinaGood idea!
Comment #11
kostyashupenkoRebase required
Comment #12
ckrinaRebased and changed the name to footer. Thanks all!