# Bug: Link on a Container

**URL:** <https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968>\
**Category:** RapidWeaver Elements\
**Created:** [January 17, 2025, 2:34pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968 "2025-01-17T14:34:45Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\
**Post date:** [January 17, 2025, 2:34pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/1 "2025-01-17T14:34:45Z")

</div>

There is a strange bug in the latest version of Elements when I insert a link on a Container. See video.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [January 17, 2025, 2:51pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/2 "2025-01-17T14:51:21Z")

</div>

Can you share the project via Elements Cloud so we can take a look and get it fixed for you?

Also, I had another thought — Are you using any custom code/components in your project (especially in that area, or above)? Could be some malformed custom html causing havoc!

---

<div class="post-metadata">

**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\
**Post date:** [January 17, 2025, 3:33pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/3 "2025-01-17T15:33:13Z")

</div>

Can I send you a message?

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [January 17, 2025, 4:04pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/4 "2025-01-17T16:04:09Z")

</div>

Sure, email it over to [dan@realmacsoftware.com](mailto:dan@realmacsoftware.com) 👍

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [January 17, 2025, 5:19pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/5 "2025-01-17T17:19:20Z")

</div>

Thanks for the project file, we’ve reproduced the issue here and it’s a bug in our Components. We’ll get this fixed up for you in next weeks beta!

---

<div class="post-metadata">

**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\
**Post date:** [January 17, 2025, 5:31pm UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/6 "2025-01-17T17:31:03Z")

</div>

Thanks. Have nice weekend.

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [January 18, 2025, 10:57am UTC](https://forums.realmacsoftware.com/t/bug-link-on-a-container/45968/7 "2025-01-18T10:57:34Z")

</div>

Hi @mrTablet

The issue you’re encountering occurs because a link (`<a>` element) has been placed inside another link, resulting in invalid HTML like this:

```html
<a href="" ...>
  <!-- Container content -->
  <a href="" ...>Button</a>
</a>

```

HTML standards don’t allow `<a>` elements to be nested within other `<a>` elements, as this creates ambiguous behaviour and breaks the rules for valid markup.

While this shouldn’t affect you directly as the end user, I wanted to explain the root cause. 😊

The good news is that we’re working on a fix, which will be included in the next beta. This update will ensure:  
1. The layout remains intact, and  
2. The Container link takes precedence over any linked child components within it.

Thanks for your patience, and let us know if you encounter any other issues!
