0

How do Tabs handle loading of their content?

Hi everyone,

I have a general question about the Tabs layout component in Ninox 4 (Builder mode),

to better design pages and forms with heavy components (charts, custom components,

views with many records).

 

1. Is the content of a hidden tab evaluated in the background when the page or form

   opens (pre-loading), or only when the user clicks on that tab (lazy loading)?

2. Once a tab has been opened, is its content kept in cache when switching between

   tabs, or is it recalculated each time?

3. Does the same behaviour apply to the Accordion component (collapsed sections)?

4. Is there any official recommendation on using Tabs or Accordions to improve the

   loading time of pages with heavy components?

 

Any documentation or experience would be very helpful.

Thanks!

2 Antworten

null
    • Customer Support Ninox
    • uwe_groegor
    • vor 20 Stunden
    • Gemeldet - anzeigen

    Hello Rafael,
    I will check with the developers.

    • Customer Support Ninox
    • uwe_groegor
    • vor 1 Stunde
    • Gemeldet - anzeigen

     
    Here are the answers to your questions:
    1. Loaded only on click. Only the selected tab’s content is built; the other tabs’ contents aren’t created

    2. No. When the user leaves a tab, its content is removed. When they come back, it is built again

    3. Yes. A collapsed section’s content isn’t built, and collapsing a section removes its content.

    4. We are considering providing information on performance optimization when using Ninox elements—similar to what we do for Ninox3.
    To do this effectively, we need more real-world examples where performance is a concern. This will allow us to analyze these cases in greater detail, make necessary adjustments to our system, or offer recommendations on how to resolve such issues using built-in tools.

Anmelden, um zu antworten

Content aside

  • vor 1 StundeZuletzt aktiv
  • 2Antworten
  • 10Ansichten
  • 2 Folge bereits