[Webkit-unassigned] [Bug 110493] Web Inspector: Segment built files by module boundaries as alternative to sourceURL

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=110493





--- Comment #6 from James Burke <jrburke at gmail.com>  2013-02-21 16:47:52 PST ---
(In reply to comment #5)
> But your goals include mapping line numbers to unbundled files and navigation by file name.  That sounds exactly like what source maps should do.

The goals include that but are not only that use case. I consider Module IDs the new units of functionality, which can be split up, loaded from different places, or grouped together. Even when wanting to map back to a separate file location, the module ID is enough without having the actual file location, and it also works in situations where a path does not make sense.

> I think your concatenator could build the source map using 
> https://github.com/mozilla/source-map/ 
> pretty easy then we could find out exactly what the unwieldy bits are.
> We might conclude that there is no hope or we might conclude that source
> maps can be a lot better.

I do not expect source maps will be usable in all cases. Example use cases where they seem awkward:

* appcache-enabled web apps.
* packaged web apps that are delivered via zip files.

I do not want to deliver the source map baggage for those cases. In those cases, I am more likely to deliver the source as-is or maybe just comments stripped, but still have some concatenated layers for performance. Working with a mobile device, it is common for them to have slower local file I/O where bundling can still help app load time. This has been found in practice with Firefox OS devices.

In those cases, this feature request would still allow better error reports, and if debugging, finer grained debug labels and code unit selection.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.