Skip to content

Release: develop -> main - #144

Merged
TaprootFreak merged 1 commit into
mainfrom
develop
Aug 26, 2026
Merged

Release: develop -> main#144
TaprootFreak merged 1 commit into
mainfrom
develop

Conversation

@github-actions

Copy link
Copy Markdown

Automatic Release PR

This PR was automatically created after changes were pushed to develop.

Commits: 1 new commit(s)

Checklist

  • Review all changes
  • Verify CI passes
  • Approve and merge when ready for production

#143)

* Restore FAQ hash scrolling dropped by the .html path rewrite

VuePress maps /de/faq to /de/faq.html and strips the fragment, so
deep links never leave the top of the page. Keep the original hash
and scroll to it after the router is ready. Give the Trade Republic
heading a stable id.

* Use an HTML id for the Trade Republic FAQ heading

VuePress 1.5 ships markdown-it-anchor 5, which does not parse
{#custom-id}. A raw anchor keeps a stable #trade-republic without
rendering the braces in the heading.

* Put the FAQ hash back in the URL and retry after client navigation

After the .html rewrite, restore the fragment with replaceState so
reload and copy-paste still work. Scroll again on afterEach for
in-app FAQ links, skip a broken percent-encoding, and aim at the
next sibling when the empty id anchor has no box.

* Restore the hash only after the target exists

replaceState after a successful lookup so a dropped fragment is not
written onto the next page. Chain the retries and name the navbar
offset. In-app header-anchor clicks stay on VuePress.

* Note that the faq.html rewrite applies in every locale

* Scroll after Vue Router's initial reset and keep history.state

Always queue a 0ms retry so handleScroll cannot leave the page at
y=0. Keep history.state in replaceState. Ignore the stored hash if
the path has already changed.

---------

Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
@TaprootFreak
TaprootFreak merged commit 51e4c47 into main Aug 26, 2026
2 checks passed
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 this pull request may close these issues.

2 participants