# Chrome: Section d-splash makes page static. Removing section id makes it working again

**URL:** <https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749>\
**Category:** Product Support\
**Created:** [January 24, 2023, 4:25pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749 "2023-01-24T16:25:07Z")\
**Posts on this page:** 13\
**Page:** 1

## AI-generated summary

Users [Johnny_JD](/t/-/252749/1) and [Koen_Verheyen](/t/-/252749/8) report that Discourse pages become unresponsive (“static”) in Chrome, specifically when the `<section id="splash">` element is present. Removing this element via DevTools restores functionality. The issue appears tied to Chrome extensions — [Johnny_JD](/t/-/252749/7) suspects Bitwarden or YouTube AutoQuality, while [Koen_Verheyen](/t/-/252749/8) confirms it doesn’t occur in Chrome Canary or other browsers. [Falco](/t/-/252749/9) suggests isolating the culprit by disabling extensions one-by-one, or testing in incognito mode with extensions toggled individually — a method [Koen_Verheyen](/t/-/252749/12) eventually used, though the exact extension remains unidentified. A temporary workaround using Tampermonkey to remove the element is mentioned [Koen_Verheyen](/t/-/252749/10). No console errors are reported, making DevTools debugging difficult without extension isolation. The issue persists across OSes (Windows, macOS) and Chrome versions (109.0.5414.120), but not universally — others like [JammyDodger](/t/-/252749/6) report no issues. The thread remains unresolved, with no confirmed root cause or fix from Discourse core.

<div class="post-metadata">

