Search lists empty results

[SaschaWillems]

When searching I often get empty result rows like this:

The number of those empty rows varies, but I always seem to get at least empty rows at the top of the search result.

[oddhack]

Seeing the same thing. Searching for 'VK_KHR_shader_fma' in the current docs site (a newly added extension) returns a bunch of empty entries. This is pretty unfortunate since the natural thing for someone to do to learn about a new extension would be to put its name into the searchbox.

[oddhack]

Another example of this (per #139) is that searching for 'VK_NV_copy' returns the empty list which 'VK_NV_cop' does not.

[oddhack]

Another example of this (per #139) is that searching for 'VK_NV_copy' returns the empty list which 'VK_NV_cop' does not.

Adding screenshot for context.

[gpx1000]

The empty rows happen when a result renders with both an empty page title and an empty snippet. In the current search UI, that occurs when the index contains docs with empty title and empty text fields. The renderer still creates an item, but there’s nothing visible to show.

• This is most likely produced by the indexer when:

1. There’s no H1 tag inside article.doc (so documentTitle becomes empty), and
2. After removing h2..h6, the remaining article content is effectively empty, so text becomes "".

• Queries like VK_KHR_shader_fma or VK_NV_copy can match on fields other than title/text (e.g., name), so the highlight routines won’t provide a snippet, and you end up with a blank row if title is empty.

Working on a PR to hopefully fix this.

[oddhack]

The empty rows happen when a result renders with both an empty page title and an empty snippet. In the current search UI, that occurs when the index contains docs with empty title and empty text fields. The renderer still creates an item, but there’s nothing visible to show.

• This is most likely produced by the indexer when:

1. There’s no H1 tag inside article.doc (so documentTitle becomes empty), and
2. After removing h2..h6, the remaining article content is effectively empty, so text becomes "".

All of the HTML files in the spec component have <title> fields and <h1> inside <article class="doc"> so presumably this isn't causing the observed behavior?

• Queries like VK_KHR_shader_fma or VK_NV_copy can match on fields other than title/text (e.g., name), so the highlight routines won’t provide a snippet, and you end up with a blank row if title is empty.

It's unfortunate that many search results fall in the middle of long wordy sections of the spec so that anchors don't place you where you need to be to see it. It might be good to be able to highlight the matching text when clicking through a search result, and make sure it's shown in context, though that's beyond the scope of this specific issue.

[gpx1000]

Please validate the fix at https://gpx1000.github.io/Vulkan-Site/spec/latest/index.html

[gpx1000]

The final fix for VK_NV_Copy involved ensuring the underscore character which was being auto replaced by " " doesn't cause lookup fails. It's two separate bugs. But both are addressed in this PR.