-
Notifications
You must be signed in to change notification settings - Fork 23
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
Kirby page sticky content shouldn't be transparent #2713
Kirby page sticky content shouldn't be transparent #2713
Conversation
…ps://github.com/kirbydesign/designsystem into bug/2685-kirby-page-sticky-content-transparency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
One thing I thought about is that the two implementations are so close to each other conceptually that it could just be one ::before
that fills the whole pinned content with the background color, and has a 1px border bottom, but I am unsure if that is doable in reality.
Also, remember to remove the [Bug] text from the PR title so it looks good on the changelog 👼
@RasmusKjeldgaard We could do that but I wasn't sure why it was made as a background in the first place. I thought this could be to enable the option to use opacity for scroll animations or so :-) By using border we won't be able to use opacity as this would then include the background :-) ? I can make the change if you would like but I think the current implementation would be more flexible going forward :-) |
Exactly the kind of insight I was lacking. 🚢 it! |
Which issue does this PR close?
This PR closes #2685
What is the new behavior?
This PR adds a pseudo element behind the sticky content that expands 16px to the left and right with the same logic as with the divider. This was we can cover the entire area with a background-color without changing the layout.
Does this PR introduce a breaking change?
Are there any additional context?
Most context should be available in the initial issue.
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Reminders
Make sure you have implemented tests following the guidelines in: "The good: Test".Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).Review
When the pull request has been approved it will be merged to
develop
by Team Kirby.