Open GoogleCodeExporter opened 8 years ago
I tried:
Google Chrome on Windows: 15.0.874.106
Eclipse features:
Chromium JavaScript Remote Debugger: 0.3.0....
ChromeDevTools SDK WIP Backends: 0.1.2
Backend: WK93101
Sites:
http://jetbrains.com (several refreshes)
http://design.ru (several refreshes)
SDK does assume that FrameNavigated comes first. Have you seen any evidence of
opposite?
Note that future versions of protocol wouldn't work with WK93101 because they
don't send FrameNavigated at all (unless explicitly required), but not
15.0.874.*
Original comment by peter.ry...@gmail.com
on 10 Nov 2011 at 5:16
I've reproduced the problem using 'WebKit Protocol' debug configuration in
Eclipse. Open the attached index.html file in Chrome, start debug configuration
in Eclipse and refresh the page. After that the stacktrace should be printed to
stdout. Also I've attached two txt files containing messages printed to
'Console' window in Eclipse before and after refresh. According to that
ScriptParsed indeed comes before FrameNavigated.
Original comment by nikolay....@gmail.com
on 15 Nov 2011 at 1:19
Attachments:
This seems to be non-fatal exception. Nikolay, can you confirm this?
Original comment by peter.ry...@gmail.com
on 15 Nov 2011 at 4:54
Yes, it seems that this exception doesn't hurt.
Original comment by nikolay....@gmail.com
on 23 Jan 2012 at 9:40
Original issue reported on code.google.com by
nik...@gmail.com
on 10 Nov 2011 at 9:58