-
Notifications
You must be signed in to change notification settings - Fork 1.8k
React tab is blank when third-party cookies are blocked #8
Comments
I made a change to the README in #7. Personally, I don't think it's worth fixing as it's inconvenient to rewrite all of blink-devtools to use chrome.storage instead. Detecting might be useful though. |
Well, we could polyfill it. Even an async api can be read in full at load. Then stored synchronously in memory, only to be occasionally flushed asynchronously. We need a better start up page with relevant error information. |
Don't rewrite it using |
I found out a workaround. I added the chrome extension ID to the list of exceptions: Looks like this will make I agree with Sebastian that a better startup page would be great, and this workaround can actually be included as a warning message if such page exists in the future. |
@irae Thanks, good find. |
Thanks :) The (copyable) chrome extension ID is |
the newly released beta version works just fine w/ third-party cookies blocked. |
If I use React Developer Tools in a Chrome profile that has "Block third-party cookies and site data" enabled in Content settings, the contents of the React tab are completely blank. Inspecting the inspector shows these errors:
The errors are thrown from these lines:
https://github.com/sebmarkbage/blink-devtools/blob/120a03721f07ecab689e5aa2444ed26094e5ede0/Source/devtools/front_end/Settings.js#L131
react-devtools/views/components/ReactPanel.js
Line 67 in 9879bdc
The relevant Chrome bug is https://code.google.com/p/chromium/issues/detail?id=319328#c4
If it isn't worth fixing, it might be worth detecting the problem and telling the user to disable third-party cookie blocking.
The text was updated successfully, but these errors were encountered: