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
MASTG-TEST-0227 currently covers WebView debugging enabled via WebView.setWebContentsDebuggingEnabled(true) and correctly notes that an app itself does not need to be debuggable for this API to enable WebView debugging.
However, the Android WebView API reference for WebView.setWebContentsDebuggingEnabled(boolean) documents an additional version-dependent behavior:
In WebView 113.0.5656.0 and later, this is enabled automatically if the app is declared as android:debuggable="true" in its manifest; otherwise, the default is false.
This appears to mean that, on WebView 113.0.5656.0 and later, WebView debugging can be enabled for debuggable apps even when the application does not explicitly call setWebContentsDebuggingEnabled(true).
From a testing perspective, this may affect how MASTG-TEST-0227 is interpreted:
On WebView 113.0.5656.0 or later, the absence of an explicit call to setWebContentsDebuggingEnabled(true) is not by itself sufficient to conclude that WebView debugging is disabled when android:debuggable="true".
When dynamically testing a debuggable build, WebView debugging may be active solely because of the manifest flag and the WebView version in use.
This also creates a relationship with MASTG-TEST-0226, since the android:debuggable flag can affect the default WebView debugging state on WebView 113+.
It may therefore be useful to document this behavior in the MASTG. Possible options could be:
Add a note to MASTG-TEST-0227 describing the automatic behavior on WebView 113+
Mention the WebView debugging impact of android:debuggable="true" in MASTG-TEST-0226
Add a cross-reference between the two test cases
I am not sure which location would be the best fit, so I would appreciate the maintainers' thoughts on whether and where this behavior should be documented.
AI assistance disclosure:
I used ChatGPT and Gemini for English translation, wording refinement, and cross-review. I reviewed the technical observations and conclusions myself and independently verified the relevant claims against the referenced Android documentation and the current MASTG content.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
MASTG-TEST-0227 currently covers WebView debugging enabled via
WebView.setWebContentsDebuggingEnabled(true)and correctly notes that an app itself does not need to be debuggable for this API to enable WebView debugging.However, the Android WebView API reference for
WebView.setWebContentsDebuggingEnabled(boolean)documents an additional version-dependent behavior:This appears to mean that, on WebView 113.0.5656.0 and later, WebView debugging can be enabled for debuggable apps even when the application does not explicitly call
setWebContentsDebuggingEnabled(true).From a testing perspective, this may affect how MASTG-TEST-0227 is interpreted:
setWebContentsDebuggingEnabled(true)is not by itself sufficient to conclude that WebView debugging is disabled whenandroid:debuggable="true".This also creates a relationship with MASTG-TEST-0226, since the
android:debuggableflag can affect the default WebView debugging state on WebView 113+.It may therefore be useful to document this behavior in the MASTG. Possible options could be:
android:debuggable="true"in MASTG-TEST-0226I am not sure which location would be the best fit, so I would appreciate the maintainers' thoughts on whether and where this behavior should be documented.
References:
AI assistance disclosure:
I used ChatGPT and Gemini for English translation, wording refinement, and cross-review. I reviewed the technical observations and conclusions myself and independently verified the relevant claims against the referenced Android documentation and the current MASTG content.
All reactions