fix: fix ocx-content-container spacing #279
Conversation
|
This PR fixes a layout/spacing issue that @HenryT-CG detected in tenant-ui. I replaced the currently specified vertical padding with a top margin matching the margin used on other OneCX screens. This will work fine in our specific use cases. However, it will of course also add the top margin if we decide to use the content-container in other places and use cases in the future, which could create layout issues and force us to overwrite the top margin using CSS classes. From my understanding, content-container was supposed to be a general purpose component, so I'm not sure if this is what we want. What do you guys think @HenryT-CG @SchettlerKoehler ? |
|
Implemented new spacing concept and moved margin into page header. Should be ready to be merged now @SchettlerKoehler @HenryT-CG |
## [4.35.0](v4.34.0...v4.35.0) (2024-06-27) ### Features * fix styling issues for page header detail values + add ability to specify icon styles ([#294](#294)) ([08d79c3](08d79c3)) ### Bug Fixes * fix csv exports by escaping delimiters ([#287](#287)) ([76eb1dc](76eb1dc)) * fix ocx-content-container spacing ([#279](#279)) ([409bc5d](409bc5d))
No description provided.