DevTools/Features/SourceMap - Revision history

Fitzgen at 18:22, 4 June 2013

2013-06-04T18:22:44Z

← Older revision		Revision as of 18:22, 4 June 2013
Line 1:		Line 1:
	{{FeatureStatus		{{FeatureStatus
	\|Feature name=SourceMap		\|Feature name=SourceMap
	\|Feature stage=~~Development~~		\|Feature stage=Landed
			\|Feature status=In progress
			\|Feature version=23
	\|Feature health=OK		\|Feature health=OK
	\|Feature status note=~~Demoed integrated with debugger, work needed~~ in ~~JS engine and some add'l frontend work~~		\|Feature status note=Initial support landed in Firefox 23. Improvements coming down the pipe as always.
	}}		}}
	{{FeatureTeam		{{FeatureTeam
	~~\|Feature product manager=Kevin Dangoor~~
	\|Feature feature manager=Dave Camp		\|Feature feature manager=Dave Camp
			\|Feature lead engineer=Nick Fitzgerald
	\|Feature qa lead=Vlad Maniac		\|Feature qa lead=Vlad Maniac
	}}		}}
Line 64:		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=* {{bug\|~~669999~~}} - ~~Add a library for parsing and consuming source map files to Firefox~~		\|Feature implementation notes=* {{bug\|771597}} - Source maps + debugger meta bug

	* {{bug\|670002}} - Use source maps in the web console		[https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit The source map file format specification]

	* {{bug\|679189}} - Allow eval'd or script tag injected scripts which have no source URL to be source mapped

	* {{bug\|568142}} - Add column information to be available to debuggers.

	* {{bug\|618650}} - map JS source coordinates to source language that was translated to JS


	[https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit The source map file format ~~spec originally proposed by Google~~]~~. I (fitzgen) have edit permissions and am working with them on making something we can all agree upon.~~

	This feature is related to the [[Script_Origin_Tracking\|Script Origin Tracking proposal]], because the mapping should be able to accommodate the many ways in which JavaScript can come into existence on a page.

	* A [https://bugs.webkit.org/show_bug.cgi?id=60550 bug with a patch] was opened for WebKit but closed INVALID.
	** Webkit has [https://bugs.webkit.org/show_bug.cgi?id=30933 another bug] open for this feature.
	** A new [https://bugs.webkit.org/show_bug.cgi?id=63940 bug with a patch] was opened.
	}}		}}
	{{FeatureInfo		{{FeatureInfo

Kdangoor at 15:27, 11 October 2012

2012-10-11T15:27:12Z

← Older revision		Revision as of 15:27, 11 October 2012
Line 2:		Line 2:
	\|Feature name=SourceMap		\|Feature name=SourceMap
	\|Feature stage=Development		\|Feature stage=Development
	\|Feature health=~~Blocked~~		\|Feature health=OK
	\|Feature status note=~~Infrastructure has been laid down~~, ~~integration with other developer tools is~~ needed.		\|Feature status note=Demoed integrated with debugger, work needed in JS engine and some add'l frontend work
	}}		}}
	{{FeatureTeam		{{FeatureTeam
	\|Feature product manager=Kevin Dangoor		\|Feature product manager=Kevin Dangoor
	\|Feature feature manager=Dave Camp		\|Feature feature manager=Dave Camp
	~~\|Feature lead engineer=Nick Fitzgerald~~
	\|Feature qa lead=Vlad Maniac		\|Feature qa lead=Vlad Maniac
	}}		}}

Fitzgen at 21:10, 27 June 2012

2012-06-27T21:10:49Z

