Bug 150114

Summary: Web Inspector: [Meta] Improve debugging of preprocessed JS
Product: WebKit Reporter: Nikita Vasilyev <nvasilyev>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: inspector-bugzilla-changes, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Bug Depends on: 142123, 150009, 150010    
Bug Blocks:    
Attachments:
Description Flags
[Image] Web Inspector vs Chrome DevTools none

Nikita Vasilyev
Reported 2015-10-13 22:13:54 PDT
Created attachment 263058 [details] [Image] Web Inspector vs Chrome DevTools I've tried to debug React.js examples from https://facebook.github.io/react/downloads.html. It was problematic for many of them: I hosted the examples on GitHub pages: http://nv.github.io/webkit-inspector-bugs/react-0.14.0/examples/ http://nv.github.io/webkit-inspector-bugs/react-0.14.0/examples/basic-jsx-external/ http://nv.github.io/webkit-inspector-bugs/react-0.14.0/examples/jquery-bootstrap/ WebKit Inspector: – Can’t set breakpoints in example.js. – When Inspector was opened after the page load, example.js isn’t showed in the resources. When Inspector was opened during the page load, example.js appears twice in the list. Chrome DevTools: — Works fine. http://nv.github.io/webkit-inspector-bugs/react-0.14.0/examples/basic-jsx/ http://nv.github.io/webkit-inspector-bugs/react-0.14.0/examples/basic-jsx-harmony/ http://nv.github.io/webkit-inspector-bugs/react-0.14.0/examples/transitions/ WebKit Inspector: — Can’t set breakpoints on the text/babel inline scripts (which was converted to JS by Babel, e.g. "browser.min.js"). Chrome DevTools: — The preprocessed inline scripts available as “embedded” virtual resources.
Attachments
[Image] Web Inspector vs Chrome DevTools (1023.48 KB, image/png)
2015-10-13 22:13 PDT, Nikita Vasilyev 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2015-10-13 22:14:16 PDT
<rdar://problem/23103540>
Note You need to log in before you can comment on or make changes to this bug.