Mark Alexander

I was using Firefox on a Linux laptop, not a mobile device.

As I mentioned in issue 714, if you pass a limit to the search of the sectionIndex, it limits the total number of section results for all pages, not just...

After some console.log debugging, I see that the problem is related to the hardcoded 5 in these two places in flexsearch.js: ```js const pageResults = window.pageIndex.search(query, 5, { enrich: true,...

Thanks. That increases the limits, but there is still the problem that for most of the pages containing the word being searched, `sectionResults` (the result of `window.sectionIndex.search`) is a zero-length...

There is still something rather strange about searching `sectionIndex`. If I set `maxPageResults` to 50, and `maxSectionResults:` to 3, the number of results for the search of `pageIndex` is 20...

This issue in Flexsearch may be the problem, or at least related: [Search using tags may result in less results than expected #459](https://github.com/nextapps-de/flexsearch/issues/459) As a workaround, I'm using this hack...

For completeness, here is my patch for flexsearch.js. ```diff --- ./assets/js/flexsearch.js 2025-08-31 13:21:21.778612466 -0700 *************** document.addEventListener("DOMContentLoa *** 318,324 **** } resultsElement.classList.remove('hx:hidden'); ! const pageResults = window.pageIndex.search(query, 5, { enrich: true,...

I used your suggestion to make parameters for maxPageResults and maxSectionResults. Are you talking about other parameters besides those two? Here's the relevant section from my hugo.yaml: ```yaml params: search:...