# "$event.stopPropagation" error occurs in webinar\_app plugin

**URL:** <https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311>\
**Category:** Kibana\
**Created:** [November 20, 2017, 4:54am UTC](https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311 "2017-11-20T04:54:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![drumn](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@drumn](https://discuss.elastic.co/u/drumn)\
**Post date:** [November 20, 2017, 4:54am UTC](https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311/1 "2017-11-20T04:54:20Z")

</div>

When I display the plugin of webinar\_app with kibana 6.0.0 and select any visualize,  
the selected Visualize is displayed on the screen, but the following error is output to the browser console.

```
C:\app\nodejs\6.0.0\kibana\node_modules\angular\angular.js:14642 TypeError: $event.stopPropagation is not a function
    at http://localhost:5601/lty/bundles/webinar_app.bundle.js?v=8467:293489:15
    at Scope.$broadcast (http://localhost:5601/lty/bundles/commons.bundle.js?v=8467:41768:29)
    at Object._callee$ (http://localhost:5601/lty/bundles/webinar_app.bundle.js?v=8467:185174:31)
    at tryCatch (http://localhost:5601/lty/bundles/commons.bundle.js?v=8467:66546:41)
    at Generator.invoke [as _invoke] (http://localhost:5601/lty/bundles/commons.bundle.js?v=8467:66780:23)
    at Generator.prototype.(anonymous function) [as next] (http://localhost:5601/lty/bundles/commons.bundle.js?v=8467:66598:22)
    at step (http://localhost:5601/lty/bundles/webinar_app.bundle.js?v=8467:184973:192)
    at http://localhost:5601/lty/bundles/webinar_app.bundle.js?v=8467:184973:438
    at new Promise (<anonymous>)
    at Object.<anonymous> (http://localhost:5601/lty/bundles/webinar_app.bundle.js?v=8467:184973:100)

```

Could you solve this error with the next minor version upgrade etc?

Thank you.

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [November 20, 2017, 5:48pm UTC](https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311/2 "2017-11-20T17:48:59Z")

</div>

cc /@thomasneirynck ping. Can you please take a look.

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [November 28, 2017, 2:05pm UTC](https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311/3 "2017-11-28T14:05:42Z")

</div>

Hi drumn,

thanks for reporting this. That issue can be safely ignored for now.  
We already removed the `ready:vis` event completely for 6.1 via [PR#14988](https://github.com/elastic/kibana/pull/14988).

And it shouldn't break things in between, just throwing nasty errors.

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![drumn](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@drumn](https://discuss.elastic.co/u/drumn)\
**Post date:** [November 28, 2017, 10:01pm UTC](https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311/4 "2017-11-28T22:01:07Z")

</div>

Thank you for your reply.

And thank you for your response that it does not occur in version 6.1.

I am looking forward to release version 6.1!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 26, 2017, 10:01pm UTC](https://discuss.elastic.co/t/event-stoppropagation-error-occurs-in-webinar-app-plugin/108311/5 "2017-12-26T22:01:27Z")

</div>

Closed on December 26, 2017, 10:01pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.