Closed Bug 301565 Opened 19 years ago Closed 19 years ago

Bottom part of suite display gray with script showing. on all Windows.

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: bill, Unassigned)

References

Details

(Keywords: regression) 

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050720 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050720 SeaMonkey/1.0a

No matter browser, address book, mail, etc. the bottom part of screen renders
gray with the following script in red.( <menuitem id="menu_inspector"
label=&inspectorTaskcmd.label;" ) under that script I have ( ____^ ) 

Reproducible: Always

Steps to Reproduce:
1.Down load the latest tinderbox build lhasa build
2.Install
3.Open

Actual Results:  
Any window open shows above bottom part of page gray area with above script showing.

Expected Results:  
Normal full page layout with no script showing.
caused by bug 299286?
Flags: blocking-seamonkey1.0a+
I forgot to preprocess the contents.rdf... I just checked in the trivial "*".
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
*** Bug 301632 has been marked as a duplicate of this bug. ***
*** Bug 301644 has been marked as a duplicate of this bug. ***
*** Bug 301532 has been marked as a duplicate of this bug. ***
I saw early today on the seamonkey tinderbox build under change that bug#  	
301565 was being addressed for todays build. I downloaded todays build
2005072107 and the bug is still there. Still have the gray bottom of window
display with same script showing. 
Still in CVS checkout finish: Fri Jul 22 05:04:11 EDT 2005
I'm changing OS: to ALL, and Version: to TRUNK, as dupes run Windows and OSX
I'm reopening the bug, as it is still seen in a CREATURE Tinderbox build:
1.8b4: 2005072200
Status: RESOLVED → UNCONFIRMED
OS: Linux → All
Resolution: FIXED → ---
Version: unspecified → Trunk
*** Bug 301673 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
checkin for this bug was 
http://webtools.mozilla.org/bonsai/cvsquery.cgi?treeid=default&branch=&branchtype=match&dir=&file=&filetype=match&who=bsmedberg%25covad.net&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-07-21+06%3A36&maxdate=2005-07-21+06%3A36&cvsroot=%2Fcvsroot

2005-07-21 06:36	bsmedberg%covad.net 	mozilla/ extensions/ inspector/ resources/
locale/ jar.mn 	1.2 	  	1/1  	Bug 301565, bustage fix from bug 299265,
seamonkey-only.

Bug 299265 doesn't have a patch attached, but is duped to Bug 205136, having a
review- patch. 

I do have http://extensionroom.mozdev.org/more-info/inspectthis installed in the
profile, but I also see the bug with a virgin profile, Win98 & Win98SE. I'm
using zip nightlies in new folders, and didn't install extensions, had only two
or three for months sitting in the profile.

(In reply to comment #10)
> 2005-07-21 06:36	bsmedberg%covad.net 	mozilla/ extensions/ inspector/ resources/
> locale/ jar.mn 	1.2 	  	1/1  	Bug 301565, bustage fix from bug 299265,
> seamonkey-only.
> 
> Bug 299265 doesn't have a patch attached, but is duped to Bug 205136, having a
> review- patch. 

it's a bustage fis from bug 299286, actually.

Possibly, build from yesterday did not pull the change yet, please check in
builds of today, and be sure you install them into an empty directory for
testing, as I suspect an exisiting chrome.rdf in the application's chrome/
directory might confuse even a fixed build.
(In reply to comment #11)

> Possibly, build from yesterday did not pull the change yet, please check in
> builds of today, and be sure you install them into an empty directory for
> testing, as I suspect an exisiting chrome.rdf in the application's chrome/
> directory might confuse even a fixed build.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050722 SeaMonkey/1.0a
Build ID: 2005072205

unzipped into a new created folder is showing the bug with my default or a
virgin profile. I'm using zips and I delete or rename the folder of the current
nightly before I unzip the next one, so I always use a fresh folder, but having
the name so my shortcut is working.
Keywords: regression
Second try at being fixed, bz helped me out... the <?xml?> declaration in the
contents.rdf was not at the beginning of the file.
Status: NEW → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → FIXED
Just for ultimate posterity, that works was done in bug 299286.
In case any of this helps ...

CREATURE Tinderbox build:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050722
SeaMonkey/1.0a

Wasn't paying too much attention when I installed today, but using the installer
build, selecting DOM, Reporter, Talkback, I had a "menuitem" bug.

Reinstalled, unselecting DOM.  "menuitem" bug remained.  This time I noticed the
bug was, Reporter Tool, "menuitem id="menu_HelpPopup_reportertoolmenu"".

Deleted XUL.mfl (in case that made a difference, & which is no longer in the
Profile directory).

Reinstalled yet again, this time selecting DOM, but unselecting Reporter Tool. 
This time, I seem to have a good install.  No "menuitem" bug.  And no Reporter
Tool, but DOM is working.
*** Bug 301788 has been marked as a duplicate of this bug. ***
*** Bug 301769 has been marked as a duplicate of this bug. ***
reopening, as this bug is still seen on zip builds.
latest tested was from CREATURE, BuildID: 1.8b4: 2005072212

Steps to repeat:
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/CREATURE/
1. download seamonkey-1.0a.en-US.win32.zip
2. unzip to a place where a folder 'seamonkey' doesn't exist.
3. make a shortcut to seamonkey.exe:
   C:\insertYourPath\seamonkey\seamonkey.exe -Profilemanager

4. start using this shortcut, create a new profile, start seamonkey.

Result: bug seen
5. exit seamonkey, restart seamonkey: bug seen
6. delete the seamonkey directory, unzip a fresh one, start: same bug.

Results:

XUL.mfl not generated in the new profile.

Message from JS console:

Error: xml declaration not at start of external entity
Source File:
jar:resource:///chrome/inspector.jar!/locale/en-US/inspector/contents.rdf
Line: 2, Column: 1
Source Code:
<?xml version="1.0"?>

Error: no element found
Source File:
jar:resource:///chrome/inspector.jar!/locale/en-US/inspector/manifest.rdf
Line: 1
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #18)
> reopening, as this bug is still seen on zip builds.
> latest tested was from CREATURE, BuildID: 1.8b4: 2005072212

No problems any longer with zip-Build from CREATURE
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050722-22
SeaMonkey/1.0a
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050723 SeaMonkey/1.0a

Sorry for the bugspam, got the old file from the tinderbox yesterday, and as I'm
in a different timezone, it is hard to notice.
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → FIXED
SeaMonkey/2005072305-trunk/WinXP have this problem.
reopen?
Well, i'm struggling against this problem on my self-compiled linux builds. The
problem is still there  and even has worsened.

Yesterday i had http://www.triffids.de/pub/screenshot/rot.png (60 KB) and now i
have http://www.triffids.de/pub/screenshot/rot2.png (63 KB).

Before the installation i had removed all traces of my old installation, even
the profile. But no success.
sorry, SeaMonkey/2005072305-trunk/WinXP's xul error is 

    <menuitem id="menu_HelpPopup_reportertoolmenu"
----^

it is klike a Bug 298675
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050723 SeaMonkey/1.0a
Build ID: 2005072305, seamonkey-1.0a.en-US.win32.zip

I'm using my normal profile, but it doesn't have a XUL.mfl
Verified - SeaMonkey/nightly/latest-trunk 2005072305 build(ZIP build,Win2K),
with both newly created profile and currently using profile.
Status: RESOLVED → VERIFIED
This behavior was not in the 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050725
SeaMonkey/1.0a build, 

using the .exe installer with the -greLocal command.
You need to log in before you can comment on or make changes to this bug.