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
I'm developing a system level extension and I'm having an issue where there's a sb-page-wrapper class that has a padding of 230px that shifts my extension to the left as shown in this picture. I'd like to have my extension be able to use the space right next to the black nav bar on the left.
There's also another div with style .cd-layout--extension .cd-layout__content--sb-expanded that has padding-left: 230px as well, which leads me to believe there's a bug where we're accidently applying the padding twice.
To Reproduce
Create a system level extension with some text to see that it does renders with extra padding from the left.
Expected behavior
I would like to have my content rendered next to the side bar with no extra padding so that I can use all of the space provided like this:
Screenshots
Version
Note that I'm developing using make start-local off of master branch.
Checklist:
argocd version
.Describe the bug
I'm developing a system level extension and I'm having an issue where there's a
sb-page-wrapper
class that has a padding of 230px that shifts my extension to the left as shown in this picture. I'd like to have my extension be able to use the space right next to the black nav bar on the left.There's also another div with style
.cd-layout--extension .cd-layout__content--sb-expanded
that haspadding-left: 230px
as well, which leads me to believe there's a bug where we're accidently applying the padding twice.To Reproduce
Create a system level extension with some text to see that it does renders with extra padding from the left.
Expected behavior
I would like to have my content rendered next to the side bar with no extra padding so that I can use all of the space provided like this:
Screenshots
Version
Note that I'm developing using
make start-local
off of master branch.Logs
The text was updated successfully, but these errors were encountered: