Closed
Bug 301632
Opened 19 years ago
Closed 19 years ago
Bottom frame of Seamonkey is too wide and has red text and symbols upon it
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 301565
People
(Reporter: steve2470, Unassigned)
Details
Attachments
(1 file)
|
150.33 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050721 SeaMonkey/1.0a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050721 SeaMonkey/1.0a 1-Clear cache. 2-Delete cookies. 3-Close browser completely. 4-Navigate to http://www.w3c.org 5-The browser appears this way: the bottom border of the browser is about 2 inches tall, and has this red text upon it: <menuitem id="menu_inspector" label="&inspectorTaskCmd.label;" ------^ Reproducible: Always Steps to Reproduce: See above. A virgin profile was used to reproduce this. Actual Results: The browser's bottom frame appears two inches wide and has red text and symbols upon it (see above). Expected Results: It should have a thin lower browser border and no text or symbols upon it. 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
(In reply to comment #1) > Created an attachment (id=190057) [edit] > screen shot of bug > Never mind, this is a dupe.
(In reply to comment #2) > (In reply to comment #1) > > Created an attachment (id=190057) [edit] [edit] > > screen shot of bug > > > > Never mind, this is a dupe. dupe of bug # 301565
Comment 4•19 years ago
|
||
*** 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.
Description
•