-
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
ExtJS 3.4 support #127
Comments
Sadly, App Inspector does not support Ext JS 3.x - only 4.x+. That's a strange error though, as it's talking about AppInspector's internal architecture - do you get the same error running Chrome stable? |
Tested on chrome 37, it does not throw the above error, but I just get: "No Sencha framework found!", and all the other tabs throw undefined error expectedly. that's due to 3.4.0. So, 3.4 is out of the question? I know it's already two generations back, but it's still widely used. Is there a specific technical reason why this extension would never support 3.4, or it's just a "support issue"? I have to say - your extension looks super-useful. cheers! |
Right now, yes, 3.4 is out of the question. The "specific technical reason" we didn't add support was simply time - we're building this in our spare time, it's not officially sanctioned by Sencha. There are likely some architectural complexities to supporting 3.x as well, but really we just didn't want to tackle it because we didn't have the time. It sounds like the Canary error could just be due to Canary... I haven't heard anything about future builds of Chrome breaking the way extensions work, so I'll just hope that's the case but keep an eye out. |
Ok, thanks. I changed the title of this issue, as a placeholder for the future. |
Trying your extension on chrome canary with a large (old, yet alive and kickin) 3.4.0 webapp.
It directly throws:
isException: true value: TypeError: undefined is not a function
The extension's background page's console gives:
Error in event handler for tabs.onUpdated: Error: Attempting to use a disconnected port object at chrome-extension://pbeapidedgdpniokbedbfbaacglkceae/background/background.js:60:30
Which doesn't really help to resolve this, as it's an unrelated.
Any tip on how to trace such issues with your extension?
Thanks.
The text was updated successfully, but these errors were encountered: