CMS Search Component issues

Hi @ben

Congrats on the CMS v2 and the online editor. This was a big step forward for Elements. Thanks for the hard work to make it happen. I just bought 2 Studio licenses for my projects, so impressed I was.

While designing my 1st site with Elements I made really good progress but found 2 issues with CMS Search component.

  1. The clear search box icon (cross in solid circle) is not playing well with dark mode. If you make the search box dark (surface 900) this will not be visible anymore.
  2. The results area is overflowing it’s parent container, resulting in ugly layout and no scrolling. Reason is that the results container is hard-coded to class=“absolute”. When I remove this in the published index.php, these things work well again. I provide pictures for the behaviour and the index.php code in question below.

Thanks for taking a look.

class=absolute in DIV below search box

Bildschirmfoto 2026-06-06 um 21.58.59 <— this is the culprit

absolute manually removed

Bildschirmfoto 2026-06-06 um 21.59.42 ← no more class=“absolute”

correct behavior

Hi @herbing
Glad to hear you’re enjoying the new CMS update :slight_smile:

This is a browser styling issue. The clear search icon colour is, by default, controlled by the browser. However, I’ll add this as an issue and see if we can improve this in a future update :slight_smile:

From your screenshots, I believe this is expected behaviour, but do you have a URL or project file we can take a look at?

Hi @ben

Thanks for getting back to me.

  1. Understood. Thanks.
  2. The position=absolute is created by the CMS search component and I don’t understand why. It causes the results to overflow the parent container, thus destroying the layout. Unfortunately there is no option to configure this in the CMS search component. The site is not yet public reachable, but I uploaded you the project file to support just now,

It’s by design. The CMS Search component is designed to have the results show as a flowing box underneath the search input.

We (or third-parties) will likely add additional CMS search components in the future, but at the moment this is just how the CMS Search works.

Do you see any chance making this a configuration option in the near future?

Do you see any chance making this a configuration option in the near future?

Update: Don’t bother anymore. I fixed it with a one-liner of JS in a custom component.