* fix: Apply theme style to embedded diagram (#7903)
When diagrams are created with "adaptive colors" they automatically
change to light-/darkmode depending on the browser preference. This
leads to rendering problems when the settings in the browser differ
from the wiki.js theme setting.
Fixes#7677
* fix: Update color scheme for SVG in diagram class
Refactor SVG color scheme handling in diagram class.
* fix: remove duplicate svg first-child class
Removed unnecessary direction property from first SVG in diagram.
---------
Co-authored-by: Nicolas Giard <github@ngpixel.com>
In case of large DrawIO diagrams, today it is sometimes impossible to display it totally on the screen.
This quick workaround provides a way to enable a scrollbar if the width of the diagram is higher than the browser/screen width.
Hide key-line created by `markdown-it-footnote` template when footnotes are directly preceded by header.
Examples:
```md
# References
[^1]: Shows no key-line because References header has one already
# New Page
Text goes here and whatever else
[^1]: these footnotes have no preceding header and will show a key-line
```
* Header formatting for Details Summary
Cleaning up Headers within Details Summary
* Fix for TOC Anchor location
Fix for TOC Anchor location within Details Summary
* display: none for the keyline seems smarter
* Fixes to accommodate large summaries
Fixed to accommodate larger summaries containing both headers and phrasing text. Still removing keylines for summaries with ONLY a header.
* fix: tabset tabs can't be scrolled
Fix for #2091. The change advised in that issue works brilliantly.
* fix: tabset scrollbar is visible even if unnecessary
* fix: tabset tall headers
Co-authored-by: Nicolas Giard <github@ngpixel.com>
This issue is related to #1006 . The $vuetify.goTo() function expects a UTF-8 ev.target.hash . However, the markdown CRM URIencodes the ev.target.hash (this is great for browser compatibility, not so much for Vuetify)
Adding decodeURIComponent() to ev.target.hash fixes compatibility with Vuetify.
This fixes GitHub issue #1873