JavaScript-dependent components on the page only become available after all images have finished loading

Open
#1,047 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, tailwindcss
Domain
frontend

Research direction

Reproduce the issue in Chrome 134 with Rails 7.1, Flowbite 2.3.0, and Tailwind CSS 3.4.4 on a page containing many images. Trace when JavaScript-dependent components become available relative to image loading; done means the components are usable before all images finish loading and the behavior has a regression check.

Written by the indexing model from the issue text.

Description

Describe the bug
JavaScript-dependent components on the page only become available after all images have finished loading

Expected behavior
components can be available even before all images are fully loaded.

Desktop (please complete the following information):

  • OS: macOS 15
  • Browser Chrome
  • Version 134

Additional context
ruby on rails: 7.1
flowbite 2.3.0
tailwindcss 3.4.4

When there are a large number of images on the page, the loading time is very long, and during this time, all components become unclickable.

Is there a way to avoid this?

Thank you very much.

Dominant language
HTML
Stars
9.4k
Forks
862
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from themesberg/flowbite

All issues in themesberg/flowbite

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.