Skip to content

Order of events during initial page load

Aref Shafaei edited this page Feb 5, 2024 · 1 revision

In the following, we've summarized how a typical Chaise app loads and how Chaise reacts to it.

  1. First, the browser will fetch the assets required to show the content. In this phase, you won't see any content if you started from a fresh tab. If this is from a different page, browsers usually keep showing you the existing tab until the assets are fetched.
step1-1
  1. When the first phase is done, you will see a spinner in the middle of a blank white page with "loading..." text. Chaise is fetching the session and catalog in this phase.
step-2
  1. When the catalog and session requests are made, the navbar will appear. Chaise will now continue with fetching the schema. This is usually the slowest step.
step-3
  1. After the schema request is made, you will see the table name and other elements on the page. Chaise is now waiting for the data to load in this phase, so we will continue showing the "loading..." spinner. We're also showing separate spinners for each facets that has to be loaded.
step-4
  1. When we fetched all the necessary data, all the spinners will disappear, and the page will be fully loaded.
step-5
Clone this wiki locally