Source maps in Firefox

[markfinger]

FF doesn't seem as robust as chrome when it comes to source maps. Currently it either throws errors when reading source maps, or simply shows a blank screen.

It appears that FF might need the original assets to be served as well.

Should be able to add another record map for the original state of textual assets. The file endpoint should check this as the last stage before 404'ing.

[markfinger]

In good news, latest FF doesn't die on sourcemaps anymore. Instead it just links to the original.

In bad news, source maps still don't work.

[markfinger]

This is a bit of a strange situation. The FF debugger is populated with the original content of the files, but it doesn't seem to actually map errors/logs/etc from the generated file to the original content.

I tried a few test cases involving manually tweaking the data in the source map, rewriting paths to file://, using purely relative urls, inlining the source maps, manually creating files that matched the names of the original content ... nothing seemed to have any effect.

No idea at this point.

[markfinger]

Things are somewhat less broken than they used to be, so I'm going to ignore this.