Closed Bug 301532 Opened 19 years ago Closed 19 years ago

Bottom edge of browser frame is very wide and has red text written on it, see Summary

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 301565

People

(Reporter: steve2470, Unassigned)

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050720 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050720 SeaMonkey/1.0a

The bottom edge of the browser is about 2 inches tall and I cannot get it to
change. Also, the bottom edge has in red letters this message: 
<!DOCTYPE window SYSTEM "chrome://prefbar/locale/prefbarOverlay.dtd">
--------------------------------------------------------------------^

I also cannot get the text to go away. Both errors occur on all web pages, I
just gave you a "perfect web page" to illustrate.





Reproducible: Always

Steps to Reproduce:
1. Start browser
2. Go to any website
3. Observe the bugs.

Actual Results:  
Every time you see the bugs I detailed.

Expected Results:  
Thin border at bottom of browser with NO text or symbols.
about:buildconfig

Build platform
target
i586-pc-msvc

Build tools
Compiler 	Version 	Compiler flags
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TC -nologo -W3 -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TP -nologo -W3 -Gy -Fd$(PDBFILE)
-I/usr/X11R6/include

Configure arguments
--enable-application=suite --without-system-jpg --without-system-zlib
--enable-extensions=default,tasks --enable-crypto --disable-auto-deps
--disable-debug --enable-optimize
Did you try a virgin profile?
(In reply to comment #2)
> Did you try a virgin profile?

Yes.

regressed somewhere between BuildID 2005071806 and BuildID 200507202, using zip
builds, and extension 'Inspect This'

I would like to confirm, but don`t know where this bug belongs to.

Bug seen with:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050721 SeaMonkey/1.0a

BuildId 2005071806 was o.k., tinderbox BuildId 2005072020 was showing the bug.
I'm using zips, and between these two builds there were no zip-packaged builds
available.
I'm nearly daily deleting the folder with the old nightly and unzip the next
into a new folder with same name, so my shortcuts stay working.
I've got maybe two extensions installed, LiveHTTPheaders 0.10 or whatelse is
current, and InspectThis, which calls DOMInspector on rightclick.
I tested tinderbox BuildId 2005072020 this morning, got the error message from
the extension 'Inspect This', used previous BuildID 2005071806 and all was ok,
then used  current nightly BuildId 2005072106 to see the bug again.
I created a new, virgin profile, and didn't change or add anything, bug was
staying. 

LiveHTTPheaders works, Inspect This produces the message. 
The bug shows when browser starts, no URL or homepage needed.
http://extensionroom.mozdev.org/more-info/inspectthis
Severity: trivial → critical
Keywords: regression
Version: unspecified → Trunk
using the virgin profile I made for testing the bug, I installed 'Inspect this'
twice, first time in the 'global chrome folder' and restarted the browser, then
in the 'profile folder' and restarted the browser, in both cases the bug stayed.
But now I'm seeing again (in my normal profile, don't know if it's also in the
test profile where I installed) the 'Inspect this' entry in the context menu,
though not working.

Error messages from JS console:

2x Error: inspectDOMDocument is not defined
Source File: chrome://inspectthis/content/inspectthis.js
Line: 5

4x Error: this.docShell has no properties
Source File: chrome://global/content/bindings/browser.xml
Line: 0

2x Error: inspectDOMDocument is not defined
Source File: chrome://inspectthis/content/inspectthis.js
Line: 5

2x Error: inspectDOMDocument is not defined
Source File: chrome://inspectthis/content/inspectthis.js
Line: 13

*** This bug has been marked as a duplicate of 301565 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.