Ember-inspector: View Tree completely empty

[nickfedoroff]

I'm not sure when I lost it, but as some point, the View Tree stopped showing anything at all. The other tabs (Routes, Data, Promises) all work as expected.

In a different project, the View Tree works fine.Are there know scenarios in which the View Tree will break?

[teddyzeenny]

I have encountered one case https://github.com/tildeio/ember-extension/issues/74.

If you navigate, does the view tree show up?

[dogawaf]

Hi, I have the same behavior, the view tree is empty, even if I navigate between routes.
Neither the search nor the checkboxes "Components" or "All views" do not work.

[teddyzeenny]

@dogawaf are you able to reproduce this in Jsbin ?

[dogawaf]

I tried but without success. One thing to notice, I run an ember-cli app...

[cyril-sf]

@dogawaf Can you try to run window.Ember.Debug.viewDebug.viewTree() in the console and tell me what is the output you get?

And also which browser are you using?

[dogawaf]

I'am using Chrome 36.0.1985.125, on Ubuntu 14.04

> window.Ember.Debug.viewDebug.viewTree()
< false

[cyril-sf]

The extension can't find the main view of your application.

what does $('.ember-application > .ember-view') return?

Which version of Ember do you use?

[dogawaf]

Thx @Cyril-sf, I found it.
I was customizing the body class (for the needs to a bootstrap theme), and the .ember-application class was not maintained in the list of classes. With .ember-application on the body, the view tree is now well populated.

Does the ember inspector can throw some advice if an ember application is detected (other tabs of the inspector work well) but no .ember-application?

[cyril-sf]

@dogawaf I guess we could use the same logic as in the other tabs: get the application from Ember.Namespace.NAMESPACES and then get the ApplicationView from the application. That would avoid to rely on CSS selectors to lookup for that view.

[dogawaf]

I think not having .ember-application somewhere in the DOM must be considered as a problem. The setup of Ember.EventDispatcher relies on this class to do some usefull assertions.
In my case, .ember-application was here at the time of Ember.EventDispatcher.setup(), but I removed it accidentally later. So finally the only "hint" about this issue was the empty view tree...

[cyril-sf]

This is orthogonal. If Ember.EventDispatcher hasn't been setup properly, Ember would have complained.

There's no reason for the inspector to display routes but not views in your case.

[cyril-sf]

I'll make a PR to close this issue.

[cyril-sf]

working on it

[adamreisnz]

It seems this issue is still impacting us. Anything I can do to check what's happening?

The command listed above triggers an error:

window.Ember.Debug.viewDebug.viewTree()

VM25018:2 Uncaught TypeError: Cannot read property 'viewDebug' of undefined(…)