Bug 145150 - Web Inspector: Support for source maps in remote debugging of JSContext
Summary: Web Inspector: Support for source maps in remote debugging of JSContext
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: iPhone / iPad All
: P2 Enhancement
Assignee: Nobody
URL:
Keywords: InRadar
Depends on: 154303
Blocks:
  Show dependency tree / graph
 
Reported: 2015-05-18 16:50 PDT by Robert Payne
Modified: 2023-06-15 02:27 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Payne 2015-05-18 16:50:22 PDT 
If one uses the remote debugger to debug a JSContext instance on an iOS device or simulator source maps do not work.

Reproduction Steps:

1. Start up a simple iOS application in the simulator that creates a JSContext and loads a script with source maps
2. Connect via WebKit remote debugging to the JSContext

Observed Results:

Source maps are not loaded and digested into the web inspector

Expected Results:

Source maps should be loaded and digested into the web inspector

-----------------------------------------

It appears that NetworkAgent.loadResource and Promise are not available to JSContext and thus the source map loading is skipped.
Comment 1 Radar WebKit Bug Importer 2015-05-18 16:50:49 PDT 
<rdar://problem/21009604>
Comment 2 Joseph Pecoraro 2015-05-18 17:00:40 PDT 
<rdar://problem/17826429>
Comment 3 Joseph Pecoraro 2016-02-16 11:58:10 PST 
As a first step, we will at least allow inline SourceMaps (a data uri sourceMappingURL which contains inline source via the `sourcesContent` list). I have a patch up for that on:
<https://webkit.org/b/154303> JSContext Inspector: Support for inline source maps

Lets keep this for tracking loading a Source Map over the network, which still does not exist yet.