# Debugging the display none issue in Discourse embeds

**URL:** https://meta.discourse.org/t/debugging-the-display-none-issue-in-discourse-embeds/411211
**Category:** Support
**Tags:** embedding
**Created:** [August 29, 2026, 1:57pm UTC](https://meta.discourse.org/t/debugging-the-display-none-issue-in-discourse-embeds/411211 "2026-08-29T13:57:49Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Carlo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carlo/32/79036_2.png) [@Carlo](https://meta.discourse.org/u/Carlo)
#### Post date: [August 29, 2026, 5:32pm UTC](https://meta.discourse.org/t/debugging-the-display-none-issue-in-discourse-embeds/411211/2 "2026-08-29T17:32:21Z")

</div>

So after nearly breaking my computer, I’ve found a workaround — probably not the ideal one 😅

It appears that when clicking Reply inside the Full App Embed, the composer actually opens correctly in the DOM (#reply-control.open), but for some reason it remains display: none.

I confirmed this in the browser console: the composer was present, but its computed display value was “none”. Manually running:

`document.querySelector('#reply-control').style.setProperty('display', 'block', 'important');`

immediately made the composer appear and everything worked normally.

As a workaround, adding the following JS to the Discourse theme fixes the issue for me:

`import { apiInitializer } from "discourse/lib/api";`  
`export default apiInitializer((api) => {`  
`if (!document.body.classList.contains("embed-mode")) {`  
`return;`  
`}`  
`const fixComposer = () => {`  
`const composer = document.querySelector("#reply-control.open");`  
`if (composer) {`  
`composer.style.setProperty("display", "block", "important");`  
`}`  
`};`  
`const observer = new MutationObserver(fixComposer);`  
`observer.observe(document.body, {`  
`childList: true,`  
`subtree: true,`  
`attributes: true,`  
`attributeFilter: ["class"],`  
`});`  
`fixComposer();`  
`});`

This seems to fix it completely, and I’ve limited the workaround to embed-mode so it doesn’t affect the normal Discourse interface.

Obviously this probably isn’t the ideal long-term solution, but hopefully this helps identify what is causing the open composer to remain display: none in the Full App Embed.

---

_[View the full topic](https://meta.discourse.org/t/debugging-the-display-none-issue-in-discourse-embeds/411211)._