You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow individual sidebars to have the option to display header and footer on all screen sizes, depending on which sidebar it is.
The Desired Behavior
Ability to show the sidebar header and footer on desktop as well as mobile, depending on which sidebar it is.
i.e. for the docs inner sidebar, I want to show the header (with the close icon) only on mobile, but I would like to show the footer (with the getting started button) on desktop as well as mobile.
i.e. If I'm using the sidebar viewport with navPlacement="above", I may want the sidebar header to be visible on desktop so I can use it to display important header content (i.e. logos).
Your Use Case
As a designer, I would like more flexibility in when all the sidebar components (header, body, footer) are visible.
Prior Work
Environment
Daffodil version: X.Y.Z
Angular version: X.Y.Z
For Tooling issues:
- Node version: XX
- Platform:
Others:
The text was updated successfully, but these errors were encountered:
💡 Feature request
Feature Name
Allow individual sidebars to have the option to display header and footer on all screen sizes, depending on which sidebar it is.
The Desired Behavior
Ability to show the sidebar header and footer on desktop as well as mobile, depending on which sidebar it is.
i.e. for the docs inner sidebar, I want to show the header (with the close icon) only on mobile, but I would like to show the footer (with the getting started button) on desktop as well as mobile.
i.e. If I'm using the sidebar viewport with
navPlacement="above"
, I may want the sidebar header to be visible on desktop so I can use it to display important header content (i.e. logos).Your Use Case
As a designer, I would like more flexibility in when all the sidebar components (header, body, footer) are visible.
Prior Work
Environment
The text was updated successfully, but these errors were encountered: