Scope and purpose

Fixes #3301.

The bug described in #3301 has been reported multiple times by users, and while fixing it I discovered that the tooltips were not rendering at all. This was due to a delegate_tooltip plugin which still used Foundation. In addition, the delegate_tooltip plugin fetched data with javascript and rendered the returned content. I changed the data fetching to use an htmx call with a mouseover once hx-trigger, which only runs the first time a tooltip trigger is hovered.

When refactoring to use a nav tooltip, I discovered that the tooltip caused layout shifts inside the navlet. This is because the container is quite small, and has automatic scroll bars. In order to fix it I had to add support for fixed position tooltips. When .nav-tooltip is annotated with data-position="fixed", the tooltip is automatically positioned below the trigger element, but without affecting the flow of the page.

This pull request

• Adds support for fixed position tooltips
• Fixes status widget tooltips on interface alerts
• Fixes tooltips in tree_list.html template in SeedDb tool
• Removes delegate_tooltip plugin

How to test

The tree list changes can be verified on the Seed database: Locations and Seed database: Organizations pages.

Testing the fix in the Status2 widget is a bit more involved. A full description of the bug can be found in #3301, but personally I followed this procedure:

1. Make sure you have a status widget in your dashboard
2. Choose a Netbox with interfaces to add an event to, and get the id of an interface.
3. Create a new AlertHistory entry, with the following values:

   AlertHistory(
       netbox_id=<netbox id>, 
       subid=<interface id>,
       event_type_id='linkState',
       alert_type_id=27,
       source_id='ipdevpoll',
       start_time=datetime.datetime.now(),
       end_time=datetime.datetime.max,
       value=1
   )

   • eventtypeid='linkState' is required for the interface tooltip to render, and alerttypeid=27 refers to the linkDown alert.
   • Alternatively, modify a recent existing alert by adding a subid (Interface id) and changing event_type_id and alert_type_id.
4. After saving the new alert, it should be visible in the status widget. If it is not visible, check the filters on the widget.

Screenshots

All before screenshots are from the "5.14.x" branch.

Before	After	Comment
		Interface (linkDown) tooltip in a long list of alerts, rendered on top of the navlet (fixed position).
		Interface (linkdown) tooltip in a short list of alerts, rendered on top of the navlet (fixed position)
		Tooltip in organization tree list.
		Tooltip in location tree list.

Contributor Checklist

Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to NAV can be found in the
Hacker's guide to NAV.

• Added a changelog fragment for towncrier
• Added/amended tests for new/changed code
• Added/changed documentation
• Linted/formatted the code with ruff, easiest by using pre-commit
• Wrote the commit message so that the first line continues the sentence "If applied, this commit will ...", starts with a capital letter, does not end with punctuation and is 50 characters or less long. See https://cbea.ms/git-commit/
• Based this pull request on the correct upstream branch: For a patch/bugfix affecting the latest stable version, it should be based on that version's branch (<major>.<minor>.x). For a new feature or other additions, it should be based on master.
• If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done
• If it's not obvious from a linked issue, described how to interact with NAV in order for a reviewer to observe the effects of this change first-hand (commands, URLs, UI interactions)
• If this results in changes in the UI: Added screenshots of the before and after
• If this adds a new Python source code file: Added the boilerplate header to that file