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
I think a recent update to CSS (presumably #638) changed how the search results are placed. If you do a search on the User Guide you'll see the search results being rendered directly on top of the page contents.
I'm assuming this issue crept in because I'd looked at #638 locally in the past, but then merged #604 without checking to make sure #638 was still okay.
I'm not a CSS expert, but I believe the issue is because the search results (id=searchresults-outer) is display: block, while the page contents (id=content) is positioned using absolute coordinates. If you close the sidebar, the page gets rendered just fine again.
We're lucky I noticed this before making a big announcement on Reddit. Looking at the crates.io stats, it seems like only 65 people have downloaded v0.1.4 so far, two of which are from me.
The text was updated successfully, but these errors were encountered:
I think a recent update to CSS (presumably #638) changed how the search results are placed. If you do a search on the User Guide you'll see the search results being rendered directly on top of the page contents.
I'm assuming this issue crept in because I'd looked at #638 locally in the past, but then merged #604 without checking to make sure #638 was still okay.
I'm not a CSS expert, but I believe the issue is because the search results (
id=searchresults-outer
) isdisplay: block
, while the page contents (id=content
) is positioned using absolute coordinates. If you close the sidebar, the page gets rendered just fine again.CC: @GuillaumeGomez, @mattico
We're lucky I noticed this before making a big announcement on Reddit. Looking at the crates.io stats, it seems like only 65 people have downloaded
v0.1.4
so far, two of which are from me.The text was updated successfully, but these errors were encountered: