This seems full of usability issues, as well as possibly performance issues loading interim unnecessary pages (e.g., user moves mouse across tabs to access one several over). To start, if there's user interaction within the tabs, even as simple as selecting a filtered option, are these changes preserved when tabs are swapped? Is there some reason swapping tabs would cause data loss? Is the hitbox going to overlap with reasonable movements within individual tabs?
Using this heuristics list from NN: https://www.nngroup.com/articles/ten-usability-heuristics/
I'd say this violates #4 at the moment: consistency and standards
Follow established industry conventions (external consistency).
As well as possibly #1, Visibility of System Status, since it changes the state of the whole page without a typical 'interaction'. Hover interactions are expected to possible show more information, not change your context.
Sites and apps should clearly communicate to users what the system’s state is — no action
with consequences to users should be taken without informing them.
And is also likely to be problematic for accessibility unless this is something you can navigate with your keyboard, and depending on the size of the hitbox for the hover, plus many people hover over things they are reading.
Changing the whole page view on hover is definitely not the current convention, though I agree with Danielillo that this could derived from megamenu interactions.
I also think it's a problem for #2, user control and freedom. Because this is a non-standard interaction, users may not understand why the page is changing. They may think they accidentally clicked, and may rapidly swap pages without intending to.
Part of a great user experience is nurturing users’ feeling of control over the user interface (UI) they happen to be using.
Similarly, as discussed in this this mega-menu article, there's the challenge of "what constitutes a hover with intent to interact", also covered more generally in Timing Guidelines for Exposing Content
If mega menus are displayed on hover, one challenge is to distinguish between two
different user intentions:
- The user is just moving the mouse towards a target on the screen, and
the mouse trajectory intersects the link corresponding to the mega
- The user actually looks at the navigation categories and needs
more information about them. The second situation should trigger the
mega menu, but the first should not.
If the hidden content displaces or covers other elements on the page, designers need to be extra careful and require a longer mouse stop over the triggering element before exposing the hidden content. In other words, the more disruptive the content displayed, the more certain designers need to be of user’s intent before triggering the animation.
So, how long must a user hover over a tab before you alter the whole page? Since the current standard for changing pages/views is clicking, users would likely just click if the waiting period is half a second or longer, but if it's less than that, they are likely to accidentally trigger while moving the mouse across the screen. Essentially, you'd be choosing between losing whatever benefit you hope to gain from making this a hover interaction instead of a click, or making it likely to happen accidentally. Furthermore, if click is not a back-up option, it will cause the opposite: fast moving users will be frustrated.
I'd say that unless there's some reason why rapid, no-click movement between tabs is a major efficiency gain, this does more harm than good. I'm not sure how, though, since the user still has to move the mouse to the item, which is usually the more inefficient step in a move-click combo.