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

Text colour in rack elevations not dependent on background #2352

New Issue
Closed
opened 2025-12-29 17:25:09 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:25:09 +01:00
Owner
Copy Link

Originally created by @ktims on GitHub (Feb 6, 2019).

Environment

  • Python version: 3.6.3
  • NetBox version: 2.5.5

Steps to Reproduce

  1. Create a Device Role with a light colour (e.g. White or Yellow)
  2. Create a device of this Role and rack it
  3. View the rack elevation

Expected Behavior

Text labels on devices in the rack elevation are legible; ie. their colour (black/white) depends on the device role colour.

Observed Behavior

In the Device Role list, black text is appropriately used on the light background, while white text is inappropriately used in the rack elevation. The same appropriate text colour selected in the Device Roles view should be used in rack elevations. On white Device Roles the text is totally illegible unless hovered, while on other colours it is merely somewhat illegible.

Originally created by @ktims on GitHub (Feb 6, 2019). ### Environment * Python version: 3.6.3 * NetBox version: 2.5.5 ### Steps to Reproduce 1. Create a Device Role with a light colour (e.g. White or Yellow) 2. Create a device of this Role and rack it 3. View the rack elevation ### Expected Behavior Text labels on devices in the rack elevation are legible; ie. their colour (black/white) depends on the device role colour. ### Observed Behavior In the Device Role list, black text is appropriately used on the light background, while white text is inappropriately used in the rack elevation. The same appropriate text colour selected in the Device Roles view should be used in rack elevations. On white Device Roles the text is totally illegible unless hovered, while on other colours it is merely somewhat illegible.
adam closed this issue 2025-12-29 17:25:09 +01:00
adam commented 2025-12-29 17:25:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 8, 2019):

No new work is being done on the current rack elevation rendering logic. Please add this as desired behavior under #2248.

@jeremystretch commented on GitHub (Feb 8, 2019): No new work is being done on the current rack elevation rendering logic. Please add this as desired behavior under #2248.
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#2352
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?