Documentation with links to fragment identifer don’t work

Bug, feature request, or proposal:

Bug

What is the expected behavior?

On the page https://material.angular.io/components/input/overview, the links for:

• In some cases that <mat-form-field> may use the placeholder as the label (see the form field label documentation).
• In some cases that <mat-form-field> may use the placeholder as the label (see the form field label documentation).

Should link to:

• https://material.angular.io/components/form-field/overview#floating-label
• https://material.angular.io/components/form-field/overview#floating-label

What is the current behavior?

On the page https://material.angular.io/components/input/overview, the links generated point to (notice input rather than form-field):

• https://material.angular.io/components/input/overview#floating-label
• https://material.angular.io/components/input/overview#error-messages

Specifically, this is the “current page” + “fragment identifier”. In the actual generated html, the contents are:

• <a href="/components/input/overview#floating-label" class="docs-markdown-a">form field label documentation</a>
• <a href="/components/input/overview#error-messages" class="docs-markdown-a">associate error messages</a>

What are the steps to reproduce?

You can only see the issue on https://material.angular.io/components/input/overview. The github page hosted at https://github.com/angular/material2/blob/master/src/lib/input/input.md seems to work correctly.

What is the use-case or motivation for changing an existing behavior?

The link does not exist

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

6.4.7+ according to docuementation

Is there anything else we should know?

This seems like an issue when the markdown code is moved into https://material.angular.io. I believe the markdown detects the link is on the same domain, and somehow messes up the domain-relative link.

[jelbourn]

Right, it looks like it just hasn’t been published yet.

[angular-automatic-lock-bot[bot]]

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.}