Fix search input in list views in the Console

[ryaplots]

Summary

References https://github.com/TheThingsIndustries/lorawan-stack-support/issues/1415

Changes

• Remove disabling

Testing

Steps

Follow the steps in cybereye issue.

Regressions

• Removing the disabling will mean the the field won't be disabled while the fetching for new entries is happening

Notes for Reviewers

There were two ways of fixing this:

1. Make the field not disabled at the risk that the user will change the input while the fetch is still happening
2. Adding more logic to the fetch table which is already huge to track that field and check is it was focused before, refocus it again.

I went for option 1. Let me know what you think

---

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[PavelJankoski]

Agree with the fix. Approved.

[PavelJankoski]

Agree with the fix. Approved.

@ryaplots Actually, another alternative is if instead of disabled we use readonly when fetching. Can you try that before merging? I think the input won't lose focus with that.

[nicholaspcr]

@PavelJankoski My apologies mate, I just saw it being approved and merged it.
Should I create the PR to revert these changes?