Framework: dd() in Chrome v.72 shows blank in AJAX response

[s-patompong]

• Laravel Version: v5.7.25
• PHP Version: 7.2
• Chrome Version: 72

Description:

I was debugging my AJAX request using dd() as I usually do on my Google Chrome browser. This time instead of showing object information in the preview tab, it shows me a blank (white background).

Note:

• This happens inside incognito mode as well. So I don't think Chrome extension is the problem here.
• This happens in Brave browser as well.
• This doesn't happens on Firefox.

Steps To Reproduce:

1. Create a test route call /test-dd in the route file and put some dd() code it in (just a simple array is fine).
2. Create a new blade file and put a script tag that does AJAX call to /test-dd route (in my case I use fetch API).

[romainSaya]

Yes, same probleme for me,
I get a blank in preview tab. but in response tab it shows me raw code

Preview Tab :

Response Tab :

[d-pollard]

This is probably due to the fact that preview in the chrome developer console doesn't run Javascript and dd() relies heavily on it to give a "developer/user"-friendly display:

A solution could be to potentially add in a CSS + HTML based solution inside the noscript tag. Sounds like an opportunity for a PR!

[s-patompong]

Found this on Chrome Dev-Tool forum: https://groups.google.com/forum/#!topic/google-chrome-developer-tools/6btEa32ISEA

Seem like people have been having this problem for a while now. Some has it since Chrome 62. It's weird that I just have this problem now, the previous version of Chrome works perfectly fine for me.

Now, I no longer think this is Laravel problem. I'm not sure if Laravel team will consider this as a big problem at all because people can just use dump-server to see the dump data now.

[driesvints]

Seems like this is a Chrome issue rather than an issue with the framework.

[lukas-pierce]

I solved this problem by installing Google Chrome Dev Edition (v74)

[s-patompong]

That mean Chrome's dev bring back the feature in v74. I'll wait until it releases then.

[browner12]

seems to be working again in Chrome 73, released yesterday.

[s-patompong]

Yep, can confirm that it's back to work now on v73. Tested on Laravel 5.7.

[acv-namtd]

Oh chrome version 73 has fixed it

[ErnestStaug]

Still not working for me...
Version 73.0.3683.86 (Official Build) (64-bit)

While it works fine on FIrefox

[s-patompong]

@ErnestStaug does it work if you change from null to something else like an array?

[ErnestStaug]

Nope, nothing works... checked on colesgues computer same issue :)

On Thu, 4 Apr 2019 at 12:08, Patompong Savaengsuk [e-mail]
wrote:

@ErnestStaug https://github.com/ErnestStaug does it work if you change
from null to something else like an array?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/27428#issuecomment-479815542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQdpgTc1y2Lr0yJEXgkcMkS95nCGGjheks5vdcEFgaJpZM4akv7p
.

[s-patompong]

Just an update, for me this issue shows up again in Chrome 75.

[driesvints]

Hey everyone,

I'm locking this issue because it either has gone off-topic, become a dumping ground for things which shouldn't be in an issue tracker or is just too old. Please try to discuss things further on one of the below channels:

• Laracasts Forums
• Laravel.io Forums
• StackOverflow
• Discord
• Larachat
• IRC