Time element throws "is not a known element" in Unit Tests

🐞 bug report

Affected Package

It happens with unit testing, not entirely sure what package is responsible.

Is this a regression?

No I think it has always been a bug

Description

When using a HTML Time element <time></time> during ng test it gives back a warnning because it doesn’t recognize it as an element.

🔬 Minimal Reproduction

Any time element will do, but for example: <time>19-08-2020</time>. Run a unit test and it will pop up.

🔥 Exception or Error

WARN: ''time' is not a known element:
1. If 'time' is an Angular component, then verify that it is part of this module.
2. To allow any element add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.'

🌍 Your Environment

Angular Version: 9.1.10 but I think it hasn’t been fixed yet.

Anything else relevant?

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time

Workaround is to not use it, use the no_errors_schema or mock the element as if it was Angular.

[gkalpak]

Thx, @vtsiris!

Based on the reproduction, it seems that Angular does indeed recognize the built-in <time> element. Since the issue seems to only be related to PhantomJS, which is not actively developed any more (see ariya/phantomjs#15344) and is not one of the browsers officially supported by Angular (see Browser support), I believe this issue can be closed.

@Martinspire, feel free to open a new issue (with a runnable reproduction) in case I’ve missed something and this is indeed an Angular issue.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}