Closed Bug 611600 Opened 14 years ago Closed 14 years ago

Possible to get Web Console into unclosable state

Categories

(DevTools :: General, defect, P1)

x86
Windows 7
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: me, Unassigned)

References

Details

(Whiteboard: [Web-Console-Testday])

User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101111 Firefox/4.0b8pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101111 Firefox/4.0b8pre It's possible to get Web Console into an unclosable state by starting it on a fresh about:blank page then visiting another page. Reproducible: Always Steps to Reproduce: 1. Set your home page to about:blank then restart the browser. 2. Click Web Developer->Web Console (nothing happens). 3. Visit any page in the current blank tab (the page loads and a separator appears). 4. Drag the separator down and click the close button. Actual Results: Nothing happens. Expected Results: The web console should close. This only seems to happen with a fresh about:blank tab, if you visit a site then go to about:blank the problem does not occur.
This could be bug 568661
The patch in bug 587734 should hopefully fix this.
mass change: filter on PRIORITYSETTING
Blocks: devtools4
Priority: -- → P1
just restested, and I believe this is fixed. running buildid 20101125.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Whiteboard: [Web-Console-Testday]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.