WinCairo and our port are both WebKit1, so your suggestion sounds quite plausible. On our port we also hooked up remote WebInpsector but it suffers from the same issue, due to the way its hooked up I think it would be pretty much with WebKit1 way of doing things here too. Are there any suggestions on how we might verify and workaround this issue?
Chris From: [email protected] [mailto:[email protected]] Sent: Friday, October 02, 2015 3:12 PM To: Vienneau, Christopher <[email protected]> Cc: WebKit Development <[email protected]>; Alex Christensen <[email protected]>; Sharma, Rupali <[email protected]> Subject: Re: [webkit-dev] [webkit-help] Issue with Web Inspector debugger breakpoint handling (on Wincairo) Here are the simple steps to reproduce it, 1. Launch WinCairo and go to google.com<http://google.com/> 2. Open Web inspector and open the script source of any .js script 3. Set a breakpoint anywhere 4. Reload the web page What we see is the spinner spinning and never the script source. However, if one presses continue-script-execution from the debugger controls, we get the view back. Is WinCairo using WebKit1 or WebKit2? This sounds like a known issue with WebKit1 where the inspector frontend page lives in the same process as the inspected page. In this situation pausing a page prevents Promise reactions from firing in the inspector frontend page. Loading resource content in the frontend depends on Promises. This should not be a problem in a WebKit2 world where the inspector frontend page lives in a separate process. - Joe
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
