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

[BUG] Docs table of contents scroll to fragment doesn't work because there are no id attributes on headings in markdown files #2857

Closed
Tracked by #1925
xelaint opened this issue Jun 13, 2024 · 0 comments · Fixed by #2927
Assignees
Labels
bug A confirmed bug report docs This issue is related to documentation
Milestone

Comments

@xelaint
Copy link
Member

xelaint commented Jun 13, 2024

🐛 Bug report

Current Behavior

Docs table of contents scroll to fragment doesn't work because there are no id attributes on headings in markdown files

Expected Behavior

Clicking on a heading item in the table of contents in docs should scroll page to the correct heading. The heading tags in markdown files need to have an id attribute set on them.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


Daffodil version: X.Y.Z
Angular version: X.Y.Z 

 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

@xelaint xelaint added the bug A confirmed bug report label Jun 13, 2024
@xelaint xelaint changed the title [BUG] Docs table of contents scroll to fragment does not work [BUG] Docs table of contents scroll to fragment doesn't work because there are no id attributes on headings in markdown files Jun 13, 2024
@xelaint xelaint mentioned this issue Jun 13, 2024
26 tasks
@xelaint xelaint added this to the Daffodil v1.0 milestone Jul 8, 2024
@xelaint xelaint added the docs This issue is related to documentation label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A confirmed bug report docs This issue is related to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants