Unknown custom element: <foreignObject> into TaskList.vue about gantt-elastic

[neuronetio]

That is weird take a look
Maybe upgrading your vue version will help

[renaudham]

Hi

the problem occurs only with one of the ForeignObject, the one directly into the template in TaskList.vue
its ok for the others.

If you put your gantt chart in a vue page loaded in a vue router link, you don't have this problem?

Thanks

[neuronetio]

I don't have this problem.
Again, I think that this is vue related bug - look at this vue bug report - you have the same problem here (I think).
If you update your vue to latest version and problem will still exists, I will reopen this issue.
Thanks for report anyway!

[neuronetio]

Take a look at this fiddle
Remove vue version 2.3.0 and uncomment version 2.5.17 instead - problem does not exists anymore.

[renaudham]

Hi

Still not working with last updates.

Updated all to latest version, same issue.

Note that I use it via WebPack and Npm, not loading the script in a tag in the page
and its a subcomponent of a page with many other elements.

But your link is right, the problem seems to be ForeignObject as first item in component.

The point is that when I look your source, in TaskList.vue from your code,
its ForeignObject as first item
<template> <foreignObject class="gantt-elastic__task-list-wrapper" ref="taskListWrapper" :style="root.style('task-list-wrapper')" x="0"

that seems to be exactly the case and that's what is rejected both by my firefox and Chrome latest versions.

The strange thing is more why its working for you and some other peoples
vuejs/vue#4813

so I guess this should probably be updated by you first into TaskList.vue ,
should you?
Because I guess this will happend for many peoples as soon as they don't use this gantt chart component as a sub part of a page and not as unique component in a page..

The warning in my browser specifically target this taskList.vue element.

Hoping you can find it, thanks for the great job anyway.

Regards

[renaudham]

Sorry, me again.

Maybe that the issue with ForeginObject is ok now, I don't see the same alert anymore, but maybe its a second and different thing

I will open a new ticket for this