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
On iOS, if you load a web page in Safari and then attach the web inspector afterward, there are no console log messages. This is in contrast to macOS, where the console log messages are there if you open the web inspector after loading a web page in Safari. These missing console log messages on iOS make it very difficult to debug certain issues, especially with Safari web extensions on the iOS 15 beta.
The text was updated successfully, but these errors were encountered:
Collecting console entries on device in advance of a connection to a remote inspector isn't a good use of resources. Almost no devices will be connected to a remote inspector. This won't change.
My response:
On iOS, Web Inspector has to be specifically enabled by the user in Settings, Safari, Advanced. So the claim "Almost no devices will be connected to a remote inspector" is a red herring. Almost all devices with Web Inspector enabled in Settings will be connected to a remote inspector.
On iOS, if you load a web page in Safari and then attach the web inspector afterward, there are no console log messages. This is in contrast to macOS, where the console log messages are there if you open the web inspector after loading a web page in Safari. These missing console log messages on iOS make it very difficult to debug certain issues, especially with Safari web extensions on the iOS 15 beta.
The text was updated successfully, but these errors were encountered: