AddScriptToEvaluateOnNewDocument does not called for sandbox'ed iframes
Reported by
dcole...@gmail.com,
Feb 16 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/64.0.3282.140 Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. Add script to evaluate on new document 2. create iframe with sandbox="allow-same-origin", append it to page's body What is the expected behavior? script is called on new document What went wrong? script is not called Did this work before? N/A Chrome version: 64.0.3282.140 Channel: dev OS Version: Flash Version:
,
Feb 19 2018
dcolecki@ Thanks for the issue. Request you to please provide a test file where this issue can be reproduced, which will help in further triaging of the issue. Thanks..
,
Feb 19 2018
,
Feb 20 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 20 2018
Pavel: I don't quite understand the context, but I take it AddScriptToEvaluateOnNewDocument is a dev tools thing. Could you take a look, please?
,
Feb 21 2018
Sry for confusing you, attaching a nodejs test to reproduce bug: chromium-browser --remote-debugging-port=1234 node test.js Result: start connected evaluate waiting for event Expected result (or if you comment line 33 with +"i.sandbox=\"allow-same-origin\";"): start connected evaluate waiting for event message: onNewDocument done
,
Feb 23 2018
Friendly ping.
,
Mar 5 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by krajshree@chromium.org
, Feb 18 2018