Created attachment 8663297 [details] view_source_blob.tar.gz Three different errors here, possibly caused by same underlying bugs(?), so reporting as one: STR: 1. Open view_source_blob.html in attachment. 2. Open page console, the page has by design an error "SyntaxError: expected expression, got '.'" (page developer is attempting to debug that error) 3. Click on the far right on the link "30911c94-8230-5545-8cdc-e6ce4a2ef7b4:10770:28" to jump in the debugger to the line where the error occurs. Observed: A. In current Firefox Stable 40, there is a systematically reproducible crash: https://crash-stats.mozilla.com/report/index/e99fee56-8033-434b-a9a7-fc2842150919 https://crash-stats.mozilla.com/report/index/48967323-bc1b-4b83-bee6-b256b2150919 however that crash no longer occurred in current Nightly, so this is possibly something that has already been fixed since. B. In current FF Nightly 43.0a1 (2015-09-19), when clicking on the source, a new empty tab is opened which has the url "view-source:blob:null/30911c94-8230-5545-8cdc-e6ce4a2ef7b4". However, the page title is empty, and the page contents is empty. Expected: Instead of opening a new browser tab, the browser debugger should have opened up and showed the JS code source of the blob and the line where the SyntaxError occurred. C. Continuing the STR: in the same empty tab that popped up with the URL "view-source:blob:null/30911c94-8230-5545-8cdc-e6ce4a2ef7b4", replace the URL and navigate to "https://www.google.com/". Observed: Google main page is loaded, and a new alert dialog "Line not found: The specified line was not found <OK>" pops up on top of the Google search page. Clicking ok on the alert, a second alert popup comes up that says "Go to line: Enter line number <textbox> <Cancel> <OK>". Expected: These two popups should not appear. It looks like the tab has gone to some kind of bad state here from the previous failed navigation.
After reporting this I realized that the test case is using .revokeObjectURL() on the blob, so it is understandable that the debugger won't be available on it. However the odd behavior is still odd, perhaps the debugger window should open up, but instead of showing the source, it should show the blob URL and "(source not available)" in the source code listing?
We only fall back to view-source if we can't find the source ourselves. Perhaps we should embed view-source within the debugger's view in these cases?
You need to log in before you can comment on or make changes to this bug.