starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Prefixes with children, caret doesnt expand list #32

New Issue
Closed
opened 2025-12-29 15:30:03 +01:00 by adam · 6 comments
adam commented 2025-12-29 15:30:03 +01:00
Owner
Copy Link

Originally created by @bellwood on GitHub (Jun 28, 2016).

I have a /20 prefix with 16 child prefixes underneath

When I view my prefix table this /20 shows a caret that should expand to show me my 16 /24's (the screenshots show this is how it should work)

In both the latest Chrome and Safari I am not able to expand the view by clicking the caret

Originally created by @bellwood on GitHub (Jun 28, 2016). I have a /20 prefix with 16 child prefixes underneath When I view my prefix table this /20 shows a caret that should expand to show me my 16 /24's (the screenshots show this is how it should work) In both the latest Chrome and Safari I am not able to expand the view by clicking the caret
adam closed this issue 2025-12-29 15:30:03 +01:00
adam commented 2025-12-29 15:30:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 28, 2016):

This is expected behavior. The carat merely signifies that the prefix contains one or more children. Although it's reasonable to expect the carat to expand the parent. We don't have any jQuery in place for that currently, but I'll mark this as an enhancement.

@jeremystretch commented on GitHub (Jun 28, 2016): This is expected behavior. The carat merely signifies that the prefix contains one or more children. Although it's reasonable to expect the carat to expand the parent. We don't have any jQuery in place for that currently, but I'll mark this as an enhancement.
adam commented 2025-12-29 15:30:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 1, 2017):

Seems that by now most people are used to the way the prefix list works. I'd still like to enable responsive expansion of the hierarchy, but it'll have to come as part of a future API-driven UI (perhaps in v3.0).

@jeremystretch commented on GitHub (Mar 1, 2017): Seems that by now most people are used to the way the prefix list works. I'd still like to enable responsive expansion of the hierarchy, but it'll have to come as part of a future API-driven UI (perhaps in v3.0).
adam commented 2025-12-29 15:30:06 +01:00
Author
Owner
Copy Link

@traveler3468 commented on GitHub (Oct 19, 2017):

adding my +1 here. I think the carat should expand the child prefixes. Makes it alot more user friendly to be able to just find them in the list rather then loading different pages.

@traveler3468 commented on GitHub (Oct 19, 2017): adding my +1 here. I think the carat should expand the child prefixes. Makes it alot more user friendly to be able to just find them in the list rather then loading different pages.
adam commented 2025-12-29 15:30:07 +01:00
Author
Owner
Copy Link

@bdlamprecht commented on GitHub (Dec 21, 2017):

Added a +1 also as I agree with both bellwood and traveler3468, but I'm okay waiting for until v3.0 time frame for this to happen.

@bdlamprecht commented on GitHub (Dec 21, 2017): Added a +1 also as I agree with both `bellwood` and `traveler3468`, but I'm okay waiting for until v3.0 time frame for this to happen.
adam commented 2025-12-29 15:30:08 +01:00
Author
Owner
Copy Link

@nickzxcv commented on GitHub (Mar 26, 2018):

I think this would be super nice also :)

@nickzxcv commented on GitHub (Mar 26, 2018): I think this would be super nice also :)
adam commented 2025-12-29 15:30:08 +01:00
Author
Owner
Copy Link

@snowie-swe commented on GitHub (Nov 11, 2018):

Would love to see this feature.
Having a /16 with multiple /24 that is then divided up in /30s.
Current way of expanding all is not usable in our case.

@snowie-swe commented on GitHub (Nov 11, 2018): Would love to see this feature. Having a /16 with multiple /24 that is then divided up in /30s. Current way of expanding all is not usable in our case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#32
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?