Confirmed users
125
edits
No edit summary |
No edit summary |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=SourceMap | |Feature name=SourceMap | ||
|Feature stage= | |Feature stage=Landed | ||
|Feature health= | |Feature status=In progress | ||
|Feature status note= | |Feature version=23 | ||
|Feature health=OK | |||
|Feature status note=Initial support landed in Firefox 23. Improvements coming down the pipe as always. | |||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature feature manager=Dave Camp | |Feature feature manager=Dave Camp | ||
|Feature lead engineer=Nick Fitzgerald | |Feature lead engineer=Nick Fitzgerald | ||
Line 12: | Line 13: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=Nearly every web developer starts with JavaScript in one form during development and then produces JavaScript in another form for production use. Most often, this is a case of joining files together and minifying the output to reduce the number of requests the browser needs to make and how much data the browser needs to transfer. Another example of JavaScript starting in one form and ending up in the final form used by the browser is in PHP scripts which will sometimes generate bits of JavaScript as they generate their pages. | |Feature overview=Nearly every web developer starts with JavaScript in one form during development and then produces JavaScript in another form for production use. Most often, this is a case of joining files together and minifying the output to reduce the number of requests the browser needs to make and how much data the browser needs to transfer. Another example of JavaScript starting in one form and ending up in the final form used by the browser is in PHP scripts which will sometimes generate bits of JavaScript as they generate their pages. | ||
Line 66: | Line 66: | ||
When an error is first generated, the source maps have not yet been loaded. That means that the Web Console cannot immediately display the mapped error info. Once an error is hit, however, the map should be loaded and the error message should be updated as soon as possible to contain the mapped info. | When an error is first generated, the source maps have not yet been loaded. That means that the Web Console cannot immediately display the mapped error info. Once an error is hit, however, the map should be loaded and the error message should be updated as soon as possible to contain the mapped info. | ||
|Feature ux design=[[File:SourceMapInConsole.png|Source mapped output in the Web Console]] | |Feature ux design=[[File:SourceMapInConsole.png|Source mapped output in the Web Console]] | ||
|Feature implementation notes= | |Feature implementation notes=* {{bug|771597}} - Source maps + debugger meta bug | ||
[https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit The source map file format specification] | |||
[https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit The source map file format | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority=P3 | |Feature priority=P3 | ||
|Feature rank= | |Feature rank=3 | ||
|Feature roadmap=Developer Tools | |Feature roadmap=Developer Tools | ||
|Feature list=Desktop | |Feature list=Desktop |