Drupal is a registered trademark of Dries Buytaert
cms 2.1.3 Update released for Drupal core (2.1.3)! drupal 10.5.11 Update released for Drupal core (10.5.11)! drupal 11.3.11 Update released for Drupal core (11.3.11)! drupal 11.2.13 Update released for Drupal core (11.2.13)! drupal 10.6.10 Update released for Drupal core (10.6.10)! cms 2.1.2 Update released for Drupal core (2.1.2)! drupal 11.1.10 Update released for Drupal core (11.1.10)! drupal 10.5.10 Update released for Drupal core (10.5.10)! drupal 10.4.10 Update released for Drupal core (10.4.10)! drupal 11.2.12 Update released for Drupal core (11.2.12)! drupal 11.3.10 Update released for Drupal core (11.3.10)! drupal 10.6.9 Update released for Drupal core (10.6.9)! drupal 10.6.8 Update released for Drupal core (10.6.8)! drupal 11.3.9 Update released for Drupal core (11.3.9)! drupal 11.3.8 Update released for Drupal core (11.3.8)! drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)!

page_load_progress

599 sites Security covered
View on drupal.org

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
10 months ago
Release cadence
33 days
Stability
80% stable

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