You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2023. It is now read-only.
Concerning bugs have been detected lately related to Chrome 40's handling of the devtools JS. This should be investigated with the upstream maintainers to ensure that the protocol is not being rev'd improperly and in a way that may leave us out in the cold in future updates.
In particular:
Chrome 40's initial release broke handling of the old @161987 and @177902 versions of the WebKit Inspector UI. The Resources tab had numerous rendering bugs, blocking access to WebSQL for us.
After upgrading to @188492, many bugs were detected on slow or unreliable networks. Requests would randomly disappear from the Network tab and the culprit was found to be a previously optional type field is now required in Network.requestWillBeSent and a new undocumented Network.loadingFailed paramater (also type) was added and made mandatory as well. Failure to send these fields causes the UI refresh to raise JavaScript errors.
Once Stetho is made public, we should engage upstream about these issues to understand what's happening.
The text was updated successfully, but these errors were encountered:
It looks like Network.requestWillBeSent's type is still optional, but it's possible the UI makes some assumptions on its presence. That'd be a bug. We could either rev protocol or address the frontend's dependence on the type attribute. We'd welcome a contribution from ya'll for the latter.
Looking at the Network.loadingFailedtype it does appear that's non-optional, and that's undocumented in 1.1.
Concerning bugs have been detected lately related to Chrome 40's handling of the devtools JS. This should be investigated with the upstream maintainers to ensure that the protocol is not being rev'd improperly and in a way that may leave us out in the cold in future updates.
In particular:
@161987
and@177902
versions of the WebKit Inspector UI. The Resources tab had numerous rendering bugs, blocking access to WebSQL for us.@188492
, many bugs were detected on slow or unreliable networks. Requests would randomly disappear from the Network tab and the culprit was found to be a previously optionaltype
field is now required inNetwork.requestWillBeSent
and a new undocumentedNetwork.loadingFailed
paramater (alsotype
) was added and made mandatory as well. Failure to send these fields causes the UI refresh to raise JavaScript errors.Once Stetho is made public, we should engage upstream about these issues to understand what's happening.
The text was updated successfully, but these errors were encountered: