[PR #9755] [CLOSED] Fixes #9754 - Fix chrome deadlock when opening some select fields #13515

New Issue

adam · 2025-12-29T23:19:18+01:00

adam commented

2025-12-29 23:19:18 +01:00

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/9755
Author: @kkthxbye-code
Created: 7/17/2022
Status: ❌ Closed

Base: develop ← Head: fix-9754

📝 Commits (1)

664962d Fix chrome deadlock when opening some select fields

📊 Changes

3 files changed (+5 additions, -6 deletions)

View changed files

📝 netbox/project-static/dist/netbox.js (+1 -1)
📝 netbox/project-static/dist/netbox.js.map (+1 -1)
📝 netbox/project-static/src/select/api/apiSelect.ts (+3 -4)

📄 Description

Fixes: #9754

This PR tries to fix an unidentified deadlock in chrome when opening certain slim-select fields. I tested as much as I could, but as I am still not sure what actually causes this, I think another valid (maybe safer) solution would be to revert #9735 and #9696 and reopen #9632 until someone who can untangle the hell of async events being fired when opening a slim-select field - I'll let you decide @jeremystretch .

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/9755 **Author:** [@kkthxbye-code](https://github.com/kkthxbye-code) **Created:** 7/17/2022 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `fix-9754` --- ### 📝 Commits (1) - [`664962d`](https://github.com/netbox-community/netbox/commit/664962dc4d18bf6391b83025f536ff6bd86d51ba) Fix chrome deadlock when opening some select fields ### 📊 Changes **3 files changed** (+5 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `netbox/project-static/dist/netbox.js` (+1 -1) 📝 `netbox/project-static/dist/netbox.js.map` (+1 -1) 📝 `netbox/project-static/src/select/api/apiSelect.ts` (+3 -4) </details> ### 📄 Description ### Fixes: #9754 This PR tries to fix an unidentified deadlock in chrome when opening certain slim-select fields. I tested as much as I could, but as I am still not sure what actually causes this, I think another valid (maybe safer) solution would be to revert #9735 and #9696 and reopen #9632 until someone who can untangle the hell of async events being fired when opening a slim-select field - I'll let you decide @jeremystretch . --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

adam added the pull-request label 2025-12-29 23:19:18 +01:00

adam closed this issue

2025-12-29 23:19:18 +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#13515