AdguardTeam / AdguardTeam/AdGuardHome
Client Settings > Identifier, first box needs delete button when there's more than 1 identifiers
- Lingua principale
- TypeScript
- Stelle
- 36.9k
- Fork
- 2.5k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Prerequisites
- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer
- [x] I have searched other issues and found no duplicates
- [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)
- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)
### Platform (OS and CPU architecture)
Linux, ARM64
### Installation
GitHub releases or script from README
### Setup
On one machine
### AdGuard Home version
0.107.68
### Action
Client Settings > Identifier - first identifier box needs a [X] delete button when there's more than 1 identifiers
1) Add a Client Settings, name it "test"
2) Enter "127.0.0.1" for example, then save to close it
3) Go open "test" Client Settings, then add second identifier 10.0.0.1, then save to close it again
4) Go open "test" Client setting again, 10.0.0.1 moved to first identifier. Now if I want to delete 10.0.0.1 and only keep 127.0.0.1. it cannot be deleted. I have to replace 10.0.0.1 with 127.0.0.1 and then delete the second box.
### Expected result
[X] button should appear for first identifier.
### Actual result
No [X] button appears for the first identifier AND it automatically sorted the identifiers alphabetically. So to delete the first one, it needs to be replaced with content of second identifier and then delete the second identifier.
### Additional information and/or screenshots
_No response_
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.