Dropdown buttons render as text until JS has loaded

Created on 14 November 2023, about 1 year ago
Updated 23 May 2024, 6 months ago

Problem/Motivation

With Drupal 10.1.4, when I got to the Taxonomy listing, the buttons render as text for about 2-3 seconds before the javascript is applied. It appears to be slowness with downloading the aggregated JS file.

With aggregation turned off, this issue does not occur. Each javascript file is downloaded or cached without delay.

Steps to reproduce

Under Configuration > Development, turn on Aggregation for Javascript files.

Go to the Taxonomy listing /admin/structure/taxonomy
The dropdown button render as text before converting to buttons.

Proposed resolution

Find the slowness in rendering the aggregated JS file. I have a theory that it's because jquery 3.7 is being aggregated on every page load and not cached.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ› Bug report
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component
JavascriptΒ  β†’

Last updated 3 days ago

Created by

πŸ‡ΊπŸ‡ΈUnited States Mitch McCoy

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Issue created by @Mitch McCoy
  • First commit to issue fork.
  • Status changed to Postponed: needs info 6 months ago
  • πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

    On a drupal install running the Umami demo, I compared the time it took to convert the static buttons into a dropbutton with and without aggregation. The aggregated version was ~20% faster.

    I notice the screenshot in the filed issue has an option for Automatic Entity Labels which is not part of core. That doesn't necessarily mean that Automatic Entity Labels are the cause of the issue, but it does indicate this is occurring on a site running more than just core so it's difficult to know how to reproduce the issue, and that needs to happen before any steps can be made to resolve it.

Production build 0.71.5 2024