Testing the new custom actions @gianantoniopini wrote (thanks again!)

but with this config:

{
    "dark": false,
    "mailto": true,
    "tel": true,
    "office365": true,
    "showFooter": true,
    "actions": {
        "custom": false
    }
}

I'm still getting a custom link being rendered:

Hi Matteo,

Thanks for the direct render functionality. I just tested it and it works as I had hoped!

I've got one unrelated question. What would be the best way to hide the subject and body in the modal? In my case they are both quite lengthy and therefore it does not make sense to display them.

Thanks,

Yoav

How should I go about calling mailgo with a mailto link i'm generating dynamically?

Here's the code: https://github.com/your-digital-rights/yourdigitalrights.org/blob/2d3cdffb3d76de478a83634124572f4e667489d8/src/components/PersonalInfoForm/index.js#L94

If i click on the outlook link the browser opens this link https://outlook.live.com/owa/?path=/mail/action/compose&to=example%40example.com but i land on the outlook homepage. I can then login, but then i don't get any compose window.

If on the other hand i change the url to https://outlook.office365.com/owa/?path=/mail/action/compose&to=example%40example.com (Note the other domain name) i do get a compose window.

I'm not sure if it is platform dependent but I've noticed this issue on MacOs in Firefox with MailGo 0.9.16

It would be good to start adding some unit tests to this useful library.

I would be willing to work on this and submit a PR. For example I could start writing some unit tests for the mailgoDirectRender and mailgoValidateEmail functions, using Typescript and the React Testing Library.

Would this be a welcome addition?

I am the following configuration:

var window.mailgoConfig = {
  dark: true,
  details: {
    subject: false,
    body: false,
    to: false,
    cc: false,
    bcc: false,
  },
};

However the dark theme option has no affect.

Fixes #104 :

• added new "custom" action
• added support for new data-custom-action-text and data-custom-action-url attributes, which can be specified in the mailto: links
• added unit tests for this new "custom action" functionality
• this new "custom" action will only work when mailgo is used with mailto: links. So it is not supported, at least for now, with tel: or callto: links and with mailgo direct render

Other:

• Also added some basic unit tests for already existing functionality (usage with mailto and tel)

It would be useful to be able to validate the To email using the same validation function used internally by mailgo.

As a consumer of the mailgo library, I would like to have the ability to validate the To email address using exactly the same validation function (i.e. same RegEx) that is used internally by mailgo. This is so that the user can be notified of an invalid To email address before the mailgoDirectRender function is called. In this way the validation of the To email address will be done in the same way by the consumer and mailgo.

Therefore it could be useful to export the mailgo validateEmail function, so that consumers of the library can use it if needed.

I would be willing to submit a PR for this.

Is it possible for us to pass a link to MailGo as an option and have it rendered as a custom action?

For example, in the CiviCRM integration it would be beneficial if we could replicate a core function when we override email links. That core function lets us create a CRM "activity" when clicking on an email. If we could add an "Open activity" action - we'd replicate the current status quo and add the amazing additional options provided by MailGo :-)

We implemented a drupal-module for this library. We'd like to allow users not to load module CSS, but also use their own styles. That would be great if your library loaded CSS separately from JavaScript. Thanks.

Hi, I'm currently building a static site with Hugo and would like to add mailgo to my site. However, I've been unable to get it functioning. I've followed the examples on the mailgo pages by linking to the script in the head and body, even by downloading the script itself, but nothing seems to work. Has anyone tried this with a Hugo site yet? Am I missing something?

It would be nice to use the TEXT as the Tel title by default.

<a href="tel:123456789">+39 123456789</a>

https://cln.sh/Z7Fe83 instead of https://cln.sh/hLM5z9

<strong id="m-tel-title" class="m-title">+39 123456789</strong>

<strong id="m-tel-title" class="m-title">123456789</strong>

It would be really nice to be able to explicitly set the title on the Tel modal.

<a href="tel:123456789" data-title="Call Us">+39 123456789</a>

I am wanting to add a custom action for a tel link. It does not display on Tel links but does on Mailto links.

This works

<a href="mailto:[email protected]" data-custom-action-text="Open Docs" data-custom-action-url="https://mailgo.dev/docs/">[email protected]</a>

This does not

<a href="tel:+1234567890" data-custom-action-text="Open Docs" data-custom-action-url="https://mailgo.dev/docs/">[email protected]</a>

I have initialized mailgo with all the config. But the mailgoDirectRender function is broken.

Uncaught TypeError: Cannot read properties of undefined (reading 'classList') at mailgoPreRender (mailgo.js?0de6:892) at mailgoDirectRender (mailgo.js?0de6:917)

The issue is with this line here:

     if ((_config9 = config) !== null && _config9 !== void 0 && _config9.dark || mailgoElement.classList.contains("dark")) {
...

I guess since i am directly calling the mailgo render via the mailgoDirectRender method, the mailgoElement is not defined and there is no null check present.

This does not work:

<a href="mailto:?subject=hello&body=how are you?">[email protected]</a>

(when no recipient of the mail is specified)

This does not work:

var mailgoConfig = {
  dark: true,
  details: {
    subject: false,
    body: false,
    to: false,
    cc: false,
    bcc: false,
  },
};
mailgoDirectRender(mailgoConfig, email);

While this does:

window.mailgoConfig = {
  dark: true,
  details: {
    subject: false,
    body: false,
    to: false,
    cc: false,
    bcc: false,
  },
};
mailgoDirectRender(email);