Errors using Weinre with Chrome Version 30.0.1599.69 on Mac

[Dave Kaplan]

I'm getting a blank screen and some errors when I try and connect through localhost:<myport_number>/client or client/#anonymous with Weinre using Chrome Version 30.0.1599.69.

Everything is fine in Safari Version 6.0.5 (8536.30.1). I can even see the target in Chrome from Safari.

Anyone else having trouble seeing targets with Chrome? These are the errors from my Chrome web inspector

StackTrace: StackTrace.amd.js:22

   InspectorBackendImpl::setupProxies StackTrace.amd.js:27

   Client.initialize StackTrace.amd.js:27

   Client::main StackTrace.amd.js:27

1. Uncaught #<Ex> InspectorBackendImpl.amd.js:27
1. module.exports.InspectorBackendImpl.setupProxiesInspectorBackendImpl.amd.js:27
2. module.exports.Client.initializeClient.amd.js:40
3. module.exports.Client.mainClient.amd.js:119
4. (anonymous function)(index):191

1. Uncaught TypeError: Object #<InspectorBackendImpl> has no method 'cachedResources' NetworkManager.js:36
1. WebInspector.NetworkManagerNetworkManager.js:36
2. WebInspector.doLoadedDoneinspector.js:475
3. WebInspector.loadedinspector.js:448
4. boundutilities.js:38

1. Uncaught TypeError: Cannot call method 'registerClient' of undefined Client.amd.js:97
1. module.exports.Client.onLoadedClient.amd.js:97
2. (anonymous function)Binding.amd.js:19

1. Uncaught TypeError: Cannot call method 'logError' of undefined Weinre.amd.js:52
1. module.exports.Weinre.logErrorWeinre.amd.js:52
2. module.exports.EventListeners.fireEventListeners.amd.js:45
3. module.exports.WebSocketXhr._fireEventListenersWebSocketXhr.amd.js:190
4. module.exports.WebSocketXhr._handleXhrResponseGetWebSocketXhr.amd.js:118
5. _xhrEventHandlerWebSocketXhr.amd.js:243

[Patrick Mueller]

I'll be curious to see if other people are getting this.  It appears something died in the browser, leaving a lot of things "unset" (all the "Cannot call method 'fooBlatz'' of undefined" messages).

Here's one possibility - if this isn't it, then ... it may well happen at some point in the future anyway.

Most of weinre is actually the guts of a really old version of Web Inspector.  The rest of weinre is icky bits written by me to get it the Web Inspector code to work by hook or by crook.  Unfortunately, the code in Web Inspector is somewhat tied to the version of WebKit that it was originally shipped with.  We are now running it under a much NEWER version of WebKit (or Blink in the case of Chrome).  The CSS, the DOM, of JavaScript may have changed enough that there's now code in the WebKit code in weinre (or my icky bits) that will just not work in newer versions of WebKit/Blink.

And then we're screwed.

You might say - "just update that crusty old version of Web Inspector you're using".  Easier said than done.  The "icky bits" referred to above, are icky because it takes a while to reverse engineer what we need to do to make the Web Inspector code work.  I only ever updated the Web Inspector code once, and it was very painful.  It will be very painful to do again.

Hope that's not it, but ... thought I'd post the bits above for folk's edification ...

--
--
From the weinre Google Group -- http://groups.google.com/group/weinre
 
---
You received this message because you are subscribed to the Google Groups "weinre" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weinre+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Patrick Mueller
http://muellerware.org

[Dave Kaplan]

Thanks for the reply Patrick! I'll remember not to update my current version of Safari when Apple releases 6.1 :-) or 7.0 or whatever it's going to be... Safari's remote debugging doesn't work with iOS 7 and Safari Version 6.0.5, so Weinre is doing it!

Edge uses Weinre right? I tried Edge, but don't want to pay to use it and it's been a while since I used it, but I think they're having trouble with the updated Webkit too. Anyway, thanks for a great tool!

Kind regards,
Dave