# New behavior of the IncludeInPage property

**URL:** <https://forum.dotvvm.com/t/new-behavior-of-the-includeinpage-property/372>\
**Category:** Discussion in English\
**Created:** [August 31, 2026, 12:17am UTC](https://forum.dotvvm.com/t/new-behavior-of-the-includeinpage-property/372 "2026-08-31T00:17:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![daltinkurt](https://forum.dotvvm.com/user_avatar/forum.dotvvm.com/daltinkurt/32/11_2.png) [@daltinkurt](https://forum.dotvvm.com/u/daltinkurt)\
**Post date:** [August 31, 2026, 12:17am UTC](https://forum.dotvvm.com/t/new-behavior-of-the-includeinpage-property/372/1 "2026-08-31T00:17:51Z")

</div>

Previously, the **IncludeInPage** and **Visible** properties could already be used together to prevent blinking.

```auto
InludeInPage={value: Show}
Visible={value: Show}

```

I don’t understand why you changed the **IncludeInPage** behavior.  
Doesn’t this put extra load on the page?

[Release DotVVM 5.0.0 major release · riganti/dotvvm](https://github.com/riganti/dotvvm/releases/tag/v5.0.0)

IncludeInPage no longer shows uninitialized content. When IncludeInPage={value: …} now evaluates to false on the server, it treats the controls as Knockout template resources (#2056). This eliminates the visibility of uninitialized content before JavaScript hides these controls.

---

<div class="post-metadata">

**Author:** ![tomasherceg](https://forum.dotvvm.com/user_avatar/forum.dotvvm.com/tomasherceg/32/513_2.png) [@tomasherceg](https://forum.dotvvm.com/u/tomasherceg)\
**Post date:** [August 31, 2026, 7:22am UTC](https://forum.dotvvm.com/t/new-behavior-of-the-includeinpage-property/372/2 "2026-08-31T07:22:21Z")

</div>

Our goal was to ensure that there would be no flickering if you use just `IncludeInPage={value: Show}`. There should be no reason to use both of them.  
I don’t have a benchmark for that, but I think it should be even faster. In DotVVM 4._, when the page was loaded, Knockout had to take the contents of the element and create the template at runtime. With 5._, the template is already there, and Knockout can just use it.

---

<div class="post-metadata">

**Author:** ![daltinkurt](https://forum.dotvvm.com/user_avatar/forum.dotvvm.com/daltinkurt/32/11_2.png) [@daltinkurt](https://forum.dotvvm.com/u/daltinkurt)\
**Post date:** [August 31, 2026, 6:26pm UTC](https://forum.dotvvm.com/t/new-behavior-of-the-includeinpage-property/372/3 "2026-08-31T18:26:50Z")

</div>

I loved the new features and updates that came with v5.

Great job and thanks!

However, instead of changing `IncludeInPage`, I wish you had added it as a new feature with a different name (e.g., `IncludeInPageWithTemplate`).

---

<div class="post-metadata">

**Author:** ![tomasherceg](https://forum.dotvvm.com/user_avatar/forum.dotvvm.com/tomasherceg/32/513_2.png) [@tomasherceg](https://forum.dotvvm.com/u/tomasherceg)\
**Post date:** [September 1, 2026, 11:33am UTC](https://forum.dotvvm.com/t/new-behavior-of-the-includeinpage-property/372/4 "2026-09-01T11:33:52Z")

</div>

Does it cause any problems or side effects?  
If it doesn’t work correctly in combination with Visible, it is a bug that we should fix. Or does the template cause any other problems?