Card component issues with external links

[BenPyton]

I have just updated my doc from 3.11.0 to 4.5.3.
I have some issues with the Card component when used with an external link.

Using this example in any page:

[!card title="Google"](https://google.com)

1. The link does not seem to be treated as an outbound link. And I found no way to set the target to blank to open the link in a new tab.

2. When using retype start command, the link does not open on Firefox browsers, but opens properly on Chrome.
   However, when using the command retype build && retype serve the link opens successfully on Firefox too.

[geoffreymcgill]

Hi @BenPyton. Good catch. I have confirmed both.

1. The link does not seem to be treated as an outbound link. And I found no way to set the target to blank to open the link in a new tab.

We will add the target setting to the Card component.

Automatically handling the outbound link in a Card component like a normal markdown [Google](https://google.com) link is not implemented either, although this does appear to be missing from other Retype components as well, such as Button and Badge.

If a change to automatically handle outbound links for Card component is implemented, that same change will be applied to other external linking Retype components, such as Button and Badge. We will investigate.

2. When using retype start command, the link does not open on Firefox browsers, but opens properly on Chrome.
   However, when using the command retype build && retype serve the link opens successfully on Firefox too.

Confirmed. This is an issue with outbound links when using Firefox during retype start only, and also applies to Button and Badge. This is not a Card component specific issue.

If the target attribute is implemented in issue 1 above, that should work-around this issue with opening in issue 2. An actual fix for this might be a challenge to implement as the defect has something to do with a defect in the underlying Turbo framework used by Retype. We will try to fix. If issue 1 is fixed, that will at least automatically work-around issue 2.

Thanks again for logging these issues. Both are interesting issues that we have not discovered with our testing process, so that also needs to be improved as well.