[Custom Formatters] 'bindRemoteObject' still missing in same edge cases
Reported by
antonin....@gmail.com,
Jun 9 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Steps to reproduce the problem: Related to: https://bugs.chromium.org/p/chromium/issues/detail?id=599884 I'm getting bug reports from some users having this issue in more recent Chrome versions under some circumstances. It looks to me that there are still some code paths which end up with "bindRemoteObject is not defined". https://github.com/binaryage/cljs-devtools/issues/14 What is the expected behavior? What went wrong? Javascript console errors with "... Custom Formatter Failed: ReferenceError: bindRemoteObject is not defined" Did this work before? N/A Chrome version: 51.0.2704.79 Channel: canary OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 21.0 r0
,
Jun 9 2016
,
Jun 13 2016
Just another observation: In my custom fork of DevTools while chasing some other issue I wasn't able to replace implementation of WebInspector.CustomPreviewSection.prototype._loadBody (in CustomPreviewSection.js). It looks like normal DevTools code, but in fact the code seems to be baked inside Chrome and cannot be replaced. Stack traces hint that the code gets injected into target page somehow. I believe the problem could be related to this mechanism and the way where is this code sourced from and how it gets injected.
,
Dec 2 2016
Is it still an issue? Did you get new reports? In codebase currently bindRemoteObject is used in one place [1] and it defines in outer function as argument so it should work correctly. Please reopen this issue if it's reproducible in last versions of Chrome. [1] https://cs.chromium.org/chromium/src/third_party/WebKit/Source/devtools/front_end/components/CustomPreviewSection.js?rcl=0&l=164
,
Dec 2 2016
It seems to be fixed now. Thank you. |
|||
►
Sign in to add a comment |
|||
Comment 1 by antonin....@gmail.com
, Jun 9 2016