Is the popover_controller needed?

[woller]

<a href="#" data-controller="toggle" data-action="mouseover->toggle#show mouseout->toggle#hide" class="text-gray-300 rounded-r-lg group relative min-w-0 flex-1 bg-white py-4 px-4 text-sm font-medium text-center hover:bg-gray-50 hover:cursor-not-allowed focus:z-10 ">
  <i class="fas fa-laptop-house"></i>
  <span>Løsøre</span>
  <span aria-hidden="true" class="bg-transparent absolute inset-x-0 bottom-0 h-0.5"></span>
  <span class="hidden translate-y-16 absolute inset-x-0 bottom-0 max-w-sm mx-auto bg-yellow-200 rounded py-2 px-4 flex flex-row justify-between items-center" data-toggle-target="toggleable">
    <span class="inline-flex flex-shrink-0 items-center justify-center h-8 w-8 rounded-full bg-yellow-500">
      <i class="fas fa-exclamation fa-sm text-white"></i>
    </span>
    <span class="text-gray-900 ml-2 p-1 text-xs text-left flex-shrink">Der kan ikke tilbydes løsøre pga. kundens skadeprocent (123%)</span>
  </span>
</a>

I just implemented the popover above in a project and ended up using the toggle_controller instead of the popover_controller for several reasons.

1. The current implementation of the popover_controller uses style attributes to translate the popover, instead of Tailwind classes. But there are Tailwind classes for this purpose.
2. The hidden class is hard coded in the controller. The toggle_controller also uses the hidden class, but as a default, making it more flexible.
3. The methods in popover_controller are called mouseover and mouseout. This couples them tightly with the same events, even though one could imagine using other events to show and hide the popovers.

When the only thing the popover_controller does different from the toggle_controller can be solved in a better way using Tailwind classes, why keep it? I suggest adding a popover html example to the toggle_controller's documentation instead.