nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HTML code in Experience builder Text widget

SigLM

It is easier for some data to create template in a text field with html code. Experience Builder should interpret this code in text widget to use it in list widget for example. We could connect data to it and display information dynamically without text configuration in Experience builder

Encuentra más publicaciones etiquetadas con

Status: Abrir

Comentarios

MappyIan

As someone relatively new to ExB, I've just discovered that the Text widget doesn't support html tables. I'm flabbergasted that 5.5 years after this idea was first logged this still hasn't been implemented. Basic HTML really must be possible in this day and age. Especially when similar functionality has been available in Hub for over three years. Where's the consistency Jack?

DavidRasner1

I would like to see dynamic html (let us add feature attributes) in the emded widget.

This is fairly common in other low code solutions. I like to use it to create custom charts using various APIs.

You could embed external viewers for 3d models, documents, 360 images, all kinds of stuff...

MichaelSmith4

There is a clunky workaround this if you have access to a webserver. Rather than putting HTML in a text field, instead put it in an HTML file on your web server. Then store the URL in the text field. Use "Embed" widget in Experience Builder instead of "Text" widget to get your HTML file into your EB project. You can also build the URL from an attribute if you don't want to store the whole thing. Like my project I wanted to embed HTML descriptions of various species as you click on that species in the list. I build the URL using the species code field and link that back to a species-specific HTML file.

YvonneBooysen

Supporting this, it's a massive pain not to have this pretty basic functionality in EB.

MichaelSmith4

I support full HTML or at least RTF tag support in text. As it stand now, AGOL's map viewer will support <b> and <i> in a text field and display them correctly, but not Experience Builder.

KevinMWright13

Additionally, full HTML should be supported in the String field type of a hosted Feature Layer so that you can use the input to the Experience Builder be a field value. Currently it looks like that is not the case. It appears to only allow Rich Text.

JanSarata

Supporting this idea. Furthemore the similar behaviour is available in ArcGIS Hub text widget where I can use html/css to specify my content to my needs. I would appreciate the same in Experience Builder text widget.

SigLM

I saw that this option was almost enable in the embed widget but only with website url not with code. We should be enable connect to data when code is used and replace code field by attribute.

Únete a la Conversación

Inicia sesión para publicar, seguir contenido y más. ¿Nuevo aquí? Regístrate gratis.