You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
On my FAQ page I have a set of Q&A like this:
::: details 100. Some question blah blah blah? {#q100}
Some answer blah blah blah.
:::
On some other page I'd like to link to FAQ 100 and have it automatically open for the user to read. On a FAQ page, it can be hard to track which Q&A item you're jumping to even after the page has scrolled to it, so automatically opening the relevant details block improves the user experience here.
Describe the solution you'd like
Let's say you go to URL /faq#q100. The details block with {#q100} (id="q100") should automatically have the open attribute applied to it.
Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.
The text was updated successfully, but these errors were encountered:
thdoan
changed the title
[Feature request] Open details block when there's an anchor
[Feature request] Automatically open details block if it matches URL anchor
Oct 6, 2024
Pardon my newbie ignorance -- I realized I can do everything I need to do by adding logic in <script>...</script> in the MD file itself. Feel free to close if this feature request is not planned.
Is your feature request related to a problem? Please describe.
On my FAQ page I have a set of Q&A like this:
On some other page I'd like to link to FAQ 100 and have it automatically open for the user to read. On a FAQ page, it can be hard to track which Q&A item you're jumping to even after the page has scrolled to it, so automatically opening the relevant details block improves the user experience here.
Describe the solution you'd like
Let's say you go to URL
/faq#q100
. The details block with{#q100}
(id="q100"
) should automatically have theopen
attribute applied to it.Describe alternatives you've considered
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: