Inconsistent behavior when evaluating properties of a cross-origin iframe's `top` while a breakpoint is hit from DevTools
Reported by
cnsimonc...@gmail.com,
Jul 19 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3160.0 Safari/537.36
Steps to reproduce the problem:
1. Create these pages:
index.html:
<iframe src="http://127.0.0.1/frame.html"></iframe>
frame.html:
<script>debugger;</script>
2. Launch Chrome,Open DevTools, Navigate to `http://localhost/index.html`.
3. When the breakpoint hit, type `top` in the Console and press Enter.
4. Try to expend the returned `Window` object.
What is the expected behavior?
Chrome lists accessible properties of `top` as it does when no breakpoints hit.
What went wrong?
Chrome lists all properties, and throws three exceptions:
(WEB_PAGE context) Lazy require of app.binding did not set the binding field
(WEB_PAGE context) Lazy require of webstore.binding did not set the binding field
(WEB_PAGE context) Lazy require of runtime.binding did not set the binding field
Did this work before? N/A
Chrome version: 61.0.3160.0 Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0
In Chrome Stable 59.0.3071.115, the tab will crash when doing step 4.
,
Jul 19 2017
,
Oct 16 2017
,
Jan 3 2018
Thanks for your report! It is related to the way how we use window proxy during evaluation on pause. But we still provide correct values of each property and unfortunately do not have enough time now to make it perfect. |
||||
►
Sign in to add a comment |
||||
Comment 1 by nyerramilli@chromium.org
, Jul 19 2017