Vue: Time tag considered as custom element

[kamui545]

Hello,

It seems the <time> tag is considered as a custom element by VueJS.

I keep getting the following warning on 1.0.0 alpha and beta:

[Vue warn]: Unknown custom element: <time> - did you register the component correctly? 

[yyx990803]

Thanks for reporting. Vue is using element.toString() to check if the browser returns [object HTMLUnknownElement]. Looks like this is a bug in Chrome where valid HTML5 elements <time>, <data>, <rb> and <rtc> return unknown instead of [object HTMLElement].

I have filed a bug for Chrome, you can ignore this warning for now. Also the warning will not show up if you use the production build.

[yyx990803]

So chrome team considers it a WontFix at the moment: https://code.google.com/p/chromium/issues/detail?id=540526

I've added an extra rule to exclude the affected elements from the check: 13e0335

[kamui545]

Oh, this is a Chrome issue, my bad.
Thanks for the patch and the heads-up about the production build, didn't notice it :+1:

[NoelDavies]

This very same thing happens with the details tag as of vue 1.0.24

[Gangwolf]

Same thing happening with <details> and <summary> tags on Firefox.

[yyx990803]

@Gangwolf should be addressed in 63dbc1ca10d1663cb379ca7bd255d0ae3e836673

[john-cheesman]

Just got this in Chrome for <navigation>, is it still an issue?

[posva]

~no, it shouldn't, if you still have the issue you should open an issue with a repro so we can take a look~

[LinusBorg]

<navigation> is an HTML5 element? isn't that <nav>

[posva]

You're right @LinusBorg , I thought he was getting an error with time 😅

[john-cheesman]

Sorry, the HTML5 tag is

. Clearly I've spent too much time writing JS and I'm now forgetting HTML.