Confirmed users
125
edits
DevTools/Features/SourceMap: Difference between revisions
→Next Steps & Open Issues
| Line 70: | Line 70: | ||
** By the time a message is logged, or an exception is thrown, it is already too late to fetch the source map because we do not want to delay displaying a message while we go fetch the source map. | ** By the time a message is logged, or an exception is thrown, it is already too late to fetch the source map because we do not want to delay displaying a message while we go fetch the source map. | ||
* When (if at all) should the browser fetch the original source file[s] referenced from a source map? | * When (if at all) should the <strike>browser</strike> debugger fetch the original source file[s] referenced from a source map? | ||
** As soon as it has retrieved the source map? | ** As soon as it has retrieved the source map? | ||
** John J Barton suggests that it should be delayed as long as possible and only the files which are needed by the user be fetched. Most likely, the user is going to be debugging ~40 or so lines of code, we don't want to fetch all thousands and thousands of lines of code from a large, un-minified app. | |||
* From an API standpoint, how should the browser tell the JS debugger that a source map has been fetched and is available? | * From an API standpoint, how should the browser tell the JS debugger that a source map has been fetched and is available? | ||