**Author:** ![Johnny\_JD](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johnny_jd/32/290411_2.png) [@Johnny\_JD](https://meta.discourse.org/u/Johnny_JD)\
**Post date:** [January 24, 2023, 4:25pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/1 "2023-01-24T16:25:07Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/4X/8/1/3/8137a3d4015751dce1ac16b8cd819742cbcb80f4.png)

Seems like a bug specific for some configurations of Chrome.

It is on different pages. Removing profile helps for a day. Clearing cache etc does nothing good for it.

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 24, 2023, 5:07pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/2 "2023-01-24T17:07:46Z")

</div>

What do you mean by “static”?

Moving to #Support since there are no clear reproduction steps.

---

<div class="post-metadata">

**Author:** ![Johnny\_JD](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johnny_jd/32/290411_2.png) [@Johnny\_JD](https://meta.discourse.org/u/Johnny_JD)\
**Post date:** [January 25, 2023, 1:44pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/3 "2023-01-25T13:44:53Z")

</div>

Static means - static. LITERALLY.

Steps of replication. Open Discourse.  
Steps of avoidance: Remove entire \<section id…

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 25, 2023, 1:57pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/4 "2023-01-25T13:57:40Z")

</div>

> [@Johnny\_JD](#):
>
> Steps of replication. Open Discourse.

Just tried opening Discourse here on my phone and this site isn’t static, I could even type this reply just fine. 😁

Can you provide a little more detail on the reproduction steps? Like what browser, browser version, OS, OS version and URL trigger this issue.

---

<div class="post-metadata">

**Author:** ![Johnny\_JD](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johnny_jd/32/290411_2.png) [@Johnny\_JD](https://meta.discourse.org/u/Johnny_JD)\
**Post date:** [January 25, 2023, 2:13pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/5 "2023-01-25T14:13:04Z")

</div>

> **[Bug](https://meta.discourse.org/c/contribute/bug/1)**
>
> A bug report means something is broken, preventing normal/typical use of Discourse. Do be sure to search prior to submitting bugs. Include repro steps, and only describe one bug per topic please. If your topic is about an official plugin, include the plugin tag.

> [@Chrome: Section d-splash makes page static. Removing section id makes it working again](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/3):
>
> Static means - static. LITERALLY. Steps of replication. Open Discourse. Steps of avoidance: Remove entire \<section id…

PC:  
Chrome is up to date

Version 109.0.5414.120 (Official Build) (64-bit)

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/c/9/9c9cce9f65838b7432208006b221149e092342bd.png)

---

<div class="post-metadata">

**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\
**Post date:** [January 25, 2023, 2:26pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/6 "2023-01-25T14:26:30Z")

</div>

I’ve got latest Chrome open on Windows 11, and it’s working for me. Do you have any browser extensions that could be having an effect?

---

<div class="post-metadata">

**Author:** ![Johnny\_JD](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johnny_jd/32/290411_2.png) [@Johnny\_JD](https://meta.discourse.org/u/Johnny_JD)\
**Post date:** [January 25, 2023, 2:27pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/7 "2023-01-25T14:27:35Z")

</div>

It is possible, that this is problem, because after resetting profile it behaves different.

It seems that bitwarden plugin / or youtube autoquality is not compatible with discourse.

---

<div class="post-metadata">

**Author:** ![Koen\_Verheyen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/koen_verheyen/32/291382_2.png) [@Koen\_Verheyen](https://meta.discourse.org/u/Koen_Verheyen)\
**Post date:** [January 31, 2023, 1:46pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/8 "2023-01-31T13:46:41Z")

</div>

I’m having the same issue (for months now). Discourse pages just don’t respond on scrolling or keyboard (basically unworkable if you can only read the top of a thread). It has to do with interference with a Chrome extension probably as it doesn’t occur on other browsers or Chrome Canary (which doesn’t have any extensions). Indeed removing the `<section id="splash">` element from the DOM with devtools makes it work. When I inspect in working browsers, that section element is not there upon loading, so there may be something keeping it in the DOM in my default Chrome. However I have removed my Bitwarden extension and the problem is still there (don’t have the Youtube autoquality plugin).

Any advise on how to find the culprit is welcome.

Probably not relevant but working on Mac OS.

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 31, 2023, 1:53pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/9 "2023-01-31T13:53:38Z")

</div>

> [@Koen\_Verheyen](#):
>
> Any advise on how to find the culprit is welcome.

Remove one extension at time until it works again and you will find the culprit.

---

<div class="post-metadata">

**Author:** ![Koen\_Verheyen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/koen_verheyen/32/291382_2.png) [@Koen\_Verheyen](https://meta.discourse.org/u/Koen_Verheyen)\
**Post date:** [January 31, 2023, 2:25pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/10 "2023-01-31T14:25:13Z")

</div>

> [@Falco](#):
>
> Remove one extension at time until it works again and you will find the culprit.

You sure there’s no better way to dig into this using devtools? Not really keen to go and possibly delete over 30 extensions to maybe not even find the solution there.

For now I’m using a Tampermonkey script to just ditch the DOM element entirely but that’s just a workaround obviously.

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 31, 2023, 3:01pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/11 "2023-01-31T15:01:52Z")

</div>

> [@Koen\_Verheyen](#):
>
> You sure there’s no better way to dig into this using devtools?

Unless there is a DevTools console error log that you can use, I don’t see how.

> [@Koen\_Verheyen](#):
>
> Not really keen to go and possibly delete over 30 extensions to maybe not even find the solution there.

You can use an incognito session, and toggle “Allow in Incognito” for one extension at time until it’s working. Wouldn’t take over 10 minutes.

---

<div class="post-metadata">

**Author:** ![Koen\_Verheyen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/koen_verheyen/32/291382_2.png) [@Koen\_Verheyen](https://meta.discourse.org/u/Koen_Verheyen)\
**Post date:** [January 31, 2023, 3:32pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/12 "2023-01-31T15:32:26Z")

</div>

Thanks for the suggestion. For some reason it’s gone now and I still don’t know which extension it was. Removed one extension at some point that was already disabled but don’t remember which it was, so it may have been that one.

Even re-installed Bitwarden to make sure it wasn’t that one after all.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [March 2, 2023, 3:33pm UTC](https://meta.discourse.org/t/chrome-section-d-splash-makes-page-static-removing-section-id-makes-it-working-again/252749/13 "2023-03-02T15:33:07Z")

</div>

Closed on March 2, 2023, 3:33pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
