Changes

Jump to: navigation, search

DevTools/Features/SourceMap

139 bytes removed, 21:10, 27 June 2012
no edit summary
|Feature stage=Development
|Feature health=Blocked
|Feature status note=Work Infrastructure has gotten to a demoable state. Needs to be picked up and finishedbeen laid down, integration with other developer tools is needed.
}}
{{FeatureTeam
}}
{{FeaturePageBody
|Feature open issues and risks=Nick Fitzgerald is an intern and primary developer of this feature. He has gone back to school.
|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.
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 implementation notes=TBD (status page link) * {{bug|669999}} - Add a library for parsing and consuming source map files to Firefox
* {{bug|670002}} - Use source maps in the web console
Confirm
125
edits

Navigation menu