mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2025-10-20 19:52:04 +00:00
a8490e6637
This PR fixes the duplicate HTML ID issue (#8778) that can occur when rendering an issue page. An issue page contains multiple renderings of Markdown elements (the issue description and issue comments). When there is more than one Markdown rendering that uses footnotes we have an ID collision because the footnote ID count starts anew for each rendering. This PR adds a `Metas["scope"]` entry to the `RenderContext` and sets it to "comment-{index}" when rendering Markdown for a comment. `Metas["scope"]` gets used as suffix during ID generation. Fixes #8778. ## Additional Notes - ID collision also happens if there are multiple header elements with the same ID. It does not seem to impact users because there are no links referencing headers. However, to err on the safe side, this PR also adds scope to the header IDs. - `Metas["scope"]` might be useful for other Markdown renderings beside comments, e.g. multiple Markdown renderings are possible on Wiki pages. - We apply `Metas["scope"]` as suffix instead of prefix because there are several places in the code that expect `user-content-` to be the ID's prefix. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [X] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [ ] I did not document these changes and I do not expect someone else to do it. ### Release notes - [ ] I do not want this change to show in the release notes. - [X] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/8880 Reviewed-by: Otto <otto@codeberg.org> Co-authored-by: psii <psii@posteo.de> Co-committed-by: psii <psii@posteo.de> |
||
|---|---|---|
| .. | ||
| actions | ||
| badges | ||
| flags | ||
| setting | ||
| action_aggregator_test.go | ||
| activity.go | ||
| attachment.go | ||
| blame.go | ||
| branch.go | ||
| card.go | ||
| cherry_pick.go | ||
| code_frequency.go | ||
| commit.go | ||
| compare.go | ||
| contributors.go | ||
| download.go | ||
| editor.go | ||
| editor_test.go | ||
| find.go | ||
| githttp.go | ||
| githttp_test.go | ||
| helper.go | ||
| helper_test.go | ||
| issue.go | ||
| issue_content_history.go | ||
| issue_dependency.go | ||
| issue_label.go | ||
| issue_label_test.go | ||
| issue_lock.go | ||
| issue_pin.go | ||
| issue_stopwatch.go | ||
| issue_timetrack.go | ||
| issue_watch.go | ||
| main_test.go | ||
| middlewares.go | ||
| migrate.go | ||
| milestone.go | ||
| packages.go | ||
| patch.go | ||
| projects.go | ||
| projects_test.go | ||
| pull.go | ||
| pull_review.go | ||
| pull_review_test.go | ||
| recent_commits.go | ||
| release.go | ||
| release_test.go | ||
| render.go | ||
| repo.go | ||
| search.go | ||
| topic.go | ||
| treelist.go | ||
| view.go | ||
| view_test.go | ||
| wiki.go | ||
| wiki_test.go | ||