HTMX Allow updating sub-parts of forms without re-rendering entire form #9254

New Issue

adam · 2025-12-29T20:47:31+01:00

adam commented

2025-12-29 20:47:31 +01:00

Originally created by @arthanson on GitHub (Feb 15, 2024).

NetBox version

v3.7.2

Feature type

Change to existing functionality

Proposed functionality

Currently we can re-render forms via HTMX when you change a select field to change the fields that are displayed (for example if you add an interface and change the 802.1Q selection).

What happens is the entire form is re-rendered via HTMX (causing a slight flash as the entire form is re-rendered). The proposal would be to allow specifying and updating just a sub-set of the fields, not just the whole form.

Use case

The issue with the current implementation is that on larger forms (like the interface form) There is a UI 'flash' as the entire form is re-rendered. Just updating the subset of fields instead of the whole form should make for a smoother experience.

Discussing with Jeremy this could probably be done by either tying the fields to a fieldset and having HTMX handle rendering of the fieldset, or else using https://htmx.org/attributes/hx-select/ Tying it to a fieldset might also make the implementation of forms more DRY as you could potentially just mark fieldsets as handled via HTMX and the underlying form-view class could auto handle the return info instead of currently how we handle the return in each form-view individually.

Database changes

None

External dependencies

None

Originally created by @arthanson on GitHub (Feb 15, 2024). ### NetBox version v3.7.2 ### Feature type Change to existing functionality ### Proposed functionality Currently we can re-render forms via HTMX when you change a select field to change the fields that are displayed (for example if you add an interface and change the 802.1Q selection). What happens is the entire form is re-rendered via HTMX (causing a slight flash as the entire form is re-rendered). The proposal would be to allow specifying and updating just a sub-set of the fields, not just the whole form. ### Use case The issue with the current implementation is that on larger forms (like the interface form) There is a UI 'flash' as the entire form is re-rendered. Just updating the subset of fields instead of the whole form should make for a smoother experience. Discussing with Jeremy this could probably be done by either tying the fields to a fieldset and having HTMX handle rendering of the fieldset, or else using https://htmx.org/attributes/hx-select/ Tying it to a fieldset might also make the implementation of forms more DRY as you could potentially just mark fieldsets as handled via HTMX and the underlying form-view class could auto handle the return info instead of currently how we handle the return in each form-view individually. ### Database changes None ### External dependencies None

adam added the type: feature netbox status: backlog complexity: high labels 2025-12-29 20:47:31 +01:00

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#9254