Closed JelleBruisten closed 1 year ago
@nzbin Do we want to support IE? seeing how angular too already dropped support for this.
Personally I don't need this fixed, seeing how there is a work around.
Maybe you can try the 12.10.0
of extensions, it can support IE 11 and the features are same with v14.
@nzbin I mean related to this bug, where we currently have a fix specific for ie that does block something with onPush strategy while current version of angular does not support ie anymore.
project where I am working on that is gonna be using this datetime picker is on latest version of angular so no need to have support for ie myself, just wondering if we should keep specific ie code.
I'm sorry, I misunderstood. There has also some compatible codes for IE in the Material library. Maybe I should fix this issue.
14.5.0 has fixed this issue, please have a try.
I noticed that when using the changeDetection strategy 'onPush' whenever the datetimepicker is closed it is not detected, therefore the:
Would still have the color when it was opened, when you do another click in the same component somewhere maybe on a button the change would be detected. I tracked this down due to:
the setTimeout would make the completeClose to be run in a new macrotask, but changeDetection would already have been run and therefore would not be picked up. A small workaround for now is setting the
on the
datetimepicker
or using the closed event:to explicity call changeDetection when the datetimepicker has closed