Drupal is a registered trademark of Dries Buytaert
Protected Pages 3.0.0 Major update available for module protected_pages (3.0.0). Commerce Core 3.3.8 Minor update available for module commerce (3.3.8). Search API HTML Element Filter 1.0.7 Minor update available for module search_api_html_element_filter (1.0.7). Layout Builder Reorder 2.0.1 Minor update available for module layout_builder_reorder (2.0.1). Ban 1.1.0 Minor update available for module ban (1.1.0). Field Formatter Range 2.0.0 Major update available for module field_formatter_range (2.0.0). Field Formatter Range 8.x-1.8 Minor update available for module field_formatter_range (8.x-1.8). UI Patterns (SDC in Drupal UI) 2.0.18 Minor update available for module ui_patterns (2.0.18). Search API Solr 4.3.11 Module search_api_solr updated after 14 months of inactivity (4.3.11). Provus Mega Menu Module provus_mega_menu crossed 1,000 active installs.

Page Load Progress

619 sites Security covered
View on drupal.org

This module prevents users from interacting with a page while a time-consuming task is being processed, showing a visual indicator to confirm the task is running. This improves user experience and avoids potential task failures by stopping accidental clicks or multiple submissions.

Page Load Progress sets a screen lock showing a throbber when the user submits a form that triggers a time consuming task. It unequivocally indicates a task is being executed, and, as a result, improves the overall user experience. By forbidding users from clicking around while waiting, it also prevents task execution failures, e.g. when working with web services.

Configuration

To configure the behavior of this module go to admin/config/user-interface/page-load-progress.

Caveats

Even though you can leverage a Configuration Management override or a Twig
template to change the default behavior, it is strongly recommended you trigger
the throbber only on form submits and internal links as these are the only
supported use cases. Be warned!

If you must, assign the behavior to <a> elements carefully. <a> elements can be opened in a new browser tab or window, which would leave the original window locked waiting for reload. Also, <a> elements are sometimes used with modals, so make sure that you identify what classes trigger modal windows and you use :not() to avoid them, or use specific classes when assigning the behavior (example a.not-modal).

Activity

Total releases
5
First release
Feb 2025
Latest release
1 year ago
Releases (12 mo)
0 ▼ from 5
Maintenance
Dormant

Release Timeline

Releases

Version Type Release date
2.0.4 Stable Jul 4, 2025
2.0.3 Stable Jun 13, 2025
2.0.2 Stable May 8, 2025
2.0.1 Stable Feb 21, 2025
2.0.x-dev Dev Feb 21, 2025