Issue metadata
Sign in to add a comment
|
Regression: Chrome DevTools Protocol - Log.entryAdded or Runtime.consoleAPICalled was not fired on iFrame logging
Reported by
ben.ma...@sourcedefense.com,
Oct 18
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Run chrome with debugging flag 2. Connect to the browser using WebSocket 3. Log.enable() and Runtime.enable() 4. Create listeners for both Log.entryAdded and Runtime.consoleAPICalled 5. Create a static page with an iFrame - Inside the iFrame create a script that prints "Hello world" to the console using console.log What is the expected behavior? both Runtime.consoleAPICalled and Log.entryAdded should be called What went wrong? both Runtime.consoleAPICalled and Log.entryAdded wasn't called Did this work before? Yes 69.0.3497.100 Chrome version: 70.0.3538.67 Channel: stable OS Version: 10.0 Flash Version: |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hhli@google.com
, Oct 19Status: Duplicate (was: Unconfirmed)