fulltext | Pure-Go full text indexer and search library | Search Engine library

As mentioned in my comment above, if you index each of the three columns separately, a MySQL query must choose one index per table reference. It cannot use all three indexes in the same query, unless you use different table references.

You should create a single fulltext index for all three columns:

It seems that your FileExt column was a bit off, and was adding in the .. So remove the + 1 from it.

This is a design limitation in TypeScript; see microsoft/TypeScript#46707 for details. It's sort of a cascading failure that results in some weird errors.

A generally useful feature was implemented in microsoft/TypeScript#29478 allowing the compiler to use the expected return type of a generic function contextually to propagate a contextual type back to the generic function's arguments. That might not make much sense, but it sort of looks like this:

You can use

Your solution is the correct solution and does indeed improve the accessibility for keyboard users.

If you need some reassurance check the W3 examples for a flyout menu

Much better than tabindex="-1" would just be to add display: none via a CSS class and change the menu item to a (assuming the top level menu item is not a link). Then opening the menu is as simple as toggling the CSS class and avoids any potential errors with managing tabindex.

If the top level item is a link to another page then follow the principles of option 2 and have an additional drop-down icon next to the main link instead (with aria-label="open (menuItemName)" for example).

The final consideration is that once a menu is open that is a "mega menu" style (multiple columns), you should ideally implement arrow key navigation to take you between columns and items.

As for whether pressing Tab should go to the next top level item it is something that I am not sure if there is any guidance on, I personally say yes it should and arrow keys are for navigation within a drop-down, but I would make it a true drop-down with aria-owns on the

If you have the knowledge of how to implement WAI-ARIA correctly then that is the best option, if not then making the Esc key close the mega menu and or pressing "up" when at the top of the list to get back to the top level links is a reasonable compromise.

I do have one other thing you can do straight away (I know sometimes there is not the scope to fix things right now) as a stop-gap "solution".

Add tabindex="1" to the search box so it is the first item that receives focus and make sure you have "skip to content" links so people can bypass the menu.

While this certainly does not solve the issue, it does improve accessibility / UX for keyboard users in the short term while you fix the problem, and although it doesn't follow "logical focus order" it would be a better experience (as a temporary fix).

Something that you can do quickly while you explore a more robust solution to the mega menu with arrow key functionality etc. etc.

I will stress this point one more time, this is a temporary improvement, not a fix!

You're misunderstanding what delete does. All your code does is remove the href attribute from that DOM element in your Mojo::DOM representation. It has nothing to do with HTTP::Tiny.

What you actually want to do is call ->strip on the element, which removes it from the DOM, but keeps its content intact.

Since you are already using Mojo::DOM, you can just as well use Mojo::UserAgent. There is no need to pull in another UA module. You've already got the whole Mojolicious installed anyway.

You can use a HEAD request rather than a GET request to check if a resource is available. There is no need to download the whole thing, the headers are sufficient.

Your code (without the DB part) can be reduced to this.

Params of the router-link should have been params: { country: data.item.name.official }}

Imagine you can use

The problem is that you have an empty line between GET and the query, so there's no query being sent, hence it's equivalent to a match_all query: