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; } } }

¿Cuál es la forma más sencilla de añadir un hipervínculo a una ventana emergente?

RobBlash

Quiero iniciar una encuesta desde una ventana emergente. ¿Hay alguna forma sencilla de añadir un hipervínculo sin tener que crear una ventana emergente totalmente personalizada? Me gustaría que la ventana emergente tuviera el mismo aspecto que el estilo predeterminado.

En una ventana emergente personalizada, he descubierto cómo imitar el HTML de la tabla (de la ventana emergente predeterminada); sin embargo, los elementos HTML de la tabla no admiten el atributo class. Esto significa que el CSS aplicado a las ventanas emergentes predeterminadas no funciona en la ventana emergente personalizada, lo que se nota sobre todo al verlas en Collector.

En resumen, ¿hay otra forma de añadir hipervínculos a una ventana emergente?

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

AdrianWelsh

Rob,

Sure, but you kind of have to trick it a little.

So, if your attribute said: " www.google.com "

You would need to write it like this: " <a href="url">www.google.com</a> "

This essentially turns it into a clickable link.

RobBlash

Thanks for the suggestion. Maybe I should clarify my question a little bit. I'm not trying to show a field that is populated with a url. I'm trying to add a hyperlink to a specific survey as shown in my attachment.

Is there another way to do this without configuring "a custom attribute display" for the popup? Alternatively, is there a way to style a custom popup to look the same as the default popups?

RobertScheitlin__GISP

Rob,

I do not know of a way to add a link that is not data from an attribute field without using custom attribute display. As far as being able to get the popup to look like the default "A list of field attributes". The way to do it is as outlined here (it involves some work depending on the number of attributes):

Leave the popup configured as "A list of field attributes".
click on on of the feature in the map viewer to display the popup.
right click on one of the attributes in the popup and choose inspect (Google Chrome). You will get something like this:
Choose the parent table element and right click > copy > copy element
Now change the popup configuration to "a custom attribute display".
In the "Custom Attribute Display" configuration dialog switch to "view html source" (toolbar bottom row left button) and paste the copied element.
Find the <td class="attrValue">blah blah</td> and select/highlight the "blah blah" and then click the "+" button and choose the field.
Repeat for all attribute fields.
Finally add you custom link test to the "Custom Attribute Display" configuration dialog.

RobBlash

Robert,

Thanks for the great explanation. This is how my popups are currently set up, but unfortunately the class attribute for the table cell elements <td> does not stick. There is limited support for HTML element attributes as per the AGOL help:

Supported HTML—ArcGIS Online Help | ArcGIS

I've added some inline styling to at least get the font color to match, and this works well enough on the web. However, in Collector the popups are not so nice. I'm not sure how the html is ultimately processed in Collector, so this is why I was looking for an alternative way to add a hyperlink. I think we'll just have to live with some ugly popups.

RobertScheitlin__GISP

Rob,

Those classes are the ones that esri uses when they make the popup so I am not sure why you had an issue with them. During my testing they worked fine.

ChadKopplin

Rob,

In your underlying shapefile or feature class, how about adding a new field and just call it hyperlink, then calculate the records to your hyperlink URL, then it will be available in your popup in collector, you may have to choose that field to be displayed.

RobBlash

This would work, but to me it's a bit of a clunky solution. It would require updating a few thousand existing features + maintaining another attribute for all new features.

Also, we want field users to be able to collect a new feature then immediately launch a survey to collect some additional information. A URL attribute wouldn't be compatible with that workflow.

AdrianWelsh

What about this. For an out-of-the-box approach at this, go under Pop Up Media and add an Image. Pick an image that is of your organization (like a logo or just a picture of a survey) and then for the Link spot, list your field that stores the URL. Would that work?

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.