Changes between Version 3 and Version 4 of Ticket #36336


Ignore:
Timestamp:
Apr 22, 2025, 12:08:53 PM (5 months ago)
Author:
Natalia Bidart
Comment:

Michał, thank you for the further details. With your instructions, I was able to reproduce. It takes a few attempts, but I managed to do it using Chrome 135.0.7049.84 (official build), incognito session. I agree the issue seems to be that the "autocomplete span" has width: auto; when the bug is visible, and in other cases, when the UI looks as expected, it shows (for example) width: 227.5px;.

I'll accept the ticket since it's an issue, but unclear how we can reliably fix it. Do you have a suggestion? Perhaps we could try upgrading select2 to its latest version and see if this is fixed?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36336

    • Property Triage Stage Unreviewed → Accepted

  • Ticket #36336 – Description

    v3 v4  
    11This error occurs on versions after removing the "collapse.js" and moving to <details> and <summary> tags, mainly Django>=5.1 and in my opinion is purely JS/CSS related and Python independent. This happens using both `StackedInline` and `TabularInline`.
    22
    3 Tested on Google Chrome (135.0.7049.96), Edge (135.0.3179.85), Brave (1.77.100), but with inconsistnt results, seems like the **problems is mainly on desktop**, but also on mobile devides most consistently when using desktop mode with sidebar open (I know how it sounds, but it might be caused by some element width checking).
     3Tested on Google Chrome (135.0.7049.96), Edge (135.0.3179.85), Brave (1.77.100), but with inconsistnt results, seems like the **problems is mainly on desktop**, but also on mobile devices most consistently when using desktop mode with sidebar open (I know how it sounds, but it might be caused by some element width checking).
    44Sometimes it happens after refresh (1st gif) and sometimes from the start (2nd gif).
    55
Back to Top