Action Row (only icon triggers action when action is 'open url')


  • When action row’s action is Open URL, you can only trigger the action by clicking the action rows icon.

Expected behavior:

  • The action should be triggered when any of the action row is tapped. On desktop there is an ‘on hover’ slight darkening of the row when you roll over with a mouse, the expected behaviour is that the action triggers when clicking anywhere within this on hover effect.

If you create an action row and set the action to - open new screen - you will see that clicking anywhere on the action row triggers the action (not just the icon)

How to replicate:
Create an action row, add values, and icon, and an action “open url” click the action row to see nothing happens. Click the icon and see the url opens.

What if you have more than one action though? Wouldn’t you want the button to be the only thing that’s clickable?

Would a Hint or Rich Text component work better in this case? I guess in my opinion, I wouldn’t expect anything to be clickable in an Action Row except the buttons. Does seem weird that it’s inconsistent though.

Yeah actually you are right. I like the design of the Action row and often use it just for one action. So I hadn’t thought of your example.

And yes strange that is it inconsistent. If it is indeed only meant to trigger the action (when one action only is available) by the icon tap only, I cannot understand what the ‘on hover’ effect implies. From a UI perspective it’s telling me I can interact with it (anywhere).

Makes sense. Maybe an unintended “feature”??? Would kind of make sense to make the whole thing clickable if there is only one action on the component, but like I said, it’s always been my impression that only the buttons were clickable.

Well in any case I felt it wasn’t clear enough for my users and had to write ‘tap icon’ which I really dislike. I could sold this button-type issue with using a button yes- but the main reason I use action rows as buttons is because it’s only clickable element where I can have a ‘title and description and action’ where the text is not unnecessarily large (like a title component with an action [button]).

That’s where I fall back to something like a hint component (which has an icon option, but unfortunately no Title), or a rich text component (which allows you to basically build a component how you want).

Either component still allows actions when clicked.

I have built my own “hint” style components using rich text components. Here’s some examples:

Basically it’s just some HTML with inline CSS and in some cases, HTML Tables if I need things to line up a certain way. Here is a basic structure that I use for homemade hint components.


That’s really great advice thank you for that. In my experience I wasn’t about to make any useful rich text components without using some html. And I thought I had read that use of HTML was not advised as it could be unsupported at any moment? Can you give me some insight about that?

CSS is the thing that is not advised to be used, in Classic Apps. We were trying to use it in rich text components and it just worked.

In the new Glide Apps, you can use CSS on Business/Enterprise plans, but it works within an “appearance” setup, not in rich text components.

HTML with inline CSS (or inline styling) should work.

1 Like

Yeah, trying to manipulate other Glide components with CSS in a rich text component is the part that is not supported…with the exception of some capabilities with a Business/Enterprise plan using build in CSS options.

The difference though, is that I’m essentially “creating” self contained components. I’m not trying to manipulate other existing components. For that reason I think HTML with Inline CSS is pretty safe. Glide isn’t going to officially support your own creations, but I don’t see it being restricted anytime soon. Many people use snippets of HTML in a rich text component to add html tables, add some specially formatted text, or display any content in a custom way. The bonus is that you can apply an action to a rich text component to give it some functionality.

It’s a nice way to fill in some design gaps in Glide. Also, when you combine it with a custom collection, you can create collections that look the way you want, and contain as much content as you want.