-
Notifications
You must be signed in to change notification settings - Fork 189
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
Merge our two "sticky headers" on scroll #1223
Comments
cc @PedroFonsecaDEV, who worked on the current sticky header solution. |
I agree with you that we need to improve this feature. You can assign me to this issue too. |
We need to think about #1193 if we will have both or just one of them. |
(Oct/27)Update after sketches: |
*ScrollTop and ScrollDown becomes: ScrollAction (We had repetead code for up and down, now we have only one component) *BackToTop becomes: BackToTopButton - No more coupling with ScrollTop *Merge our two "sticky headers" on scroll (Seneca-CDOT#1223)
*ScrollTop and ScrollDown becomes: ScrollAction (We had repetead code for up and down, now we have only one component) *BackToTop becomes: BackToTopButton - No more coupling with ScrollTop *Merge our two "sticky headers" on scroll (Seneca-CDOT#1223)
*ScrollTop and ScrollDown becomes: ScrollAction (We had repeated code for up and down, now we have only one component) *BackToTop becomes: BackToTopButton - No more coupling with ScrollTop *Merge our two "sticky headers" on scroll (Seneca-CDOT#1223)
*ScrollTop and ScrollDown becomes: ScrollAction (We had repeated code for up and down, now we have only one component) *BackToTop becomes: BackToTopButton - No more coupling with ScrollTop *Merge our two "sticky headers" on scroll (Seneca-CDOT#1223)
*ScrollTop and ScrollDown becomes: ScrollAction (We had repeated code for up and down, now we have only one component) *BackToTop becomes: BackToTopButton - No more coupling with ScrollTop *Merge our two "sticky headers" on scroll (Seneca-CDOT#1223)
*ScrollTop and ScrollDown becomes: ScrollAction (We had repeated code for up and down, now we have only one component) *BackToTop becomes: BackToTopButton - No more coupling with ScrollTop *Merge our two "sticky headers" on scroll (Seneca-CDOT#1223)
Fixes #1223: Merge our two "sticky headers" on scroll
We landed a fantastic PR the other day to support scrolling and having 2 sticky headers. The only down side of it is that the two headers take up a lot of space at the top.
Today I noticed that GitHub does something similar, but collapses the two down into a single-height header:
I wonder if we should flip our top header into the "mobile" view and show the menu on the right vs. the words/icons:
Then we could slide the post title into the middle, empty section between the logo and search/menu icons. That would let us do both things in the same amount of space.
The text was updated successfully, but these errors were encountered: