device-management-toolkit / device-management-toolkit/sample-web-ui

Proxy selector in Profile Details: cannot reliably add/select proxies and shows internal no-proxy key

Open
#3,469 0 comments 0 reactions 1 assignee View on GitHub

@nbmaiti is already working on this.

Since Jul 27, 2026.

bug
Dominant language
TypeScript
Stars
13
Forks
19
Avg merge
1d 1h
Merged PRs (30d)
49

Description

Describe the bug 🪲
After the proxy selector change (feat: add proxy configuration selector), proxy selection behavior in Sample UI regressed in Profile Details.

Two user-facing issues are observed:

  1. Once a proxy is added, proxy selection is not working as expected (should still allow selecting another proxy/config from the selector).
  2. The UI displays the internal no-proxy key/text instead of a user-friendly label (example shown: internal object/key for "no proxy" is rendered).

To Reproduce 🪜

  1. Open Sample UI.
  2. Go to Profiles and create/edit a profile.
  3. Navigate to the proxy configuration section.
  4. Add a proxy configuration.
  5. Try to select another proxy from the selector.
  6. Observe selector behavior and rendered proxy text entries.

Expected behavior

  • Proxy selector remains usable after adding a proxy.
  • Valid proxy entries are selectable in a clear way.
  • No internal keys/object names are shown to users.
  • "No proxy" state (if applicable) is shown as a localized/user-friendly label.

Actual behavior

  • After adding a proxy, selection behavior is incorrect / not intuitive for further proxy selection.
  • Wrong entry text is displayed: internal no-proxy object/key appears in UI instead of a proper label.

Screenshots 🖼️
Issue 1 (selector behavior):
Proxy selector issue

Issue 2 (wrong no-proxy/internal text rendering):
Wrong no-proxy entry


Browser Information (please complete the following information): 🖥️

  • OS: Linux
  • Browser and Version: [please fill]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.