A nice feature would be to be able to pass the email hash value instead of the email if you already have that value at hand. This could be either by adding a new input parameter or letting the module detect if the value passed in for the existing email parameter is already an MD5 hash.

@input() backgroundColor: boolean;
should be
@input() backgroundColor: string;

When attempting to set this up, I get the following message to the console:

Uncaught Error: Template parse errors:
Can't bind to 'email' since it isn't a known property of 'img'.
<img ngxGravatar [ERROR ->][email]="user.email" [src]="user.avatar" class="img-thumbnail rounded-circle" alt="">

Hi,
I'm trying to do some unit test on NgxGravatarDirective which seems to be not doable because of the class is not exported as public API

Hi. when can we expect for this to have a angular 10 upgrade?

Hi, when can we expect angular 11 support??

Describe the bug
When loading a webpage with a user's email that is not currently registered to a Gravatar account, we get a 404 error in the console that appears to be generated from the library. A default Gravatar is still generated and renders successfully in the browser. Aside from the console error, ngx-gravatar appears to work successfully. We are importing the library and passing the user's profile. None of the inputs are being used.

To Reproduce
Steps to reproduce the behavior:

1. Submit unregistered email to Gravatar using ngx-gravatar lib
2. Check console for error

Expected behaviour
No errors in the console with a renderer Gravatar.

Screenshots

Desktop (please complete the following information):

• OS: macOS 10.15.6
• Browser [chrome]
• Version [85.0.4183.102]

Additional context

When theres no internet connection, it sends like 100 requests per second, trying to find the gravatar servers.

Hey there,

thank you for this easy to use module.

Got a Chrome warning because of missing attributes while setting cookie:

A cookie associated with a cross-site resource at https://gravatar.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

angular Version: 8.2.x
ngx-gravatar Version: 8.0.0
Chrome Version: Version 78.0.3904.108 (Official Build) (64-Bit)
OS: Mac OSX 10.15

When used with combination of electron and angular, there is issue with protocol.
It is not set to neither https or http but "//" and image can't be downloaded.

Hi. I have a warning using ivy the message is

"Entry point 'ngx-gravatar' contains deep imports into 'node_modules/ts-md5/dist/md5'"

Can we fixed this? I think ivy doesn't like deep imports.

I think this is the issue.

I recently used ngx-gravatar and trying to bind property like the below image. this is throwing error.

Hello!

Thank you for this module. I would like to ask one question, I'm using this module probably in some not-standard way, like this:

import { ɵb } from "ngx-gravatar";

@Component({
  selector: 'user-component',
  templateUrl: 'user.component.html'
})
export class UserComponent {

  constructor(private ngxGravatarService: ɵb) {
  }

  getAvatarUrl(): String {
    return this.ngxGravatarService.generateGravatarUrl(this.authService.currentUser.email);
  }

// .....

}

My question is regarding this alias "import { ɵb }", it comes from a file node_modules/ngx-gravatar/ngx-gravatar.d.ts:

/**
 * Generated bundle index. Do not edit.
 */
export * from './public-api';
export { GRAVATAR_CONFIG_TOKEN as ɵc } from './lib/gravatar-config.token';
export { NgxGravatarDirective as ɵa } from './lib/ngx-gravatar.directive';
export { NgxGravatarService as ɵb } from './lib/ngx-gravatar.service';

Is there any way to remove these aliases, like NgxGravatarService as ɵb.

Best regards,
Alexey Zhokhov.

When using this library, it works wonderfully in every browser except Firefox. On Firefox, the icon is square regardless of settings.

First of all—thanks for putting this together!

To support hi-res monitors/phones, can the requested image size be separate from the img display size? Even when I hard-coded a width/height, the values get overridden.

<img width=40 size="80"...>