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

Sporadically broken HTML formatting since at least 3.5.0 #8138

New Issue
Closed
opened 2025-12-29 20:32:57 +01:00 by adam · 9 comments
adam commented 2025-12-29 20:32:57 +01:00
Owner
Copy Link

Originally created by @stavr666 on GitHub (May 30, 2023).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v3.5.1

Python version

3.10

Steps to Reproduce

Spontaneously observed behavior:

  1. Open any list
  2. Click to any object
  3. Press "Go back" (or ALT+←) in browser

Expected Behavior

List will be rendered as usual.

Observed Behavior

Loaded only part of page, without sidebar, with empty head tag:

image

Originally created by @stavr666 on GitHub (May 30, 2023). Originally assigned to: @DanSheps on GitHub. ### NetBox version v3.5.1 ### Python version 3.10 ### Steps to Reproduce Spontaneously observed behavior: 1. Open any list 2. Click to any object 3. Press "Go back" (or ALT+←) in browser ### Expected Behavior List will be rendered as usual. ### Observed Behavior Loaded only part of page, without sidebar, with empty head tag: ![image](https://github.com/netbox-community/netbox/assets/84839985/b18e3bd7-46f4-41b1-bc1d-8c3b72ee72c2)
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:32:57 +01:00
adam closed this issue 2025-12-29 20:32:57 +01:00
adam commented 2025-12-29 20:32:58 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 30, 2023):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.2 (Also not able to reproduce on 3.5.1). Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@DanSheps commented on GitHub (May 30, 2023): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.2 (Also not able to reproduce on 3.5.1). Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 20:32:58 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 30, 2023):

I have seen this also from time-to-time recently. I thought it was just some glitch when I was debugging stuff so didn't bother to track it down, but I have seen this several times. On a Mac using chrome browser, not sure if that has anything to do with it.

@arthanson commented on GitHub (May 30, 2023): I have seen this also from time-to-time recently. I thought it was just some glitch when I was debugging stuff so didn't bother to track it down, but I have seen this several times. On a Mac using chrome browser, not sure if that has anything to do with it.
adam commented 2025-12-29 20:32:58 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 30, 2023):

I don't think it's a bug with netbox. Just how browsers load the css and js. When you click back, if the styling is not loaded this happens and I have seen it on other sites too.

@abhi1693 commented on GitHub (May 30, 2023): I don't think it's a bug with netbox. Just how browsers load the css and js. When you click back, if the styling is not loaded this happens and I have seen it on other sites too.
adam commented 2025-12-29 20:32:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 30, 2023):

Yeah, I tried it with Chrome on both my prod and the demo and no joy. It could also be browser specific.

I think I may have seen it before too, and when I encountered it I thought at the time it was just a glitch with the HTMX request.

@DanSheps commented on GitHub (May 30, 2023): Yeah, I tried it with Chrome on both my prod and the demo and no joy. It could also be browser specific. I think I may have seen it before too, and when I encountered it I thought at the time it was just a glitch with the HTMX request.
adam commented 2025-12-29 20:32:59 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (May 30, 2023):

Please re-confirm the reported behavior on the current stable release

It's totally reproduceable in 3.5.0, 3.5.1, 3.5.2. I encountered it dozen time my own production installation (3.5.0, 3.5.1) and at least once in every 3 versions on your Demo-site, during my check of some conceptions before generating other reports there.

But I agree with @abhi1693 that it's look like browser-related (3 different Chromium-based), because it never reproduceable on repeat (forward-back buttons).

@stavr666 commented on GitHub (May 30, 2023): > Please re-confirm the reported behavior on the current stable release It's totally reproduceable in 3.5.0, 3.5.1, 3.5.2. I encountered it dozen time my own production installation (3.5.0, 3.5.1) and at least once in every 3 versions on your Demo-site, during my check of some conceptions before generating other reports there. But I agree with @abhi1693 that it's look like browser-related (3 different Chromium-based), because it never reproduceable on repeat (forward-back buttons).
adam commented 2025-12-29 20:32:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 31, 2023):

Honestly, the lack of HTML in the screenshot makes me think it is the browser replaying a HTMX request, which results in only a partial HTML being sent and it glitching. (You only get the table, not anything else like the nav menu)

If we had a consistent way to reproduce this, we could maybe track it down better.

@DanSheps commented on GitHub (May 31, 2023): Honestly, the lack of HTML in the screenshot makes me think it is the browser replaying a HTMX request, which results in only a partial HTML being sent and it glitching. (You only get the table, not anything else like the nav menu) If we had a consistent way to reproduce this, we could maybe track it down better.
adam commented 2025-12-29 20:32:59 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jun 4, 2023):

Probably similar to this:

https://github.com/bigskysoftware/htmx/issues/1201

I can reliably recreate it by going to the device list, order the table by a column, closing the tab and then hitting ctrl+shift+t in chrome (re-open closed tab). This only renders the table, without css.

Anyway, there's some context if anyone wants to look into it. There's some suggestions in the linked issue.

@kkthxbye-code commented on GitHub (Jun 4, 2023): Probably similar to this: https://github.com/bigskysoftware/htmx/issues/1201 I can reliably recreate it by going to the device list, order the table by a column, closing the tab and then hitting ctrl+shift+t in chrome (re-open closed tab). This only renders the table, without css. Anyway, there's some context if anyone wants to look into it. There's some suggestions in the linked issue.
adam commented 2025-12-29 20:32:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jun 5, 2023):

Looks like we might just need to use the cache-busting params.

@DanSheps commented on GitHub (Jun 5, 2023): Looks like we might just need to use the cache-busting params.
adam commented 2025-12-29 20:33:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 23, 2023):

This seems like it can be addressed by setting the Vary: HX-Request response header as described here.

@jeremystretch commented on GitHub (Jun 23, 2023): This seems like it can be addressed by setting the `Vary: HX-Request` response header as described [here](https://htmx.org/docs/#caching).
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 severity: low status: accepted type: bug
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#8138
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?