Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Striped rendering of opposing rack face varies (depends on rack height?) #4232

Closed
candlerb opened this issue Feb 21, 2020 · 0 comments
Closed
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@candlerb
Copy link
Contributor

candlerb commented Feb 21, 2020

Environment

  • Python version: 3.5.2
  • NetBox version: 2.7.7

Steps to Reproduce

This is a very minor one, but I thought I would mention it anyway.

  1. Create a rack of height 6U and one of height 47U
  2. Add some devices on the front which are not full depth
  3. Check the rendering of the rear side (the grey stripes)

I am checking with Chrome 80.0.3987.116 under macOS.

Expected Behavior

Visually consistent rendering

Observed Behavior

With the 6U rack, the stripes are tightly packed:

image

With the 47U rack, the stripes are thick:

image

Both racks have the same styles referenced from the rect element, and both have the same definition of element #occupied used as the fill:

<linearGradient gradientTransform="rotate(45, 0, 0)" gradientUnits="userSpaceOnUse" id="occupied" spreadMethod="repeat" x1="0" x2="0" y1="0%" y2="5%">
  <stop offset="0%" stop-color="#f7f7f7" />
  <stop offset="50%" stop-color="#f7f7f7" />
  <stop offset="50%" stop-color="#d7d7d7" />
  <stop offset="100%" stop-color="#d7d7d7" />
</linearGradient>
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Feb 21, 2020
@jeremystretch jeremystretch self-assigned this Feb 21, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants