-
Notifications
You must be signed in to change notification settings - Fork 42
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
App Inspector doesn't work for components in iframes #33
Comments
This would be a use case I didn't consider... can you possibly create an example in Sencha Fiddle that I can use to start exploring? The problem I already know I'll encounter will be the rabbit-hole of possibilities - we'll have to check each frame to see if child frames exist, etc. The easiest solution will be (similar to Chrome DevTools) to ask the user to select the frame they want to inspect and only show it's contents (components, stores, etc) - because trying to find and merge everything from the top level will be a nightmare and ultimately confusing. In theory it's not technically difficult, but I need a test case in order to be sure I'm solving the task at hand. |
I think you can see it just by going into the Sencha API docs, looking at a class that has an example (like this: http://docs.sencha.com/extjs/4.2.1/#!/api/Ext.grid.Panel), and running the example. The running example is shown inside an iframe, so the problem should be apparent immediately. |
True... I just wanted to be sure it solved a specific problem for you. I'll see if I can get that working, and then you'll be my tester ;-) |
Sure, happy to test it! Just FYI, we use a framework called Ozone which loads separate Ext JS apps into their own iframes (they call these "widgets"). Basically, it acts like a portlet-based "web desktop" to show and manage communication between multiple separate widgets. So this is why I happened to notice the problem. |
We have a very large Sencha application running many iframes containing Sencha sub-applications. This tool would come into its own if we could navigate to the iframes as you have suggested above. As it is the tool is of very little use to us as the sub-applications cannot run in isolation. Do you have a timeframe to provide frame navigation as the console does? |
Sorry, no timetable yet. This actually turns out to be far more difficult than I first thought... and as we develop this project in our spare time we've been trying to focus on lower-hanging fruit first. |
Just as a source of reference, it might be worth looking at another plugin like JSONView (https://chrome.google.com/webstore/detail/jsonview/chklaanhfefbnpoihckbnefhakgolnmc/details?hl=en), which has an option you can enable for "inject into frames". I have no idea how they're doing that, but it sounds similar enough to what is being asked for here that it might be worth a look. |
Ah... I'm running into this issue now. Cannot detect components within a frame. |
Not sure if you know about this or if there's even anything that can be done, but it looks like the extension won't work if a component is loaded into an iframe. (Both Elements inspector "Sencha Component" and the top-level Sencha tab with the full components list, even after hitting refresh, it only shows the top-level page components, but nothing from within any iframes).
Is there a workaround for this, or is this something you might be able to accommodate?
Thanks,
Brian
The text was updated successfully, but these errors were encountered: