# Posts with embedded polls fail to load

**URL:** https://meta.discourse.org/t/posts-with-embedded-polls-fail-to-load/135549
**Category:** Support
**Tags:** unsupported-install
**Created:** [December 10, 2019, 12:11pm UTC](https://meta.discourse.org/t/posts-with-embedded-polls-fail-to-load/135549 "2019-12-10T12:11:08Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![nmcgovern](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nmcgovern/32/132630_2.png) [@nmcgovern](https://meta.discourse.org/u/nmcgovern)
#### Post date: [December 10, 2019, 7:03pm UTC](https://meta.discourse.org/t/posts-with-embedded-polls-fail-to-load/135549/9 "2019-12-10T19:03:13Z")

</div>

For those who are interested, the second error also happens here on meta - visit [https://meta.discourse.org//t/posts-with-embedded-polls-fail-to-load/135549](https://meta.discourse.org//t/posts-with-embedded-polls-fail-to-load/135549) as an example 🙂

It looks like the [basic URL parser spec](https://url.spec.whatwg.org/#concept-basic-url-parser) says that a browser will always throw a validation error if a path starts with two slashes.

I suppose that one could argue that discourse should be checking that the path it is passing to history.replaceState() is valid before it does so and fixing it, but that sounds like a whole heap of pain (ie: implementing your own url parser and automagical fixer) for something which would be fairly rare in the wild.

_This post has been brought to you by melted brains from reading WHATWG HTML living standards_

---

_[View the full topic](https://meta.discourse.org/t/posts-with-embedded-polls-fail-to-load/135549)._