NEW 134688
Web Inspector: clicking in console on user script error fails to jump to resource 
https://bugs.webkit.org/show_bug.cgi?id=134688
Summary Web Inspector: clicking in console on user script error fails to jump to reso...
Antoine Quint
Reported 2014-07-07 13:01:09 PDT
Created attachment 234503 [details] screenshot of prompt to search App Store I have a Cocoa app on Yosemite (14A283o) using the Modern WebKit API (WKWebView) to inject user scripts with the WKUserContentController.addUserScript() method. In the injected script source, I use a `//# sourceURL=foo.js` comment to customise the name of the resource in the Resource sidebar, which works fine. However, when I inspect my WKWebView using Safari 8's OS X remote inspection feature, I can see errors in this user script, but the URL for the error is "user-script:1:90" instead of using the name "foo.js" and clicking on the error shows a dialog saying "There is no application set to open the URL user-script:1." offering to search the App Store for a compatible app.
Attachments
screenshot of prompt to search App Store (96.31 KB, image/png)
2014-07-07 13:01 PDT, Antoine Quint 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2014-07-07 13:01:44 PDT
<rdar://problem/17578798>
Joseph Pecoraro
Comment 2 2014-07-07 13:21:54 PDT
Arg. This is unfortunate. We could probably fix this in the front-end, but a clean fix would be to have JavaScriptCore understand sourceURL per-Script.
Note You need to log in before you can comment on or make changes to this bug.