1311694 - The inspector goes blank when calling document.open/write and never calling document.close

Status: NEW

(DevTools :: Inspector, defect, P2)

Description

[Alexandre Poirot [:ochameau]]

Followup of bug 1277348.
There is still some cases where the inspector goes blank when using document.open or document.write.
Using attachment 8769625 [details] from :pbro and his STR from bug 1277348 comment 8:

- open the URL in a new tab
- quickly open the inspector (you have 5 seconds)
- notice that the inspector is correctly loaded, with "content 1" being the only content in the page
- wait until the timeout expires
- notice that the page goes back in loading state, and the inspector goes empty

Now, if you switch to the console and execute 'document.close()' then things are going to go back to normal.

I imagine it triggers a will-navigate event from the TabActor and then never fire any navigate event, which is expected as "load" event will only fire once document.write is called.

Ideally, the inspector wouldn't wait for navigate/load event, but instead window-ready. I tried doing that but it breaks everything. It looks like it would require a significant refactoring on the inspector initiliazation/destruction codepath.

Comment 1

[Patrick Brosset <:pbro>]

Inspector bug triage (filter on CLIMBING SHOES).

Comment 2

[Boris Zbarsky [:bzbarsky]]

It looks like bug 1489308 did not fix this. I don't know what inspector is doing here, exactly, and why it's failing; document.open should not look like a navigation anymore!