# Theme component containing a web component that modifies the post's URL anchor freezes the browser

**URL:** <https://meta.discourse.org/t/theme-component-containing-a-web-component-that-modifies-the-posts-url-anchor-freezes-the-browser/315548>\
**Category:** Development\
**Created:** [July 9, 2024, 9:19am UTC](https://meta.discourse.org/t/theme-component-containing-a-web-component-that-modifies-the-posts-url-anchor-freezes-the-browser/315548 "2024-07-09T09:19:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![wwerner](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wwerner/32/430199_2.png) [@wwerner](https://meta.discourse.org/u/wwerner)\
**Post date:** [July 9, 2024, 10:26am UTC](https://meta.discourse.org/t/theme-component-containing-a-web-component-that-modifies-the-posts-url-anchor-freezes-the-browser/315548/2 "2024-07-09T10:26:06Z")

</div>

Answering my own question: Seems it had nothing to do with Discourse after all.  
A certain combination of params sent the web component into an `scheduleUpdate` loop.  
Sorry for the noise.

For reference, here’s what I did:

- Used a non-minified version of rapidoc in the theme component
- Used the debugger while the site was stuck
- Looked at the call-stack & found the culprit triggering repeated updates (`show-curl-before-try`)
- Changed rapidoc’s params not to trigger this scenario anymore

If you feel this topic doesn’t add to the discussion/is irrelevant, feel free to remove.

Thanks anyway and sorry for the noise again

---

_[View the full topic](https://meta.discourse.org/t/theme-component-containing-a-web-component-that-modifies-the-posts-url-anchor-freezes-the-browser/315548)._