← Older revision		Revision as of 21:10, 27 June 2012
Line 3:		Line 3:
	\|Feature stage=Development		\|Feature stage=Development
	\|Feature health=Blocked		\|Feature health=Blocked
	\|Feature status note=~~Work~~ has ~~gotten to a demoable state. Needs to be picked up and finished~~.		\|Feature status note=Infrastructure has been laid down, integration with other developer tools is needed.
	}}		}}
	{{FeatureTeam		{{FeatureTeam
Line 12:		Line 12:
	}}		}}
	{{FeaturePageBody		{{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.		\|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 65:
	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=~~TBD (status page link)~~		\|Feature implementation notes=* {{bug\|669999}} - Add a library for parsing and consuming source map files to Firefox

	* {{bug\|669999}} - Add a library for parsing and consuming source map files to Firefox

	* {{bug\|670002}} - Use source maps in the web console		* {{bug\|670002}} - Use source maps in the web console

Kdangoor at 16:08, 4 April 2012

2012-04-04T16:08:07Z

← Older revision		Revision as of 16:08, 4 April 2012
Line 89:		Line 89:
	{{FeatureInfo		{{FeatureInfo
	\|Feature priority=P3		\|Feature priority=P3
	\|Feature rank=6		\|Feature rank=3
	\|Feature roadmap=Developer Tools		\|Feature roadmap=Developer Tools
	\|Feature list=Desktop		\|Feature list=Desktop

Kdangoor at 15:36, 24 January 2012

2012-01-24T15:36:43Z

← Older revision		Revision as of 15:36, 24 January 2012
Line 89:		Line 89:
	{{FeatureInfo		{{FeatureInfo
	\|Feature priority=P3		\|Feature priority=P3
	\|Feature rank=5		\|Feature rank=6
	\|Feature roadmap=Developer Tools		\|Feature roadmap=Developer Tools
	\|Feature list=Desktop		\|Feature list=Desktop

Kdangoor at 15:35, 24 January 2012

2012-01-24T15:35:56Z

← Older revision		Revision as of 15:35, 24 January 2012
Line 88:		Line 88:
	}}		}}
	{{FeatureInfo		{{FeatureInfo
	\|Feature priority=P2		\|Feature priority=P3
			\|Feature rank=5
	\|Feature roadmap=Developer Tools		\|Feature roadmap=Developer Tools
	\|Feature list=Desktop		\|Feature list=Desktop

Kdangoor at 19:50, 25 October 2011

2011-10-25T19:50:40Z

← Older revision		Revision as of 19:50, 25 October 2011
Line 7:		Line 7:
	{{FeatureTeam		{{FeatureTeam
	\|Feature product manager=Kevin Dangoor		\|Feature product manager=Kevin Dangoor
	\|Feature feature manager=~~Kevin Dangoor~~		\|Feature feature manager=Dave Camp
	\|Feature lead engineer=Nick Fitzgerald		\|Feature lead engineer=Nick Fitzgerald
	\|Feature qa lead=Vlad Maniac		\|Feature qa lead=Vlad Maniac

Kdangoor at 16:11, 19 October 2011

2011-10-19T16:11:41Z

← Older revision		Revision as of 16:11, 19 October 2011
Line 2:		Line 2:
	\|Feature name=SourceMap		\|Feature name=SourceMap
	\|Feature stage=Development		\|Feature stage=Development
	~~\|Feature status=In progress~~		\|Feature health=Blocked
	\|Feature health=OK
	\|Feature status note=Work has gotten to a demoable state. Needs to be picked up and finished.		\|Feature status note=Work has gotten to a demoable state. Needs to be picked up and finished.
	}}		}}

Kdangoor at 15:03, 20 September 2011

2011-09-20T15:03:49Z

← Older revision		Revision as of 15:03, 20 September 2011
Line 3:		Line 3:
	\|Feature stage=Development		\|Feature stage=Development
	\|Feature status=In progress		\|Feature status=In progress
	~~\|Feature version=Firefox 9~~
	\|Feature health=OK		\|Feature health=OK
	\|Feature status note=~~Web Console work is next~~.		\|Feature status note=Work has gotten to a demoable state. Needs to be picked up and finished.
	}}		}}
	{{FeatureTeam		{{FeatureTeam
Line 14:		Line 13:
	}}		}}
	{{FeaturePageBody		{{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.		\|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.

Fitzgen at 21:16, 1 September 2011

2011-09-01T21:16:31Z

← Older revision		Revision as of 21:16, 1 September 2011
Line 73:		Line 73:
	* {{bug\|670002}} - Use source maps in the web console		* {{bug\|670002}} - Use source maps in the web console

	* ~~[https://bugzilla.mozilla.org/show_bug.cgi?id=568142 Bug 568142: Expand~~ source ~~notes to carry column information] - Bug to add line/col information~~ to be ~~available to debuggers.~~		* {{bug\|679189}} - Allow eval'd or script tag injected scripts which have no source URL to be source mapped

	* ~~[https://bugzilla.mozilla.org/show_bug.cgi?id=618650 Bug 618650: map JS source coordinates~~ to ~~source language that was translated~~ to ~~JS]~~		* {{bug\|568142}} - Add column information to be available to debuggers.

	* ~~[https://bugzilla.mozilla.org/show_bug.cgi?id=626932 Bug 626932: Shrink JSParseNode] - Would add character~~-~~offset to SpiderMonkey (as opposed~~ to ~~line/col).~~		* {{bug\|618650}} - map JS source coordinates to source language that was translated to JS
	** Has an incomplete patch by njn. Doesn't compile.

	* David Flanagan has been working on adding "//@line ###" style comment support to ~~SpiderMonkey which is being tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=663934 this bug].~~


Line 86:		Line 83:

	This feature is related to the [[Script_Origin_Tracking\|Script Origin Tracking proposal]], because the mapping should be able to accommodate the many ways in which JavaScript can come into existence on a page.		This feature is related to the [[Script_Origin_Tracking\|Script Origin Tracking proposal]], because the mapping should be able to accommodate the many ways in which JavaScript can come into existence on a page.


	* Brendan and Jim Blandy have suggested that using a separate mapping file will work better than including the mapping in the generated source.

	* A [https://bugs.webkit.org/show_bug.cgi?id=60550 bug with a patch] was opened for WebKit but closed INVALID.		* A [https://bugs.webkit.org/show_bug.cgi?id=60550 bug with a patch] was opened for WebKit but closed INVALID.