website logo
⌘K
Introduction
PORTAL
Agency Whitelabelling
PAGES
Pages - Accessing Page Data
Pagination Layouts
Page Templates
FORMS
CATEGORIES
Filtering WebApps and Modules by Categories
Outputting Categories on WebApp / Module / eCommerce Layouts
Outputting Category Fields in any Location
Category Detail Layouts
FAQ - Categories
COMPANY INFORMATION
Company Information
SITE SEARCH
Site Search
PUBLIC API/ZAPIER
Zapier - Formatting arrays correctly
Public API/Zapier Changelog
MODULES
Module Marketplace
Building Custom Modules
Siteglide Modules
Front-end Submit Modules
DATA STRUCTURES
Creating WebApps from the CLI
Field Types
WEBAPPS
Front-end Submit WebApps
Layouts
Search and Filtering
Understanding Custom Field Names and IDs
FAQ - WebApps
CRM
User Details
User Secure Zones
Storing User's Favourite WebApp / Module Items
User's Form Submissions (Cases)
How Users Edit their Email and Password Front End
Editing a User's CRM record Front End with Custom Field Sets
CLI
Introducing Siteglide CLI
CLI Changelog
Secure Zones with CLI
Page Templates with Siteglide CLI
Pages with Siteglide CLI
Includes with Siteglide CLI
Managing Email Templates
Migrate - Manual Form setup
Migrate - Convert existing Forms
Liquid
Accessing Assets
Liquid Dot Notation
Using WebApp Collections- Tutorial
Using the current_user object with Secure Zones
Preventing Duplicate Content with Query Parameters- Canonical URL and Robots.txt
FAQ - Liquid
GraphQL
Tutorial Overview
About GraphQL
Tutorial 1- Your First Query
Tutorial 2 - Pagination
Tutorial 3 - Filtering the Results
Tutorial 3 - Answers to the First Filtering Challenge
Tutorial 4 - Advanced Filtering
Tutorial 4 - Challenge Answers
Tutorial 5 - Using Liquid to run GraphQL queries on your Site
Tutorial 6 - Variables
Tutorial 6 - Answers to the Variables Challenge
Tutorial 7 - Sorting
Tutorial 8 - Building a Liquid API GET Endpoint Page powered by GraphQL queries
Best Practice and Performance
Module/WebApp Caching
Getting Started with Liquid Caching - to Reduce Server Response time and Improve Performance
Includes
ecommerce/checkout_standard
Frequently Asked Questions
Using Liquid Logic to Check if a field exists, or is empty on the Front End
How do I learn more about Liquid?
How to setup a multi domain start page
Docs powered by archbee 

Adding Custom CSS To Show Form Submit Process

7min

When a Form submits, it can take a moment to make the requests it needs. Here's how you can use CSS to show submission progress.

Introduction

When a Form submits, it can take a moment to make the requests it needs. This is especially true with eCommerce Forms which need to make multiple requests for security reasons. 

This Article will explain how you can use CSS to show submission progress and let the User know your Form is still submitting without errors.

You may also be interested to read about how you can use a custom validation function to change the way the Form behaves when validation errors are found: Custom JavaScript Validation for Forms

The CSS Class

When you submit a Form, the HTML Form element has two class names added to it:

  • "form_submitting"
  • "form_x_submitting" where x represents the ID of the Form in Admin

These classes should be removed if the Form is interrupted by a valid error, e.g. validation errors, so targeting one of these classes should tell you that the Form is busy submitting and the User should wait for completion.  

The Simplest Example

In this example, we'll use CSS to select all Forms that are busy submitting globally. You may choose to select particular Forms differently.

HTML
|
<style>
  form.form_submitting {
    opacity: 0.3;
  }
</style>


A More Complex Example

In this example, a spinner icon has been added to the Form Layout in advance: <i class="fas fa-spinner fa-5x"></i>

The CSS demonstrates how Front-End CSS is used to achieve a different effect:

HTML
|
<style>
  .fa-spinner {
    display: none;
  }
  form.form_submitting {
    opacity: 0.3;
  }
  form.form_submitting .fa-spinner {
    display: block;
    animation: spin 5s infinite;
  }
  @keyframes spin {
    from {transform: rotate(0deg);}
    to {transform: rotate(359deg);}
  }
</style>


Validation

A future update will remove the class "form_submitting" when a validation error occurs. For now, we'd recommend you follow the steps in this article to build a custom error function: Custom JavaScript Validation for Forms. With this, you'll be able to write JavaScript to remove the "form_submitting" class manually when there is an error.

JS
|
var forms_submitting = document.querySelectorAll("form_submitting");

for (i=0;i<forms_submitting;i++) {
  forms_submitting[i].classList.remove("form_submitting");
}




Updated 06 Apr 2023
Did this page help you?
Yes
No
PREVIOUS
Adding a Progress Bar
NEXT
Dynamic Content in Workflow and Autoresponder Emails
Docs powered by archbee 
TABLE OF CONTENTS
Introduction
The CSS Class
The Simplest Example
A More Complex Example
Validation