New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana's require.js error when defining >1 bettermap #952

Closed
brainstorm opened this Issue Feb 14, 2014 · 0 comments

Comments

Projects
None yet
2 participants
@brainstorm
Copy link

brainstorm commented Feb 14, 2014

When trying to set more than one bettermap, the map's loading bar keeps loading but nothing happens.

The following backtrace shows up in the Chrome JS console:

Error: Map container is already initialized.
    at e.Map.e.Class.extend._initContainer (http://localhost/kibana/app/panels/bettermap/module.js?r=928332b:4:24865)
    at e.Map.e.Class.extend.initialize (http://localhost/kibana/app/panels/bettermap/module.js?r=928332b:4:18220)
    at new b (http://localhost/kibana/app/panels/bettermap/module.js?r=928332b:4:2574)
    at Object.e.map (http://localhost/kibana/app/panels/bettermap/module.js?r=928332b:4:29835)
    at Object.<anonymous> (http://localhost/kibana/app/panels/bettermap/module.js?r=928332b:8:1609)
    at http://localhost/kibana/app/app.js?r=928332b:21:1271
    at Object.f.$eval (http://localhost/kibana/app/app.js?r=928332b:8:9658)
    at Object.f.$apply (http://localhost/kibana/app/app.js?r=928332b:8:9765)
    at http://localhost/kibana/app/app.js?r=928332b:21:1251
    at Object.u.execCb (http://localhost/kibana/vendor/require/require.js:4:12214) 

@rashidkpc rashidkpc added the bug label Feb 24, 2014

@rashidkpc rashidkpc closed this in 5a0dabd Feb 24, 2014

w33ble added a commit to w33ble/kibana that referenced this issue Sep 13, 2018

Chore: enable component testing (elastic#952)
* chore: add and configure enzyme

for testing react components

* chore: add a basic Download test

* chore: move the babelhook

* chore: use JSDOM to provide DOM dependencies

create window, document, and navigator instances to satisfy some deeper UI-centric dependencies

* chore: add simple tests for Loading component

* chore: skip some history tests

JSDom's history api implementation is pretty buggy, so skip these tests until we get execution in a real DOM working
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment