-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
Freeze with TASK and inline footnotes #2521
Comments
Closing as there seem to be something else causing DataView to freeze, not the markers |
Nailed it down to an inline footnote instead (as, turns out, in my vault, the exact files that had custom tasks also had inline footnotes, what are the odds?) |
As a side note/bug: having a regular footnote on a task item causes its label to be rendered as plain text in the |
So exactly what is the current bug situation as you see it? What triggers it, and what do you expect to happen, which doesn't happen? I'm a little confused at all the back and forth... |
Hi! I apologise about the excessive messages, as i initially misdiagnosed the issue, closed it, and then reopened when i had a more concrete example. So, i ran a few more tests, and there seem to be some conflict between the DataView and Fancy a Story theme, specifically when it comes to showing inline footnotes on tasks with the However, there are a few bug/issues in the way DataView displays the footnotes that might be the cause:
You can reproduce it by installing the aforementioned FaS theme and DV plugin in a sandbox vault and adding the following to the note: - [ ] foo^[bar]
```dataview
TASK
``` |
What happened?
When a task that has an inline footnote
^[this kind]
is present in the search path (excluding them inFROM
bypasses the issue) of theTASK
query - it causes the entirety of Obsidian to freeze up when the note with the query is loaded in Reading mode.Easy reproducible example would be to create a test note with following content:
DQL
JS
Dataview Version
0.5.67
Obsidian Version
1.8.4
OS
Linux
The text was updated successfully, but these errors were encountered: