GUI bugging out when using saved info #11473

Open
opened 2025-12-29 21:45:42 +01:00 by adam · 7 comments
Owner

Originally created by @alaltuntas on GitHub (Aug 12, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.2

Python Version

3.10

Steps to Reproduce

This issues seems to only be present in Microsoft Edge, I could not replicate the problem when using Google Chrome.

This issue is replicable, by doing the following:

  1. devices > devices > add a new device > then adding a new device
  2. devices > devices > add a new device > click on "Name" > try using the saved info

Expected Behavior

Saved information to be filled in.

Observed Behavior

While trying to add new devices to our NetBox, there seems to be a recurring problem whever the "saved info"/"last used" in Microsoft Edge is clicked.
The GUI bugs out and seems to jumping through all textbox, i.e. if you were to spam "tab".
Only reloading the website stops it from continuously scrolling through text boxes.

Originally created by @alaltuntas on GitHub (Aug 12, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.2 ### Python Version 3.10 ### Steps to Reproduce This issues seems to only be present in Microsoft Edge, I could not replicate the problem when using Google Chrome. This issue is replicable, by doing the following: 1. devices > devices > add a new device > then adding a new device 2. devices > devices > add a new device > click on "Name" > try using the saved info ### Expected Behavior Saved information to be filled in. ### Observed Behavior While trying to add new devices to our NetBox, there seems to be a recurring problem whever the "saved info"/"last used" in Microsoft Edge is clicked. The GUI bugs out and seems to jumping through all textbox, i.e. if you were to spam "tab". Only reloading the website stops it from continuously scrolling through text boxes.
adam added the type: bugstatus: blockednetboxseverity: low labels 2025-12-29 21:45:42 +01:00
Author
Owner

@bctiemann commented on GitHub (Aug 14, 2025):

Does this happen only in Edge, or only in certain versions? Can you get a screen recording of what's going on?

Since this is not apparent in other browsers, and other Edge users have not seen this behavior, we need some more specifics on how to reproduce it.

@bctiemann commented on GitHub (Aug 14, 2025): Does this happen only in Edge, or only in certain versions? Can you get a screen recording of what's going on? Since this is not apparent in other browsers, and other Edge users have not seen this behavior, we need some more specifics on how to reproduce it.
Author
Owner

@De-Backer commented on GitHub (Aug 15, 2025):

I can confirm this behavior as well.
In all honesty, I thought it was only happening on my PC, but now that I read this.

Self-hosted v4.0.9
Microsoft Edge
win 11

@De-Backer commented on GitHub (Aug 15, 2025): I can confirm this behavior as well. In all honesty, I thought it was only happening on my PC, but now that I read this. Self-hosted **v4.0.9** Microsoft Edge win 11
Author
Owner

@alaltuntas commented on GitHub (Aug 16, 2025):

Does this happen only in Edge, or only in certain versions? Can you get a screen recording of what's going on?

Since this is not apparent in other browsers, and other Edge users have not seen this behavior, we need some more specifics on how to reproduce it.

Thank you for replying.
I will be posting more specific information as soon as I can (probably in 1-2days)

@alaltuntas commented on GitHub (Aug 16, 2025): > Does this happen only in Edge, or only in certain versions? Can you get a screen recording of what's going on? > > Since this is not apparent in other browsers, and other Edge users have not seen this behavior, we need some more specifics on how to reproduce it. Thank you for replying. I will be posting more specific information as soon as I can (probably in 1-2days)
Author
Owner

@alaltuntas commented on GitHub (Aug 18, 2025):

Does this happen only in Edge, or only in certain versions? Can you get a screen recording of what's going on?

Since this is not apparent in other browsers, and other Edge users have not seen this behavior, we need some more specifics on how to reproduce it.

I've got some more Information:
-it seems to only be happening if the "Last used" is being chosen (see attached => Number 1 bugs, Number 2 works fine

Image

-choosing any other in the saved info tab seems to be working fine
-Microsoft Edge version is: Version 139.0.3405.86 (Official build)
-the only Browser Extensions are: Bitwarden and Adblock

@alaltuntas commented on GitHub (Aug 18, 2025): > Does this happen only in Edge, or only in certain versions? Can you get a screen recording of what's going on? > > Since this is not apparent in other browsers, and other Edge users have not seen this behavior, we need some more specifics on how to reproduce it. I've got some more Information: -it seems to only be happening if the "Last used" is being chosen (see attached => Number 1 bugs, Number 2 works fine <img width="923" height="214" alt="Image" src="https://github.com/user-attachments/assets/472884f8-878a-4b78-9571-85532bce534d" /> -choosing any other in the saved info tab seems to be working fine -Microsoft Edge version is: Version 139.0.3405.86 (Official build) -the only Browser Extensions are: Bitwarden and Adblock
Author
Owner

@alaltuntas commented on GitHub (Aug 18, 2025):

Here is a Screen-Recording of this issue

https://github.com/user-attachments/assets/7cfa1348-fbb5-444e-b12e-e8cb8a65bdcd

@alaltuntas commented on GitHub (Aug 18, 2025): Here is a Screen-Recording of this issue https://github.com/user-attachments/assets/7cfa1348-fbb5-444e-b12e-e8cb8a65bdcd
Author
Owner

@jeremystretch commented on GitHub (Dec 17, 2025):

I was able to reproduce this on Edge. It appears to be an upstream bug in Tom-Select: orchidjs/tom-select#806.

@jeremystretch commented on GitHub (Dec 17, 2025): I was able to reproduce this on Edge. It appears to be an upstream bug in Tom-Select: orchidjs/tom-select#806.
Author
Owner

@jeremystretch commented on GitHub (Dec 17, 2025):

I'm going to mark this as blocked pending an upstream fix as it doesn't seem like something we can feasibly address locally.

@jeremystretch commented on GitHub (Dec 17, 2025): I'm going to mark this as blocked pending an upstream fix as it doesn't seem like something we can feasibly address locally.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11473