ix-textarea strings displayed as objects

[siemandalorian]

Prerequisites

• I have read the Contributing Guidelines.
• I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?

Created from community: https://community.siemens.com/t/ix-textarea-strings-displayed-as-objects/2804

We recently upgraded ix-angular to v3 and with that replaced all textarea with ix-textarea components. But we faced a problem that even when passing the value as string to ix-textarea (ex: "{"test": "sample data" }" which is a json stored as string it was always shown inside the textarea as [object Object].

        <ix-textarea
          textarea-height="100px"
          textarea-width="100%"
          #credentialsTextArea
          [value]="getFormattedData()"
        ></ix-textarea>

We overcome it by replacing all double quotes with single quotes but be need to modify the text for that.

Can you advise how can we display value like: {"test": "sample data" } inside ix-textarea ?

What type of frontend framework are you seeing the problem on?

Angular

On which version of the frontend framework are you experiencing the issue?

@angular/core@19.2.3

Which version of iX do you use?

v3

Code to produce this issue.

<ix-textarea
          textarea-height="100px"
          textarea-width="100%"
          [value]="{"attribute1": "example1"}"
        ></ix-textarea>

[danielleroux]

@siemandalorian This is the default behaviour of javascript object.

[value]="aObject"

We need to call "toString()" on the object to get an string to render.

If you need to render the object in json format I would recommend to use a pipe e.g. https://angular.dev/api/common/JsonPipe

[siemandalorian]

@danielleroux this is what does not work even if I pass the string to ix-textarea. I checked the type before assigning the value and although it is a string still rendered inside textarea as object.

[github-actions]

Thank you for creating this issue! It has been labeled as needs reproduction.

To help us assist you better, could you please provide a way for us to access the code (such as a GitHub repository or a StackBlitz link). Without a reliable code reproduction, it might be challenging for us to resolve the issue, and we may have to close it.
Thank you for your understanding!

[danielleroux]

@siemandalorian then please create a example (repo or stackblitz) which shows the issue on that base we are analyzing the issue then. Thank you

[MasonVX]

@danielleroux Just came here to report the same thing. And it is also the same for normal input fields. It did work before 3.0.

You do not need a StackBlitz, just go to you demo page and type -> {} in the preview. E.g. https://ix.siemens.io/docs/components/input/code here

Thanks

[LSBOSS]

@danielleroux

Reproduction:

• Please go to https://ix.siemens.io/docs/components/input/code and enter anything in the Basic example that might get interpreted as object (e.g. {} or {"test":"test"}

Look like this:

Screen.Recording.2025-07-01.at.10.56.03.mov

or this:

Screen.Recording.2025-07-01.at.10.56.14.mov

[ridvandmrc]

I have reproduced it and it could be related stencil render mechanism and handling strings, and I found some example they were using some solution and I created PR about it,

#1990

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!