Clicking to the left of a field acts as if the field was clicked #9749

Closed
opened 2025-12-29 21:22:02 +01:00 by adam · 3 comments
Owner

Originally created by @Chiniquy on GitHub (May 27, 2024).

NetBox Version

v4.0.3

Python Version

3.10

Steps to Reproduce

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.

  1. Click on "Add new IP address"
  2. Left click to the left of the name of any field (see the red X in the image)
    image
  3. The field will now act as if it was clicked, even though it 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 (May 27, 2024). ### NetBox Version v4.0.3 ### Python Version 3.10 ### Steps to Reproduce 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. 1. Click on "Add new IP address" 2. Left click to the left of the name of any field (see the red X in the image) ![image](https://github.com/netbox-community/netbox/assets/10709382/c18f366a-457a-4eff-989f-d634a6c78d9a) 3. The field will now act as if it was clicked, even though it 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 closed this issue 2025-12-29 21:22:02 +01:00
Author
Owner

@DanSheps commented on GitHub (May 27, 2024):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@DanSheps commented on GitHub (May 27, 2024): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
Author
Owner

@Chiniquy commented on GitHub (May 28, 2024):

Maybe I am missing something, but I cannot see how this could possibly be the intended behavior?

@Chiniquy commented on GitHub (May 28, 2024): Maybe I am missing something, but I cannot see how this could possibly be the intended behavior?
Author
Owner

@Chiniquy commented on GitHub (Jun 3, 2024):

I believe this issue was closed in error. Any chance to get a second set of eyes on it?

@Chiniquy commented on GitHub (Jun 3, 2024): I believe this issue was closed in error. Any chance to get a second set of eyes on it?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9749