I did some investigation from the links shared by Volker and the implementation created by Danny.

So I have done some work, and this is what I have so far, do you guys agree? I rolled back with a couple of things I suggested above, as while developing they were making the code very unclear!

Hi Anne,

Hei Anne, unfortunately, I do not seem to be able to help here as I cannot replicate the issue not even in the wiki environment.

I have investigated the issue and I have been able to replicate it neither in the current main nor by checking out main on and before May the 3rd.

A patch has been raised with the following fixes:

I have done some research on the different components and found the following differences:

All changes have been addressed and the Patch merged. Moving the ticket forward for design review.

All suggested Acceptance criteria have been completed and the item should be ready for "design sign-off"

• Update typeaheadSearch

FYI: I have not updated the typedahead yet as it is still in current changes and development.

hei @Volker_E if you give me some guidance on the dev expectation and naming I can help you here.

For some reason, the gerrit review link was not automatically made.

Hi all , after some investigation and lots of help from @matthiasmullie, we have found out that this is not a train blocker as the issue was not due to any code changes but a single malformed Image.

Hi guys, I am investigating the issue now.
It seems like it is the same error, but a different cause (before it was the existence of a complex value LocationShown), but this does not seem to be the case in this case.

I have opened a patch with the following changes:

I am going to work on the design comments for now, while I gather further information on what was discussed in refinement.

I have implemented the required changes above for the select, lookout and Combobox components.

re: is the button group in codex:
Me and julia already asked about it, and they said that they are not currently building it and will share its position in the roadmap sooon, then also discussed the possibility for us to actually "implement" the component for them!

Correct, we have removed the old function viewer now, so this is completed!

For QA purposes, the error was shown when the browser has "no javascript enabled".