New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navbar covers text on FAQ page #492
Comments
I'm able to confirm this. 👍 |
Is there a reason why the code is structured in the following manner? |
argo49
added a commit
to argo49/yeoman.github.io
that referenced
this issue
Oct 7, 2015
- Top padding changes jump viewport position to top of padding while negative top margin offesets the padding - http://nicolasgallagher.com/jump-links-and-viewport-positioning/demo/#method-C Found a better way to keep markdown and offset nav - Fixes Issue yeoman#492 - Headers are relatively positioned so the anchor tags offset the viewport by enough to clear the nav - Because the name attribute is meant for form submission, it's not a common attribute for anchor tags Removed extra anchor closing tag
eddiemonge
pushed a commit
that referenced
this issue
Dec 11, 2015
- Top padding changes jump viewport position to top of padding while negative top margin offesets the padding - http://nicolasgallagher.com/jump-links-and-viewport-positioning/demo/#method-C Found a better way to keep markdown and offset nav - Fixes Issue #492 - Headers are relatively positioned so the anchor tags offset the viewport by enough to clear the nav - Because the name attribute is meant for form submission, it's not a common attribute for anchor tags Removed extra anchor closing tag Using name instead of id in an empty anchor tag for viewport positioning https://stackoverflow.com/questions/6695439/how-do-you-create-link-to-a-named-anchor-in-multimarkdown Closes #553
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When jumping to a question on the FAQ, the navbar covers the question text and part of the answer, which means users have to scroll up. This happens on both Firefox and Chromium.
The text was updated successfully, but these errors were encountered: