Search results with collapsed results inconsistent

Bug graveyard
, ,
#1

Steps to reproduce

  • click on a tag in a note
  • in the resulting list in Search pane collapse the results
  • click on another tag in the same note
  • the new results list does not show all the results

Expected result

A complete list of the new results

Actual result

A partial list.

Workaround

In the new results list, click on the collapse button to decollapse the list. the list will then be complete, and recollapsing it still shows all results.

Environment

  • Operating system: macOS 10.14.6
  • Obsidian version: 0.8.0

Additional information

4 Likes
Search does not reveal all of the found notes
Incomplete tag search results
#2

Thanks for the report.

#3

I could not reproduce.
Are you using the default CSS?
can you post a short gif?

#4

Jul-15-2020 19-35-00

#5

Does this happen with the default css?

#6

I’m getting this too. v0.8.0, with and without css. Obsidian-v080-Obsidian-Main-2020

#7

thanks

#8

Will be fixed in 0.8.1

#9

Hi all. Saw this in the Bug graveyard and mentioned fix in the 0.8.1 release notes. I wanted to report that I’m currently running into this bug in the 0.8.1 Insider Version using the default CSS.

#10

can you post a gif\video?

#11

Yup! Here’s the gif. Same as before, the results are fixed when toggling the collapsed state back and forth.

giphy

#12

Moving back to bugs. We made further chages. let me know if you still have this problem with 0.8.2

1 Like
#13

I’ve been having this issue too in 0.8.1 — looking forward to the fix!

#14

Search does not reveal all of the found notes until you click in the results list. See this video and note two last notes on the results list, which are not available right after the search until you click in the results list.

Edit: At first I was thinking this is related to search by tags, but looks like this happens when searching anything: video.

Environment

  • Operating system: macOS Big Sur
  • Obsidian version: 0.8.0, no CSS
3 Likes
#15

will be fixed in 0.8.2 or 0.8.3

#16

This does seem be fixed in 0.8.2 for me. Thank you!!

#17

Yep, it sure seems to be fixed.