Repository navigation
feat(aio): layout max width and design cleanup - #16301
Conversation
|
The angular.io preview for abea275184e470ef692da2999e7bdfb36d5e011a is available here. |
gkalpak
left a comment
There was a problem hiding this comment.
LGTM if it LGT @sjtrimble 😃
I might prefer the banner the be the same width as the .sidenav-container. Or even not have a banner at all.
But that is a different discussion.
abea275 to
5421d1d
Compare
|
The angular.io preview for 5421d1d9ae391bdccacea606826939bb0ff9f6c6 is available here. |
- Content container now has a max width and made the body background the same offwhite color so the cut-off is not visible - Sidenav will always remain at the left of the page - Added a max width to the api banner of filter search inputs - Left aligned content container so it is flush with sidenav - Changed API filter width to match size of filter results
5421d1d to
b6458d8
Compare
|
@petebacondarwin @gkalpak I implemented both your comments, should be ready for full review now |
|
I am happy with the banner. Still LGTM 😃 |
|
Merging but please take a look at #16337 @sjtrimble |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |

Closes #16098 (comment)
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
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: