starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Clickable area of input fields extends too far left #10051

New Issue
Closed
opened 2025-12-29 21:26:13 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:26:13 +01:00
Owner
Copy Link

Originally created by @Chiniquy on GitHub (Aug 6, 2024).

Originally assigned to: @bctiemann on GitHub.

Deployment Type

NetBox Cloud

NetBox Version

v4.0.8

Python Version

3.10

Steps to Reproduce

(Previous issue #16302 was closed, but I am pretty certain that this is in fact a bug, not an intended feature.)

This seems to be the case for all objects in Netbox, both in the Create New screen and in the Edit screen. I will use an IP address for this example.

Click on "Add new IP address"
Left click to the left of the name of any field (see the red X in the image below)
image

The field will now act as if it was clicked, even though it obviously was not clicked
There seems to be a limit to how far left you can go before this stops occuring.

Expected Behavior

When clicking outside of the field, the field should not act as if it was clicked.
Clicking on the red X in the image should do nothing (and close any open drop-downs).

Observed Behavior

The field acts as if it was clicked, and the drop down opens up.

Originally created by @Chiniquy on GitHub (Aug 6, 2024). Originally assigned to: @bctiemann on GitHub. ### Deployment Type NetBox Cloud ### NetBox Version v4.0.8 ### Python Version 3.10 ### Steps to Reproduce (Previous issue #16302 was closed, but I am pretty certain that this is in fact a bug, not an intended feature.) This seems to be the case for all objects in Netbox, both in the Create New screen and in the Edit screen. I will use an IP address for this example. Click on "Add new IP address" Left click to the left of the name of any field (see the red X in the image below) ![image](https://github.com/user-attachments/assets/c49c4aef-40e7-4932-abcc-157cea6a0143) The field will now act as if it was clicked, even though it obviously was not clicked There seems to be a limit to how far left you can go before this stops occuring. ### Expected Behavior When clicking outside of the field, the field should not act as if it was clicked. Clicking on the red X in the image should do nothing (and close any open drop-downs). ### Observed Behavior The field acts as if it was clicked, and the drop down opens up.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:26:13 +01:00
adam closed this issue 2025-12-29 21:26:13 +01:00
adam commented 2025-12-29 21:26:14 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 9, 2024):

This is a result of being used for the column definition. It should be fairly trivial to wrap the label in a "col-sm-3" div and then have the label just there but I have not tested or anything.

If anyone is interested in taking this up, please feel free to ask for assignment here.

@DanSheps commented on GitHub (Aug 9, 2024): This is a result of <label> being used for the column definition. It should be fairly trivial to wrap the label in a "col-sm-3" div and then have the label just there but I have not tested or anything. If anyone is interested in taking this up, please feel free to ask for assignment here.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label severity: low status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10051
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?