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

Improve display of long-text custom fields #9947

New Issue
Closed
opened 2025-12-29 21:24:46 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:24:46 +01:00
Owner
Copy Link

Originally created by @raphis on GitHub (Jul 5, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.0.6

Python Version

3.12

Steps to Reproduce

  1. Create a type "Text (long)" custom field for Devices
  2. Save a very long text into this field
  3. Access the device in the "read-only" view
  4. The page gets very long and the user needs to scrol

Expected Behavior

Use a defined height for the text (long) type of custom field and add a scrollbar as it's shown in the edit-view of an object.
long-text_view
long-text_edit

Observed Behavior

Page gets very long and user needs to scroll.

Consider this as rather a "room for improvement" than a real bug.

Originally created by @raphis on GitHub (Jul 5, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.0.6 ### Python Version 3.12 ### Steps to Reproduce 1. Create a type "Text (long)" custom field for Devices 2. Save a very long text into this field 3. Access the device in the "read-only" view 4. The page gets very long and the user needs to scrol ### Expected Behavior Use a defined height for the text (long) type of custom field and add a scrollbar as it's shown in the edit-view of an object. <img width="875" alt="long-text_view" src="https://github.com/netbox-community/netbox/assets/7922644/4e0fb923-9571-40a6-837d-e47ab89f62d2"> <img width="601" alt="long-text_edit" src="https://github.com/netbox-community/netbox/assets/7922644/341769fa-44e8-47eb-84a0-230b18b6bd75"> ### Observed Behavior Page gets very long and user needs to scroll. Consider this as rather a "room for improvement" than a real bug.
adam closed this issue 2025-12-29 21:24:47 +01:00
adam commented 2025-12-29 21:24:47 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 8, 2024):

Please use the proper template for opening an enhancement or feature request

@DanSheps commented on GitHub (Jul 8, 2024): Please use the proper template for opening an enhancement or feature request
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#9947
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?