Closed Bug 263192 Opened 21 years ago Closed 21 years ago

More DTD errors in Thunderbird

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mscott, Assigned: benjamin)

References

Details

(Keywords: fixed-aviary1.0, regression, smoketest)

Attachments

(2 files, 1 obsolete file)

In todays 10/06 bits, I get a DTD error about closeCmd.label not being defined in the main mail 3:pane window. The xul error box shows up at the bottom of the window.
adding the usual keyword fun...
Severity: normal → blocker
Keywords: regression
Summary: More DTD errors in Thunderbird → More DTD errors in Thunderbird
actually you don't even need a release or packaged build to see this. This error is also visible in a regular debug build without any packaging FUD. FYI....
Fixed on branch
Status: NEW → RESOLVED
Closed: 21 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
hmmm that didn't seem to fix it for me. I rebuilt mail\locales with that latest change and now I get two errors: 1) the same close error because it can't find platformCommunicatorOverlay.dtd and now a new one: 2) can't find releaseURL; for the throbber... re-opening
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Keywords: fixed-aviary1.0
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0? → blocking-aviary1.0+
I just checked in another patch, there was a preexisting issue where mail/base/jar.mn shipped several files into toolkit.jar that should have gone into comm.jar (utilityOverlay.xul) which was the cause of the releaseURL entity error. This problem was masked by the repackaging system, which put these files "back" into the right place, I believe.
(In reply to comment #6) > This problem was masked by the repackaging system, which put these files > "back" into the right place, I believe. That's really weird. I saw both of these problems in a debug build that doesn't do any repackaging at all. The repackaging only happens for release builds. I'll test out the fix.
benjamin, that fixed the missing exit/close DTD error but the releaseURL; error is still there. File/Edit and View menus are still broken without any DTD entries in the headers. Again this requires no packaging to see this. Just a debug build will show it to you. So it's not related to the release packaging scripts at all.
-* locale/navigator-platform/contents.rdf (generic/chrome/navigator-region/contents.rdf) +* locale/navigator-platform/contents.rdf (generic/chrome/navigator-platform/contents.rdf) Damn, I apologize for doubting your error, this didn't show up in my build because chrome.rdf had it cached... I was installing the wrong contents.rdf, which was messing up both global-platform and navigator-platform :( In my local build, I'm still missing the text from View -> Toolbars, it's more like View -> "" -> (the toolbar list)... is this string loaded from a properties file or something like that?
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
your latest fix seems to have done the trick! I'm geting View / Toolbars text as well. (it should be going from a DTD file)
*** Bug 263236 has been marked as a duplicate of this bug. ***
Hmmm my debug build at home is still having the error about the label for close not being found. I just did a fresh clobber build and i still see it. I think the problem is that the auto generated installed-chrome.txt in dist\bin\chrome is registering: locale,install,url,jar:resource:/chrome/en-win.jar!/locale/en-US/navigator-platform/ locale,install,url,jar:resource:/chrome/en-win.jar!/locale/en-US/communicator-platform/ locale,install,url,jar:resource:/chrome/en-win.jar!/locale/en-US/global-platform/ but there is no more en-win.jar file getting generated by the build anymore.
Scott: Using today's build on the Mac (version 0.8 (20041007)) I am still seeing issues that are likely related to the DTD errors. This was also reported in the forums: http://forums.mozillazine.org/viewtopic.php?t=141101. I am unable to reply to an email using the Mac. I am also seeing the <menuitem id="menu_close" label="&closeCmd.label;"............../> error that Talios reported in the forum. Sarah hasn't seen this on Linux, and I downloaded today's windows build and I don't have trouble replying to mail and I don't see the errors on the screen that I see on the mac.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
The 20041006 Mac version of TB is clean!
OK, the random incorrect lines in installed-chrome.txt were from "libs" targets in xpfe/global/Makefile.in xpfe/communicator/Makefile.in xpfe/browser/Makefile.in which I wasn't picking up using "make chrome". This has been fixed. I also reverted mail/base/jar.mn since it was causing the View -> Toolbars menuitem to be blank. It appears that the mail/ versions of these three files are bogus and should be removed. If there are more errors, could we open a new bug? This one has morphed twice, although I know that is hard to notice because most of the DTD errors look the same on the outside.
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
haven't seen these problems for a while, so vrfy'ing. if others like this crop up, pls file a separate bug rather than reopening this. thanks!
Status: RESOLVED → VERIFIED
wrong bug Markus?
Flags: needinfo?(mstange)
Attachment #8751969 - Attachment is obsolete: true
Attachment #8751969 - Flags: review?(matt.woodrow)
oops, thank you, sorry about that.
Flags: needinfo?(mstange)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: