[ACS-3742] Added styles for new layout design #3137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The button vertical text alignment seems to be broken, the text is not in the middle
|
|
Sidebar items have vertical text alignment problems too, if you pay attention, they are not in the center of the element |
Yasa-Nataliya
force-pushed
the
ACS-3742-Styling-Changes
branch
from
3b1f186 to
4a26ff0
Compare
Text alignment is fixed for buttons |
DenysVuika
reviewed
Apr 25, 2023
projects/aca-shared/src/lib/components/page-layout/page-layout.component.scss
Outdated
Show resolved
Hide resolved
DenysVuika
reviewed
Apr 25, 2023
DenysVuika
approved these changes
Apr 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
https://alfresco.atlassian.net/browse/ACS-3742,
https://alfresco.atlassian.net/browse/ACA-4691