Technical Specifications & Compatibility
Technical Module Name
Supported Odoo Versions
v19.0
License
Odoo
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
576 lines (Python / XML / JS)
Overview & Description
Odoo 19 Odoo 20 Community and Enterprise OPL-1 Version 19.0.1.0.0 Skeleton Loading Odoo shows a blank screen while a view loads. This fills it with a placeholder shaped like the view that is coming. And it will not flicker: a load faster than the threshold shows nothing at all, so a quick page still looks instant rather than flashing grey at you. Module Overview What this module solves. The blank gap Click a menu and the content area goes blank while the view loads. All you get is a small loading chip in the corner, and after three seconds the interface is blocked outright. Odoo 19 ships no skeleton screens at all. A placeholder shaped like what is coming Rows for a list, cards for a kanban, fields for a form, columns for a graph. The user sees the shape of the page arriving instead of an empty rectangle, so the wait reads as progress rather than as nothing happening. The hard part is not drawing it, it is when. A placeholder that appears for eighty milliseconds is worse than no placeholder: it reads as a glitch. Nothing is drawn for the first fraction of a second, and once drawn it stays long enough to be read rather than blinking out. Key Features Everything included in the module. It Does Not Flicker Nothing is drawn for the first 150 ms, and that is configurable A load faster than that is never represented at all Once drawn it stays at least 400 ms, even if the data has arrived A second load during the hold keeps the placeholder up Overlapping loads share one placeholder, leaving when the last finishes Set the threshold to zero to draw immediately Shaped Like The View List: a header row and eight rows of uneven columns Kanban: a responsive grid of cards with a footer and an avatar Form: a title, then two columns of label-and-value pairs Graph and pivot: a row of columns of varying height Anything else: a neutral title-and-lines block Row widths vary but are deterministic, so it reads as content Two Places It Appears Between actions, where Odoo mounts a blank component Inside a view, on filters, pager and group-by In-view it covers the records area only The control panel the user just clicked in is left alone The two are timed independently and can run at once Stale rows are covered rather than left on screen Theme-Proof Everything inherits the theme's own text colour at low opacity Correct in light mode, dark mode and any future theme No second palette to maintain Card outlines are fainter than card contents, so a grid is not a table The overlay is opaque, not translucent Nobody reads figures dimly through a placeholder that is about to change Considerate Animation removed entirely under reduced-motion preferences The shape is the message; the movement is decoration The sheen animates transform only, staying on the compositor Hidden from screen readers, with no text to announce Eight empty announced rows would be worse than silence No permanent change is made to a core layout element Robust Configuration Four settings in General Settings, and an off switch Delivered with the session, so there is no request before the first paint A junk stored value falls back to the default rather than raising A negative delay is clamped to zero Zero is a real setting, not treated as unset The settings form and the web client read through one helper Business Benefits Why it matters. Odoo Feels Faster Nothing is actually quicker, but a wait with visible progress is perceived as shorter than the same wait staring at nothing. Fewer Double Clicks A blank screen invites the user to click again. A placeholder says the request was heard and something is on its way. No Stale Numbers Change a filter and the old rows are covered rather than sitting there looking current while their replacement loads. Nothing To Maintain It inherits your theme's colours, needs no per-view configuration, and switches off from Settings if you change your mind. Screenshots A tour of the placeholder. List Skeleton Screenshot Placeholder A header row and eight rows of uneven columns, mid-load. Kanban Skeleton Screenshot Placeholder A grid of cards with footers and avatars, outlines kept faint. Dark Mode Screenshot Placeholder The same placeholder inheriting a dark theme, with no second palette. Settings Screenshot Placeholder Loading Screens in General Settings, with the four options. Workflow What happens on a click, millisecond by millisecond. The user clicks a menu or changes a filter. Odoo starts loading, and the module starts a timer rather than drawing anything. If the data arrives first, nothing is ever shown. A fast load looks instant, because no placeholder appeared to interrupt it. Past the threshold, the placeholder is drawn. Shaped for the view that is coming, and portalled into the blank area Odoo has already mounted. It stays for its minimum time. Even if the data lands a moment later, so it is read as a loading state rather than as a flash of grey. Overlapping loads are counted, not stacked. A group-by fetching records and aggregates at once shows one placeholder, which leaves when the last of them finishes. The real view replaces it. The host element goes back to exactly what it was, with no lasting change to the layout. Skeleton Shapes By View Type View What is drawn List A header row and eight rows of uneven columns Kanban A responsive grid of six cards with a footer and an avatar Form A title, then two columns of label-and-value pairs Graph and Pivot A row of columns of varying height Calendar and anything unknown A neutral title-and-lines block Configuration Four settings, and an off switch. Settings, General Settings, Loading Screens Setting Default What it does Skeleton Loading On The master switch for the whole module Draw After 150 ms How long to wait before drawing anything; zero draws immediately Keep For At Least 400 ms The minimum time a drawn placeholder stays on screen Cover Reloads Too On Whether filters, pager and group-by also get a placeholder Tuning The Timings Raise Draw After on a fast local server so fewer loads ever show one Lower it on a slow connection so users see feedback sooner Set it to zero to draw straight away, accepting the flicker Raise Keep For At Least if placeholders still feel snatched away Turn Cover Reloads Too off to leave in-view refreshes alone Access Who Can do Settings administrators Change the four settings for the database Everybody else See the placeholders; nothing to configure per user No new security group is added. The settings are ordinary system parameters behind the standard Settings access. Settings travel with the session, not by a request. Fetching the configuration over the network before the first paint would be the very delay the module exists to hide, so the values are delivered with the session information instead. Technical Details What it touches, and how. Module Information Technical Name web_skeleton_loading_aura Version 19.0.1.0.0 Category Technical License OPL-1 Dependencies web, base_setup New Models None. Three core models are extended, nothing is added. External Libraries None. No animation library, no CSS framework. Automated Tests 15 JavaScript unit tests, 12 Python tests, and a browser tour What It Extends Model Why ir.http To put the settings into the session before the first paint ir.config_parameter To read the stored values safely, with defaults and clamping res.config.settings To expose the four options in General Settings The rest is client-side: a service, an overlay component, and small patches on the layout and the model. Design Notes Timing is the feature. A threshold before drawing and a floor after it are what separate a loading state from a flash of grey. One colour, inherited. Drawing everything from the current text colour at low opacity means there is no second palette to keep in step with a theme. Graph and pivot load lazily. They are not in the main bundle, so neither is the patch for them. The layout change is scoped. The host is only made a containing block while a placeholder is actually inside it, using a CSS selector rather than a permanent edit to a core element. Configuration cannot break the client. A junk value stored in a system parameter falls back to its default rather than raising while the session is being built, because an exception there would leave the user with no Odoo at all. Compatibility Where the module runs. Item Supported Odoo Version 19.0 Current Hosting Odoo.sh, On-Premise and any self-managed deployment Views Covered List, kanban, form, graph, pivot, and a neutral fallback for the rest Light And Dark Themes Yes, by inheriting the current text colour rather than fixing one Reduced Motion Yes, the animation is removed entirely Screen Readers Hidden from them, deliberately, with nothing to announce Mobile and Tablet Yes, the kanban grid is responsive like the real one Backend Only Yes. The website frontend is untouched. Supported Editions Both editions, one code base. Community Edition Supported Depends only on web and base_setup, so it runs on the leanest installation there is. Enterprise Edition Supported Runs unchanged on Enterprise, covering its views through the same shape rules and the same neutral fallback. Odoo.sh Supported No extra Python packages, and nothing to build. It deploys with no change to your configuration. Installation Install and it works. Copy the module. Place the web_skeleton_loading_aura folder in your Odoo addons path, then update the apps list from developer mode. Install Skeleton Loading. Only web and base_setup are required, and both are always present. Refresh the browser. The placeholders are active immediately, with sensible defaults and no configuration needed. Tune it if you want to. Settings, then General Settings, then Loading Screens, where the timings and the off switch live. No data is created and no model is added. Uninstalling removes the placeholders and leaves the database exactly as it was. Frequently Asked Questions The questions asked most often. No, and it does not claim to. Nothing loads any quicker. What changes is that the wait has visible progress in it instead of a blank rectangle, and a wait you can see the shape of is perceived as shorter than the same wait spent looking at nothing. No. Nothing is drawn for the first 150 milliseconds, so a load that finishes inside that is never represented at all. Once a placeholder is drawn it stays for at least 400 milliseconds even if the data has already landed, so it never appears and vanishes in the same instant. Both numbers are settings. Yes, without configuration. Every shape is drawn from the current text colour at low opacity rather than a fixed grey, so it takes on whatever the theme sets, in light mode, dark mode and any theme released later. There is no second palette to keep in step. Both. Between actions the placeholder fills the blank area Odoo mounts, and inside a view it covers the records area on a filter, a pager click or a group-by, leaving the control panel the user just clicked in untouched. The in-view behaviour can be switched off on its own. A reduced-motion preference removes the animation entirely while keeping the placeholder, because the shape is the message and the movement is only decoration. Where the sheen does run it animates a transform only, so it stays on the compositor and costs nothing in layout. Yes, with one switch in General Settings, and Odoo goes back to exactly what it did before. You can also keep it for view changes but switch it off for in-view reloads, or set the draw threshold high enough that only genuinely slow pages ever show one. No new models and no new security groups. It extends three core models so the settings can be stored and delivered with the session, and the rest is client-side. Uninstalling leaves the database as it was. Changelog Release history. Version 19.0.1.0.0 Initial Release Skeleton placeholders between actions and on in-view reloads Shapes for list, kanban, form, graph and pivot, plus a neutral fallback A draw threshold so fast loads show nothing at all A minimum on-screen time so placeholders never blink out Overlapping loads share one placeholder and one lifetime Records area covered on reload, control panel left alone Colours inherited from the theme, correct in light and dark Opaque overlay, so stale figures are never half-readable Animation removed under a reduced-motion preference Hidden from screen readers, with transform-only animation Four settings in General Settings, delivered with the session Junk, negative and zero configuration values all handled safely 15 JavaScript unit tests, 12 Python tests and a browser tour Support We answer, and we keep our modules current. Email odooaura@gmail.com Website www.auraodoo.tech YouTube youtube.com/@Auraodoo Free support for bug fixes on the Odoo version you downloaded. Customisation and installation help available on request. Aura Odoo Tech Odoo modules built to be understood, not just installed. Odoo 19 OPL-1 web_skeleton_loading_aura www.auraodoo.tech | odooaura@gmail.com | youtube.com/@Auraodoo
Key Capabilities & Features
- Nothing is drawn for the first 150 ms, and that is configurable
- A load faster than that is never represented at all
- Once drawn it stays at least 400 ms, even if the data has arrived
- A second load during the hold keeps the placeholder up
- Overlapping loads share one placeholder, leaving when the last finishes
- Set the threshold to zero to draw immediately
- List: a header row and eight rows of uneven columns
- Kanban: a responsive grid of cards with a footer and an avatar
- Form: a title, then two columns of label-and-value pairs
- Graph and pivot: a row of columns of varying height
- Anything else: a neutral title-and-lines block
- Row widths vary but are deterministic, so it reads as content
- Between actions, where Odoo mounts a blank component
- Inside a view, on filters, pager and group-by
- In-view it covers the records area only
- The control panel the user just clicked in is left alone
- The two are timed independently and can run at once
- Stale rows are covered rather than left on screen
- Everything inherits the theme's own text colour at low opacity
- Correct in light mode, dark mode and any future theme
- No second palette to maintain
- Card outlines are fainter than card contents, so a grid is not a table
- The overlay is opaque, not translucent
- Nobody reads figures dimly through a placeholder that is about to change
- Animation removed entirely under reduced-motion preferences
- The shape is the message; the movement is decoration
- The sheen animates transform only, staying on the compositor
- Hidden from screen readers, with no text to announce
- Eight empty announced rows would be worse than silence
- No permanent change is made to a core layout element
- Four settings in General Settings, and an off switch
- Delivered with the session, so there is no request before the first paint
- A junk stored value falls back to the default rather than raising
- A negative delay is clamped to zero
- Zero is a real setting, not treated as unset
- The settings form and the web client read through one helper
- The user clicks a menu or changes a filter. Odoo starts loading, and the module starts a timer rather than drawing anything.
- If the data arrives first, nothing is ever shown. A fast load looks instant, because no placeholder appeared to interrupt it.
- Past the threshold, the placeholder is drawn. Shaped for the view that is coming, and portalled into the blank area Odoo has already mounted.
- It stays for its minimum time. Even if the data lands a moment later, so it is read as a loading state rather than as a flash of grey.
- Overlapping loads are counted, not stacked. A group-by fetching records and aggregates at once shows one placeholder, which leaves when the last of them finishes.
- The real view replaces it. The host element goes back to exactly what it was, with no lasting change to the layout.
- Raise Draw After on a fast local server so fewer loads ever show one
- Lower it on a slow connection so users see feedback sooner
- Set it to zero to draw straight away, accepting the flicker
- Raise Keep For At Least if placeholders still feel snatched away
- Turn Cover Reloads Too off to leave in-view refreshes alone
- Timing is the feature. A threshold before drawing and a floor after it are what separate a loading state from a flash of grey.
- One colour, inherited. Drawing everything from the current text colour at low opacity means there is no second palette to keep in step with a theme.
- Graph and pivot load lazily. They are not in the main bundle, so neither is the patch for them.
- The layout change is scoped. The host is only made a containing block while a placeholder is actually inside it, using a CSS selector rather than a permanent edit to a core element.
- Copy the module. Place the web_skeleton_loading_aura folder in your Odoo addons path, then update the apps list from developer mode.
- Install Skeleton Loading. Only web and base_setup are required, and both are always present.
- Refresh the browser. The placeholders are active immediately, with sensible defaults and no configuration needed.
- Tune it if you want to. Settings, then General Settings, then Loading Screens, where the timings and the off switch live.
- Skeleton placeholders between actions and on in-view reloads
- Shapes for list, kanban, form, graph and pivot, plus a neutral fallback
- A draw threshold so fast loads show nothing at all
- A minimum on-screen time so placeholders never blink out
- Overlapping loads share one placeholder and one lifetime
- Records area covered on reload, control panel left alone
- Colours inherited from the theme, correct in light and dark
- Opaque overlay, so stale figures are never half-readable
- Animation removed under a reduced-motion preference
- Hidden from screen readers, with transform-only animation
- Four settings in General Settings, delivered with the session
- Junk, negative and zero configuration values all handled safely
- 15 JavaScript unit tests, 12 Python tests and a browser tour
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
Screenshots & Previews
1 image availableExpand Preview
The AuraOdoo Quality Guarantee
100% Tested
Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.
Clean Architecture
Built according to official Odoo guidelines and PEP 8 standards with zero bloat.
Dedicated Support
Free installation assistance and quick bug turnaround from our team.