django-debug-panel icon indicating copy to clipboard operation
django-debug-panel copied to clipboard

Doesn't work on Chrome 65

Open petrprikryl opened this issue 7 years ago • 7 comments

Ajax requests are not showing in Django Debug Panel Chrome extension. Chrome version 65.0.3325.181. Latest 64 version works.

petrprikryl avatar Mar 22 '18 12:03 petrprikryl

It s working for me on Version 65.0.3325.181 (Official Build) (64-bit). Perhaps some other issue.

aakram1 avatar Mar 26 '18 16:03 aakram1

I have the same problem as @nichcz -- the panel doesn't show any requests any more in Version 65.0.3325.181 (Official Build) (64-bit) on linux. Nothing obvious in the console....

I uninstalled the extension, reinstalled it, restarted chrome, and then I got one entry in the debug panel (for '/'). However, the ajax requests did not appear, and subsequent loads of '/' did not create new entries.....

pjsg avatar Mar 30 '18 15:03 pjsg

Same issue here, with Chromium 65.0.3325.181 in linux mint

mredvard avatar Apr 04 '18 01:04 mredvard

this issue is in wrong repository. It should be under https://github.com/recamshak/chrome-django-panel the problem is that at least for me https://github.com/recamshak/chrome-django-panel/blob/master/panel.js#L59 this function does not work for all pages. For me it looks like that like cloudfront / google analytics etc works but my own page does not do any hit for this function? (I am also testing valid https page but still it does not work)

I can see following in extension inspector (developer tools):

image

The more django requests, the more failed requests. So I think this is the bug

I found it. This is similar issue https://productforums.google.com/forum/#!topic/chrome-ja/VVH31BFHgIA

It means that if response has any set-cookie header, the chrome extensions will fail. At least I have csrftoken changing all the time so it means that this does not work at all. I tested it by disabling csrf things, then debug panel works fine again.

Added bug https://bugs.chromium.org/p/chromium/issues/detail?id=836324

zetaab avatar Apr 24 '18 16:04 zetaab

could you guys test with chrome 66, works for me at least

zetaab avatar Apr 25 '18 05:04 zetaab

Chrome 68.0.3440.106 works for me. Looks like problem is solved.

petrprikryl avatar Aug 15 '18 15:08 petrprikryl

not work for me Chrome 76.0.3809.100 not error, not warnning

ruandao avatar Aug 23 '19 07:08 ruandao