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
Currently, BChecks allow users to access the raw response body of a web request using response.body. However, it does not allow access to the DOM (Document Object Model) structure of a web page. The DOM is critical to modern web applications because it represents the structure, style, and content of a page, which are dynamically modified by client-side scripts. Without direct access to the DOM, it is difficult to fully understand how a web page behaves in response to various actions or to effectively test for certain types of vulnerabilities, such as cross-site scripting (XSS) based on the DOM.
I would like to get possibility to render the actual DOM and access it via response.dom or similar.
Thanks!
The text was updated successfully, but these errors were encountered:
We'll raise a feature request for this functionality. However, this is not likely to occur in the near future.
Access to the DOM would require various callbacks from the browser at different stages. We don't currently expose this to extensions, so before this feature could come to BChecks, it would need to be added to our Montoya API.
If there's anything else we can help with, then please let us know.
Currently, BChecks allow users to access the raw response body of a web request using response.body. However, it does not allow access to the DOM (Document Object Model) structure of a web page. The DOM is critical to modern web applications because it represents the structure, style, and content of a page, which are dynamically modified by client-side scripts. Without direct access to the DOM, it is difficult to fully understand how a web page behaves in response to various actions or to effectively test for certain types of vulnerabilities, such as cross-site scripting (XSS) based on the DOM.
I would like to get possibility to render the actual DOM and access it via response.dom or similar.
Thanks!
The text was updated successfully, but these errors were encountered: