Glimmer-site-header.gjs:144 getBoundingClientRect error only when custom plugin enabled

pfaffman · December 10, 2025, 12:50pm

I don’t know if this is your problem, but rather than connectors, you should now use api.renderInOutlet. I find that more intuitive and less fiddly.

github.com/literatecomputing/discourse-custom-components

javascripts%2Fdiscourse%2Fapi-initializers%2Fcustom-components.gjs

main

import { apiInitializer } from "discourse/lib/api";
import ButtonLink from "../components/button-link";
import TextBlock from "../components/text-block";

export default apiInitializer((api) => {
  // loop through settings.buttons and render a button for each one
  settings.buttons.forEach((button) => {
    api.renderInOutlet(
      button.outlet,
      <template><ButtonLink @button={{button}} /></template>
    );
  });

  settings.custom_text_block.forEach((component) => {
    api.renderInOutlet(
      component.outlet,
      <template><TextBlock @component={{component}} /></template>
    );
  });
});

Topic		Replies	Views
Brand header theme component breaks page layout on static and no_ember pages Development	3	1693	January 15, 2019
Can't access element defined in plugin outlet with DOM interface Development	3	685	April 3, 2021
api.renderInOutlet not rendering? Development	11	486	June 28, 2025
Upcoming Header Changes - Preparing Themes and Plugins Development dev-news	36	4689	September 8, 2024
Site header issue when resizing Bug	3	489	November 29, 2022

Glimmer-site-header.gjs:144 getBoundingClientRect error only when custom plugin enabled

Related topics