CRM Extensions - ability to configure target attribute on rendered A tags for Links

[Wholesale-Solar]

Hello-

We use crm extensions for lots of things, one is integrating with our on-premise legacy FileMaker based applications.

FileMaker registers a custom url type with the operating system so that we can create urls like fmp://some-database-name/dosomething.

When this url is opened in a browser it immediately launches filemaker and does it's thing.

CRM Extensions render the link urls with a A tag with the target attribute set to "_blank".

This understandable for standard http urls, but with external application urls, when a new tab is opened for the "fmp://" url it leaves behind an empty tab.

We would like the ability to specify/override the target attribute on the rendered A tag so that for certain types of urls the A tag will NOT open a new tab.

[IsaacTakushi]

Hi, @Wholesale-Solar.

Was your username on the old Developer Forum "Chadical"? I believe we spoke on this thread. If so, it's great to hear from you!

I like this idea; in your use case, it makes sense not to open a new tab.

To be transparent, though, the team won't be able to prioritize this over feature requests which have greater potential impact.

Would you create an idea on this board and share it below? I'll upvote the request and other users who want to customize the target attribute of CRM extensions do the same. I'll share the feedback internally as well. Sorry that I can't promise more at this time.

[Wholesale-Solar · Accepted solution]

Hello Isaac Takushi-

Yes, that was me. 🙂

Here is a link to the idea: https://community.hubspot.com/t5/HubSpot-Ideas/CRM-Extensions-ability-to-configure-target-attribute-...

[IsaacTakushi]

Hi, @Wholesale-Solar.

Apologies for the delayed response. I missed this message.

Thanks for sharing! I've upvoted the feature request.

[Wholesale-Solar]

Also, we are still limping along with the redirect solution from the original post as well...

[IsaacTakushi]

I notified the product team of your request to support non-HTTP(S) schemes back in January and it is in their backlog.

I'll update here with any substantive news!