Skip to content
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

Anchors inside callouts within documentation markdown #3501

Closed
jasonsturges opened this issue Apr 27, 2019 · 1 comment · Fixed by #3585
Closed

Anchors inside callouts within documentation markdown #3501

jasonsturges opened this issue Apr 27, 2019 · 1 comment · Fixed by #3585
Assignees

Comments

@jasonsturges
Copy link

Changing your indention to 2 spaces would render links correctly inside these alerts:

image

<div class="@ns-callout @ns-intent-danger @ns-icon-error">
    <h4 class="@ns-heading">Centering the component</h4>
    **Do not center this component** using `text-align: center`, as it will cause an infinite loop
    in the browser ([more details](https://github.com/JedWatson/react-select/issues/540)). Instead,
    you should center the component via flexbox or with `position` and `transform: translateX(-50%)`.
</div>

Above, the "more-details" link would interpret correctly if implemented as follows:

image

<div class="@ns-callout @ns-intent-danger @ns-icon-error">
  <h4 class="@ns-heading">Centering the component</h4>

  **Do not center this component** using `text-align: center`, as it will cause an infinite loop
  in the browser ([more details](https://github.com/JedWatson/react-select/issues/540)). Instead,
  you should center the component via flexbox or with `position` and `transform: translateX(-50%)`.
</div>
@adidahiya adidahiya self-assigned this Apr 28, 2019
@adidahiya
Copy link
Contributor

Nice, thanks for the suggestion! Same issue as #3487 but I'll leave this one open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants