# Achieveving the same fading page transition as NodeBB?

**URL:** <https://meta.discourse.org/t/achieveving-the-same-fading-page-transition-as-nodebb/141678>\
**Category:** Development\
**Created:** [15 בפברואר,‏ 2020,‏ 11:29am UTC](https://meta.discourse.org/t/achieveving-the-same-fading-page-transition-as-nodebb/141678 "2020-02-15T11:29:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)\
**Post date:** [15 בפברואר,‏ 2020,‏ 2:47pm UTC](https://meta.discourse.org/t/achieveving-the-same-fading-page-transition-as-nodebb/141678/4 "2020-02-15T14:47:12Z")

</div>

Hi, I tried the feature in your plugin, but that’s not quite the same: when I display the topic list, that’s the requested content which fades in after being loaded; on NodeBB, it’s the current content that fades out while the next content is being loaded.

The main thing is that we should find a way to prevent Discourse removing the current HTML immediately after clicking a link. The HTML should be kept in place until the new content has been loaded (or until the fade out effect has ended but I’m not sure that’s better 🙃) and is ready to be displayed.

---

_[View the full topic](https://meta.discourse.org/t/achieveving-the-same-fading-page-transition-as-nodebb/141678)._