Darel Ngogang

> For me, `NgxMatIntlTelInputComponent.reset()` works. But when I use Reactive Forms and do a reset() on the FormControl, it will not clear the input field. Is this a known issue?...

> The Time-Based Algorithms work this way. It doesn't mean that the code's 30-second life starts from the time when it is generated. It means that it complies with the...

> @Lerado correct! Thank you ! According to the RFC it's recommended to consider having an acceptable delay of transmission that could be considered valid. At most one time-step backwards...

Ok I think I'm kinda stucked by this lol. Please, is it at least possible to use native window.print() with a html visible content ?

> As far as i know window.print() should work. Ok I think that would be a workaround for now. Thank you for the good work there. Glad I bet on...

Same issue here. This is a real problem because I'm using a vendor component I try to inject in a MatDialog. I can't really change that behavior.

This is so annoying. I strongly think the most reusable way of embedding pure components in dialogs is using ng-templates. Please let us know if there is anything we can...

> It seems like the problem has been fixed in angular 16 with this [PR](https://github.com/angular/angular/pull/50270) > I think that is possible. Especially with the new reactivity model.

> Self Answering > > When you set the step to 7 days (604800 seconds) in the otplib.totp.generate method, it will not generate the same output for 7 days. The...