Repository navigation
aio: webpack guide style issue #17912
Description
I'm submitting a ...
[ ] Regression (behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
There's a wrong style behavior on the webpack guide. If you open https://angular.io/guide/webpack you can see that the content of the guide overlaps the toc-container on the right side. So it's hard to read that guide.
Expected behavior
The text content of the webpack guide must not overlap the toc on the right side.
Minimal reproduction of the problem with instructions
Open the webpack guide at https://angular.io/guide/webpack and look at the content and the toc on the right side of the page.
What is the motivation / use case for changing the behavior?
A better readability of the webpack guide.
Please tell us about your environment
Browser:
- Chrome (desktop) version 59
Metadata
Metadata
Assignees
Labels
No labels
Activity
gkalpak commentedon Jul 4, 2017
cc @wardbell, @Foxandxss
Shouldn't
guide/webpackbe in a SideNav submenu? 😕Foxandxss commentedon Jul 4, 2017
Yes, definitely.
aravindfz commentedon Jul 18, 2017
This is because of this PR which removed the max-height property on the md-side-bar @gkalpak you are fixing it or shall I raise a PR reverting back
gkalpak commentedon Jul 18, 2017
@aravindfz, the issue is not related to that PR. As pointed above, the root of the problem is #17912 (comment) (which means that the guide should be included somewhere in here).
fix(aio): fix layout of the webpack guide
fix(aio): fix layout of the webpack guide (#18493)
fix(aio): fix layout of the webpack guide (#18493)
fix(aio): fix layout of the webpack guide (angular#18493)
fix(aio): fix layout of the webpack guide (angular#18493)
fix(aio): fix layout of the webpack guide (angular#18493)
angular-automatic-lock-bot commentedon Sep 12, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.